# Notifly integrations

Canonical page: https://notifly.io/integrations
Last updated: 2026-10-16

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

### SendGrid (Email)

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.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/sendgrid (markdown: https://notifly.io/integrations/sendgrid.md)

### Postmark (Email)

A Postmark server token and your sender address. Workflows, digests and subscriber preferences run in Notifly; Postmark delivers from your account.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/postmark (markdown: https://notifly.io/integrations/postmark.md)

### Resend (Email)

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.

Claims last checked: 2026-10-16

Read it: https://notifly.io/integrations/resend (markdown: https://notifly.io/integrations/resend.md)

### Mailgun (Email)

A Mailgun API key and sending domain on the US or EU endpoint. Custom headers, reply-to and inline images carry through to Mailgun.

Claims last checked: 2026-10-15

Read it: https://notifly.io/integrations/mailgun (markdown: https://notifly.io/integrations/mailgun.md)

### Amazon SES (Email)

An IAM access key pair, your region and an optional configuration set. Sends go through the SES v2 API on your AWS account.

Claims last checked: 2026-10-16

Read it: https://notifly.io/integrations/amazon-ses (markdown: https://notifly.io/integrations/amazon-ses.md)

### Twilio (SMS)

Account SID, auth token and a sender, with optional EU (Ireland) data residency. SMS steps in any workflow route to your Twilio account.

Claims last checked: 2026-10-16

Read it: https://notifly.io/integrations/twilio (markdown: https://notifly.io/integrations/twilio.md)

### Vonage (SMS)

The API key, API secret and From sender of your Vonage account, listed as Nexmo in the store. SMS steps send through Vonage’s SMS API.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/vonage (markdown: https://notifly.io/integrations/vonage.md)

### Firebase Cloud Messaging (Push)

A Firebase service-account JSON, device tokens registered per subscriber, one trigger. Tokens FCM reports as invalid are pruned by default.

Claims last checked: 2026-10-16

Read it: https://notifly.io/integrations/fcm (markdown: https://notifly.io/integrations/fcm.md)

### APNs (Push)

A .p8 signing key with its Key ID, your Team ID and bundle ID, sandbox or production. Tokens APNs rejects as unregistered are pruned by default.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/apns (markdown: https://notifly.io/integrations/apns.md)

### Expo Push (Push)

An Expo access token and the Expo push tokens your app registers per subscriber. Each device gets its own send; malformed tokens are pruned.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/expo (markdown: https://notifly.io/integrations/expo.md)

### OneSignal (Push)

Keep OneSignal delivering push: its App ID and API key, player ids or External IDs per subscriber, and the workflow around each send in Notifly.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/onesignal (markdown: https://notifly.io/integrations/onesignal.md)

### Slack (Chat)

Add the Notifly Slack app, or bring your own. Reach subscribers through an incoming webhook, or a workspace install that posts as the Notifly bot or as your own app’s bot.

Claims last checked: 2026-10-13

Read it: https://notifly.io/integrations/slack (markdown: https://notifly.io/integrations/slack.md)

### Microsoft Teams (Chat)

Post to a Teams incoming webhook with no credentials, or connect your own Azure bot to message users and channels through the Bot Framework.

Claims last checked: 2026-10-08

Read it: https://notifly.io/integrations/microsoft-teams (markdown: https://notifly.io/integrations/microsoft-teams.md)

### WhatsApp Business (Chat)

A Meta access token, phone number ID, business account ID and app secret. Messages reach the subscriber’s phone through Meta’s Graph API.

Claims last checked: 2026-10-02

Read it: https://notifly.io/integrations/whatsapp-business (markdown: https://notifly.io/integrations/whatsapp-business.md)

## Every provider you can connect

The full list from the dashboard's Integration Store, by channel, under the names the store uses.

### Email (20)

Anypost, Braze, Brevo (formerly Sendinblue), Custom SMTP, Email Webhook, Infobip, MailerSend, Mailgun, Mailjet, Mailtrap, Mandrill, Microsoft Outlook365, Netcore, Plunk, Postmark, Resend, SendGrid, Sendly, SES, SparkPost

### 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.

Channel documentation: https://notifly.io/docs/channels

## 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.