At Mailpro the word “webhook” covers three different mechanisms. They serve different needs and are configured in different places — the direction of the arrow makes all the difference.
| Direction | What it is for | Where to configure it | |
|---|---|---|---|
| A | Mailpro → your tool (event webhooks) | Be notified in real time when something happens in your account: email delivered, bounce, new contact, SMS delivered… | Settings → Webhooks menu, or the Webhook API |
| B | Your automation → a tool (webhook targets) | At a given step of a workflow, push information to Slack, your ERP, a Google Sheet, Zapier… | Automations → Webhook targets menu, then the “Send a webhook” action |
| C | A tool → Mailpro (incoming webhook) | Start a Mailpro automation from outside: a Stripe payment, a Typeform answer, a sign-up on your website… | In the automation, the “Incoming webhook” trigger |
Which one do I need?
- You want to know what happens in Mailpro → A. See the list of events.
- You want Mailpro to act on another tool during a workflow → B. See the “Send a webhook” action.
- You want another tool to start a workflow in Mailpro → C. See the incoming webhook.
The three combine: a payment triggers an automation (C), which sends a confirmation email and then notifies your ERP (B); the delivery of that email is confirmed to you by an event (A).
Going further: the Mailpro developer portal documents the Webhook API and the data formats.