🤖 Automated notifications
Order confirmations, payment reminders, dispatch updates and OTPs go out the moment the event happens, on the channel each recipient prefers.
Reach the right person on the right channel automatically
Connect ERPNext to WhatsApp, Twilio, Slack, Microsoft Teams and email so every alert, OTP, approval and customer message goes out from one place. Your team and your customers stay informed without anyone sending a manual update.
5 Channels
One Rule Engine
Event-Driven
Alerts
Zero
Manual Follow-Ups
How ERPNext sends a message on any channel
An event triggers the native notification engine, which fills a template and sends on the chosen channel.
Step 1
Event
A document is created, saved, submitted, or reaches a date, for example an order or overdue invoice.
Step 2
Condition
The rule checks that it matters, such as amount over a limit or invoice overdue.
Native
Notification engine
Fills a template with document fields and picks the recipient.
Step 3
Channels
Email
Slack
WhatsApp
SMS
Teams (webhook)
➔ Flows back: replies and delivery status are captured against the record, and approvals update the document in ERPNext.
Four ways ERPNext keeps everyone in the loop
One notification engine drives every channel, so an alert, OTP, approval or follow up reaches the right person the moment it matters.
See the ERPNext communication integration in action
Representative dashboard views showing how notifications, approvals, customer follow ups and ticket updates flow from ERPNext to every channel.
Automated notifications: every alert and OTP, sent the moment it fires
A notification rule watches a document event, checks a condition, fills a template and sends on the right channel, all without anyone pressing send.
One rule can reach email, WhatsApp, Slack or SMS
OTPs and confirmations delivered in seconds
Every message logged against the record it came from
Notification Center
Illustrative dashboard mockup, not a live ERPNext screenshot.
How the ERPNext notification engine works
Email and Slack alerts and the notification engine are native to ERPNext. Twilio, WhatsApp and Teams plug into the same engine, so one rule can reach any channel.
Watch an event
Fire on new, save, submit or cancel of any document, or a number of days before or after a date.
Add a condition
Only send when it matters, for example an order over a value or an invoice that is overdue.
Write the message
Use templates with document fields, tuned for each channel, so the message reads right everywhere.
Pick the channel
Send on email, Slack, SMS or WhatsApp, or route to Microsoft Teams by an incoming webhook.
Every channel, and how it connects
Overview of native support levels, transaction support, and backend setup requirements.
| Channel | Notifications | OTP | Two way | How it connects |
|---|---|---|---|---|
| Email (SMTP / IMAP) | Yes | Yes | Inbound and outbound | Native (Email Account) |
| Slack | Yes | Not typical | One way alerts | Native (incoming webhook) |
| Twilio | SMS and voice | Yes | SMS and WhatsApp | Official Frappe app |
| Yes | Yes | With templates | Via Twilio or WhatsApp Cloud API | |
| Microsoft Teams | Yes | Not typical | One way alerts | Incoming webhook or iPaaS |
Email, Slack notifications and the notification engine are native. Twilio is an official Frappe app that adds SMS, voice and WhatsApp. WhatsApp needs the WhatsApp Business API and message templates approved by WhatsApp. Microsoft Teams connects through an incoming webhook or an iPaaS layer.
The business case in three numbers
How automated communications improve operational velocity.
3,280+
Messages a day, hands-free
Notifications, OTPs and follow-ups send themselves the moment an event fires, so no one spends the day sending manual updates.
1
Rule engine
One notification engine drives every channel, so you set a rule once and reach anyone on email, WhatsApp, Slack, Teams or SMS.
Faster
Approvals and replies
Alerts reach the right person instantly, so approvals move and customer questions get answered without the wait.
Frequently Asked Questions
Everything you need to know about setting up and running ERPNext communications integrations.
Email over SMTP and IMAP, Slack, SMS and WhatsApp through the native notification engine. Twilio adds SMS, voice and WhatsApp, and Microsoft Teams connects through an incoming webhook or an iPaaS layer. Any other channel with an API can be added through a custom Frappe integration.
Yes, through Twilio or a WhatsApp Cloud API app. WhatsApp requires the WhatsApp Business API and message templates approved by WhatsApp before you can send to customers, which keeps you compliant with WhatsApp policy.
A Notification rule watches a document event, such as new, save, submit, cancel, or a number of days before or after a date. It checks a condition, fills a template with document fields, and sends on the channel you choose.
Yes. Approval alerts route to Slack natively or to Microsoft Teams through an incoming webhook, with the document context the approver needs, and the outcome flows back into ERPNext.
Yes. ERPNext has native inbound and outbound email through the Email Account, using IMAP or POP for incoming mail and SMTP for outgoing, with every message logged against the related record.
Ready to automate yourNotifications & Alerts?
Connect ERPNext to WhatsApp, Twilio, Slack, and Microsoft Teams. Streamline automated alerts, OTP confirmations, and workflow approvals on autopilot.
