Send a channel alert when a specific project inbox receives mail. The workflow starts from Boundry's New Email trigger and posts through the Slack connection you select.
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 shared support or operations inbox where a person should see a new request quickly, without forwarding the whole message to another mailbox.
Before you start
Inbound receiving must report ready for the selected Sydney project before you publish its MX record.
Connect a Slack workspace and select a channel the app can post to.
Choose which message fields your team is comfortable sending to Slack.
Build it in Boundry
Create a sequence and choose Boundry → New Email as the trigger.
Set To address to the inbox that should alert the channel. Leave other filters empty unless needed.
Add Slack → Send Channel Message and select the connected workspace and channel.
Map the text below, test with a received email, then enable the trigger, action, and sequence.
Workflow template
Use these field values as a starting point, then replace the examples with resources in your own project.
New inbox message → Slack alert
Show the sender and subject in the channel, then let a person open the original in Boundry.
Boundry / New Email (email.received)Slack / Send Channel Message (send_channel_message)
Field mapping
To address
support@your-domain.exampleOnly this inbox starts the sequence.
Channel
Your connected support channelThe Slack app must be allowed to post there.
Message text
New email from {{trigger.from}}
Subject: {{trigger.subject}}Uses fields emitted by New Email; omits the body by default.
Unfurl links
OffAvoids extra link previews in the channel.
Expected result. One Slack message per matching inbound event. Inspect the run and Slack response before treating the alert as delivered.
Where the data goes
The trigger, mapping, run state, and logs belong to the project's regional workflow plane. The selected sender and subject leave that plane when the Slack action runs; Slack then processes them under its own terms.
