Keep your providers. Add the workflow layer.
Notifly connects to 81 email, SMS, push and chat providers. You connect each one with your own account and API key, so deliveries leave from your domains and numbers, on your provider plan, and your sender reputation stays yours.
On top of them, one API call runs a whole notification workflow: steps across channels, digest, delay and throttle, subscriber preferences checked before each send, an in-app Inbox, and an activity feed that shows what each provider answered.
Provider setup guides
Each guide quotes the exact fields the dashboard asks for, shows a trigger with the published SDK, and lists what reaches the provider on every send.
SendGrid
Your SendGrid API key, the Global or EU region, and an optional IP pool. Every send is tagged with its workflow as the SendGrid category.
Postmark
A Postmark server token and your sender address. Workflows, digests and subscriber preferences run in Notifly; Postmark delivers from your account.
Resend
A Resend API key and a verified from-address. Messages go out as “Sender name <address>”, and a refused send records Resend’s own error.
Mailgun
A Mailgun API key and sending domain on the US or EU endpoint. Custom headers, reply-to and inline images carry through to Mailgun.
Amazon SES
An IAM access key pair, your region and an optional configuration set. Sends go through the SES v2 API on your AWS account.
SMS
Twilio
Account SID, auth token and a sender, with optional EU (Ireland) data residency. SMS steps in any workflow route to your Twilio account.
Push
Firebase Cloud Messaging
A Firebase service-account JSON, device tokens registered per subscriber, one trigger. Tokens FCM reports as invalid are pruned by default.
Chat
Slack
Your own Slack app. Reach subscribers through an incoming webhook, or an OAuth workspace install that posts as your app’s bot.
Every provider you can connect
The full list from the dashboard's Integration Store, by channel, under the names the store uses. Providers with a setup guide link to it.
Email 20
SMS 38
- 46elks
- Africa's Talking
- Afro Message
- Azure Sms
- Bandwidth
- Brevo
- BulkSMS
- clickatell
- Clicksend
- CM.com
- Eazy
- Firetext
- Gupshup
- iMedia
- Infobip
- iSend SMS
- iSendPro
- Kannel SMS
- Kudosity (formerly BurstSMS)
- Maqsam
- MessageBird
- Mobishastra
- Nexmo
- Plivo
- RingCentral
- Ruach SMS
- Sendchamp
- SimpleTexting
- Sinch
- SMS Central
- SMS Webhook
- sms77
- smsmode
- SNS
- Telnyx
- Termii
- Twilio
- Unifonic
Push 9
- APNs
- AppIO
- Expo Push
- Firebase Cloud Messaging
- OneSignal
- Push Webhook
- Pusher Beams
- Pushpad
- Web Push (VAPID)
Chat 14
- Chat Webhook
- Discord
- GetStream
- LINE
- Mattermost
- MSTeams
- Rocket.Chat
- Ryver
- Sendblue
- Slack
- Telegram
- Webex Messaging
- WhatsApp Business
- Zulip
In-app needs no provider
The in-app channel is Notifly's own Inbox rather than a third-party provider: a real-time feed you embed with the React component or the JavaScript SDK. The same workflow that emails or texts a user can write to their Inbox in the same run.
Channel setup in the docs
Frequently asked questions
Do I need my own account with each provider?
Yes. Every provider listed here connects with your own account and credentials, so messages leave from your sending domains and numbers, show up in your provider's own logs, and are billed to you by the provider. Notifly runs the workflow around each send; it does not resell email, SMS or push.
What does Notifly charge for if my provider delivers the messages?
Events. A Notifly plan meters the workflow triggers you send, not individual messages, so one trigger that reaches email, in-app and push counts once. What each provider charges for its own deliveries stays between you and that provider.
Can I connect two providers for the same channel?
Yes. For email and SMS you can connect several accounts in one environment: one is the primary integration that sends by default, and another active integration takes the send when its conditions match the subscriber or the tenant in the trigger's context. Development and Production keep separate integrations.
How are provider credentials stored?
API keys, tokens, secrets and service-account files are encrypted at rest with AES-256; new and re-saved credentials use authenticated AES-256-GCM. Each provider guide lists which of that provider's fields are encrypted and which, like a sender address or a region, are stored as entered.
Bring your provider account. Keep your sender reputation.
One POST /v1/events/trigger — email, SMS, push, in-app, and chat. 10,000 events a month, free.