Webhooks overview
Run custom logic in your own systems when messages arrive in an Emailgistics mailbox.
When a message lands in an Emailgistics mailbox, you can have Emailgistics call an HTTPS endpoint you own. Your endpoint can do whatever it needs — query a CRM, classify the message, look up a customer record — and respond with one or more actions that Emailgistics applies to the message.
Today, one event is supported: received (a new incoming message). New event types may be added in future versions of the API — see Forward compatibility for how to handle unknown events.
What you’ll build
- An HTTPS endpoint that accepts a POST request from Emailgistics and returns a structured response. Any platform — your own server, AWS Lambda, Azure Functions, Power Automate — works.
- A webhook definition in Emailgistics Admin that tells Emailgistics where to deliver the request and what secret to authenticate with.
- A mailbox rule that triggers the webhook for matching messages.
How a single delivery flows
- A message arrives. A matching mailbox rule fires.
- Emailgistics POSTs the message details to your endpoint, with a Bearer secret in the
Authorizationheader. - Your endpoint runs custom logic and returns an
actions[]response — assign, tag, set custom fields, send a templated reply, or forward. - Emailgistics applies the actions to the message in order.
What’s covered in these pages
Setting up a webhook
Admin flow: define the webhook, point it at your endpoint, attach it to a rule.
Request payload
Everything Emailgistics sends you, including conditional fields.
Response envelope
The structure your endpoint must return.
Actions
The action types your endpoint can request.
Delivery, retries and security
Retry semantics, IP whitelisting, secret rotation.