EventLogger Rules
EventLogger Rules evaluates every EventLogger event against the event rules configured in the CRM and runs the matching rules' actions: sending emails, posting to Slack, creating CRM tasks and editing suppliers. It also serves the REST API the CRM uses to manage rules, action templates and rule history, and it forwards CRM events to EventLogger.
The application is serverless: one AWS SAM stack per account with two Lambda functions, one for the API and one for background work, and no servers waiting for requests.
|
New here? Start with System architecture, then Event processing and rules for what happens to an event. |
What it does
| Capability | Where it lives |
|---|---|
Run event rules for every event on the |
|
Rule, action template and history management for the CRM |
|
Capture events from SDKs and tracking pixels ( |
|
Flag rules that stopped firing (watchdog) |
|
Forward CRM events to EventLogger |
|
Environments
| Environment | AWS account | Stack | Deployed from |
|---|---|---|---|
Staging |
605668041275 |
|
|
Production |
625663093496 |
|
|
Both run in us-east-1. In production the API is published on api.payability.com under
/eventlogger_v2, /track and /tracking.
Where to go next
-
Configuration and secrets: environment settings,
EnableTriggers, thecommon/crmsecret -
Local development:
maketargets, tests, running the API locally -
Build and deployment: SAM build, GitHub Actions, OIDC follow-up
-
Operations: monitoring, the Zappa to SAM cutover, rollback