Connect one event to the next system.
Start with a real Boundry trigger, choose an action, and follow a template with exact fields to map. Each guide shows where the data goes before you enable the workflow.
Connection templates
These pairs correspond to the customer-facing New Email trigger and the available action systems in the workflow editor.
Inbound email → SlackUseful for a shared support or operations inbox where a person should see a new request quickly, without forwarding the whole message to another mailbox.View templateInbound email → HTTPS APIUseful when your system should open a ticket or queue a review, while you keep the message body in the original regional inbox until a trusted service fetches it.View templateInbound email → Boundry emailUseful for a monitored mailbox that needs a human handoff, or for a team that needs a short notification without the original body.View templates
Browse by integration
See the actions available for an app and follow its related workflow templates.
Check receiving before you build.
New Email depends on inbound receiving being enabled for the selected regional deployment. Do not publish a receiving MX record until that project reports ready. A template is a configuration guide; open the workflow builder to create and test the sequence in your own project.