The “Incoming webhook” trigger starts a Mailpro automation from outside (direction C): a confirmed payment, a form filled in another tool, an event in your own application.
Setting it up
- In Automations, create a workflow and choose the Incoming webhook trigger.
- Build the actions, then activate the workflow: Mailpro shows the trigger URL, once only.
- Paste that URL into the sending tool (Stripe → Webhooks, Typeform → Connect, Zapier/Make/n8n → HTTP or Webhook module), using the POST method.
Test example:
curl -X POST "https://…/Automation/Webhook/Inbound/<your id>/<secret code>"
-H "Content-Type: application/json"
-d '{"email": "[email protected]", "order": "A-1042"}'
→ 202 AcceptedNo developer on hand? You can connect Mailpro to Zapier, Make or n8n and trigger the same automation without writing code.
Good to know
- The code in the URL is your secret: treat it like a password and share it only through a safe channel. An unknown code returns 404.
- Lost the URL? Deactivate then reactivate the automation: a new code is generated and the old one stops working immediately.
- You can send any content, up to 256 KB. Every request received starts one execution of the workflow.
- The
202 Acceptedanswer means “taken into account”: the actions run within the next seconds.
Combine it with the “Send a webhook” action to send a result back to the originating tool.
Mailpro and webhooks
Beyond incoming webhooks — automate your whole email flow
Mailpro's SMTP and API deliver your transactional and marketing email with real-time events, so your app always knows what happened.