Keep a received message moving through the same regional project. You can forward the original to a person or send a separate notification from a verified sending domain.
The New Email trigger depends on regional inbound receiving. Check the selected deployment before publishing MX or enabling this workflow. The templates below are configuration recipes, not preinstalled sequences.
Useful for a monitored mailbox that needs a human handoff, or for a team that needs a short notification without the original body.
Before you start
Inbound receiving must report ready for the selected Sydney project before you publish its MX record.
The project needs a verified sending domain for the outbound message.
Decide whether the destination may receive the original body and attachments, or only a separate notification.
Build it in Boundry
Create a sequence and choose Boundry → New Email as the trigger.
Set To address to the mailbox this workflow should handle.
Choose Forward Email for a human handoff, or Send Email for a separate team notification.
Fill the destination and message fields, test with a controlled email, then enable the trigger, action, and sequence.
Workflow templates
Use these field values as a starting point, then replace the examples with resources in your own project.
New inbox message → human forward
Send the original message to a monitored team address.
Boundry / New Email (email.received)Boundry / Forward Email (forward_email)
Field mapping
To address
help@your-domain.exampleOnly this inbox starts the sequence.
Forward to
team@your-domain.exampleA person should own the destination inbox.
Subject prefix
Fwd:Makes the handoff recognisable in the destination inbox.
Include attachments
Off until reviewedAttachments can contain sensitive files.
Expected result. Boundry forwards the stored message using the received email ID. Its automated-forward marker prevents the same message from looping back into another receiving workflow.
New inbox message → team notification
Notify a fixed team address without forwarding the original message.
Boundry / New Email (email.received)Boundry / Send Email (send_email)
Field mapping
To address
help@your-domain.exampleLimits the notification to the intended inbox.
From
team@your-verified-domain.exampleThe sender must be on a verified domain in this project.
To
team@your-domain.exampleA fixed internal destination avoids replies to unverified sender addresses.
Subject
Inbox alert: {{trigger.subject}}Helps the team identify the request.
Text body
New message from {{trigger.from}}. Review it in Boundry.Sends selected metadata without the original body or attachments.
Expected result. The action queues an outbound email. Check its delivery record separately; a successful workflow run does not prove mailbox delivery.
Where the data goes
The received message, workflow run, and outbound message operations stay with the project's selected regional plane. Final delivery still crosses to each recipient's mailbox provider.
