Overview
Many platform modules emit events when something changes — a conversation is created, a payment is confirmed, a deal changes stage, etc. You can react to these events via webhooks or through the internal automation rules.
Prerequisites
- Configured webhooks (for external consumption) or Automation access (for internal reactions).
Step by step
- Identify the module event you want to consume (e.g., conversation created, payment paid).
- For external consumption: subscribe to the event in the webhook and handle the payload at your endpoint.
- For internal reactions: create an automation rule with the matching trigger.
- Validate and process the payload idempotently.
Settings & options
- Webhooks: subscription per inbox/account.
- Automation: per-event triggers, with conditions and actions.
- Payload: contains the event context (ids and relevant data).
Use cases
- Update an external system when a payment is confirmed.
- Trigger a follow-up cadence when a deal changes stage.
Tips, limits & best practices
- Always check the real payload source before mapping fields (don't invent the format).
- Ensure idempotency by event identifier.
Troubleshooting
- Event not arriving: confirm the subscription and the endpoint status.
- Unexpected fields: review the actual received payload and adjust the mapping.