Notify
MessagingSend SMS, email, push, Slack, and webhook notifications from a Notify account, which bundles many providers behind one connection. Agents pick the channel per recipient without a contract per provider.
What This Integration Enables
The pitch for Notify is procurement, not features. It bundles a set of messaging providers behind one send API and one Belgian account, so a team that would otherwise be running a Twilio contract, an email provider contract, a push service and a Slack app ends up with one connection and one invoice. FlowRunner agents call it the same way regardless of which provider is doing the delivering, and when the provider behind a channel changes in the Notify app, nothing in the flow changes at all.
That split is the thing to design around. Message content lives in Notify as multilingual templates. The flow supplies a template key, a language and a parameters object, and Handlebars fills the placeholders. The upside is real: a marketing or support owner can fix the wording of a payment failure notice without opening a workflow, and the flow keeps working. The consequence is equally real: the flow does not know what it is about to say. It knows the parameters, the transports and the recipients. Everything a customer reads was authored somewhere else, by someone else, possibly last week. When an agent is about to fan that template out over five channels at once, that gap is exactly where a human-in-the-loop step earns its place.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Payment failure, on the channel the customer answers
A subscription payment fails in Stripe. The agent looks up the customer's contact preference and language, then calls Send Email Notification with the dunning template and the invoice link. If the email is not opened within the retry window, it escalates with Send SMS Notification using the short form of the same template. The wording of both is owned by the billing team inside Notify. The flow owns the escalation timing, the parameters and the decision to escalate at all.
An internal event fanned to the people who need it and the system that logs it
A monitoring flow detects that a nightly reconciliation job did not finish. The agent calls Send Multi-Channel Notification once, with a transport array that puts a message into the finance operations Slack channel and simultaneously posts the same payload to a webhook channel, where the receiving application records the incident against the run. One call, two audiences, one template, and the recipient value travels in the webhook data so the receiving system can link the payload to the right account.
Scheduled maintenance notice with a rehearsal
Maintenance is planned for Sunday. The agent builds the recipient list and renders the template with each customer's parameters. Notify credentials marked as Test log a notification without delivering it, so the flow runs the whole send against test credentials first and hands the resulting log to the person who owns the message. They read what customers would actually receive, in each language, before a single real notification leaves. Then the same flow runs with live credentials on the scheduled date.
Human-in-Loop Highlight
Send Multi-Channel Notification takes a raw transport array, and each entry selects a channel key with its own recipients. One call can put the same template into a customer's inbox, onto their phone as SMS, onto their device as push, into a Slack channel and onto a webhook. That is the useful part and it is also the blast radius. The content is not in the flow, delivery is asynchronous, and the API returns a notification identifier rather than a delivery result, so the first honest confirmation of what customers received arrives in the Notify logs after the fact. Before an agent fans a template across more than one transport to a list above the threshold the team set, it stops and posts the whole case: "This outage notice resolves to 4 transports and 1,180 recipients. Here is the rendered French and Dutch text with parameters filled. Every placeholder resolved. Confirm the transports, or drop SMS and send email plus Slack only?" A person confirms the wording and the reach together, because on this connector those are one decision. Automation exceptions here look like an unresolved placeholder or a recipient with no channel preference, and those go to the same person rather than out to the customer with a blank in the middle of the sentence.
Agent Capabilities
6 actionsNotifications
6- Send Email Notification Sends an email through a configured Notify email channel using a template from the Notify account, with placeholders filled from the template parameters. Supports CC, BCC, Reply-To, a custom From address, Base64 attachments and scheduled delivery. Returns a notification identifier, since delivery itself is asynchronous.
- Send SMS Notification Sends an SMS through a configured Notify SMS channel using an account template, with support for a custom sender number and scheduled delivery. Used as the escalation step when an email has not been acted on.
- Send Push Notification Sends a push notification through a configured mobile or web push channel, delivered to every user subscribed to the given topics. Used for app resident audiences where topic subscription already models who should hear about what.
- Send Slack Notification Sends a message to one or more Slack channels through a configured Notify Slack channel, referenced by name or ID. Used to put an internal event in front of the team without standing up a separate Slack integration.
- Send Webhook Notification Sends a notification through a configured webhook channel, including the recipient value in the payload so the receiving application can link it to the correct user. Used to fan an event to an internal system on the same call that reaches a person.
- Send Multi-Channel Notification Sends one notification over multiple configured channels in a single call by supplying the raw transport array, so the same template goes out over email, SMS, push, Slack, digest and webhook channels at once. Supports attachments on email channels and scheduled delivery. The widest reaching action on the connector, and the one worth putting a person in front of.
Frequently Asked Questions
What can FlowRunner do with Notify?
FlowRunner agents can run Send Email Notification, Send SMS Notification, and Send Push Notification in Notify, plus 3 more actions.
Does connecting Notify to FlowRunner require OAuth?
No. Notify connects to FlowRunner with an API key, no OAuth flow required.
Can Notify trigger a FlowRunner workflow automatically?
Notify doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Notify
$100 in credits. No card required. Connect in minutes.