Alerting and notification integrations
Notification integrations fire when something important happens in your app and deliver messages to your customers through channels they already use - Slack, Microsoft Teams, email, SMS, and more.
Build one integration per channel - a Slack integration, an email integration, an SMS integration, and so on. Customers enable whichever channels they want.
Trigger
Use a webhook trigger when your app can emit events in real time - this is the preferred approach. If your app can't push events, use a scheduled polling trigger to check for new conditions periodically.
Your webhook payload should include enough context for the flow to compose a useful notification: what happened, which record it affects, severity, and any relevant IDs or links.
Flow design
One integration per channel. Build a dedicated integration for each notification channel. Prismatic includes built-in components for Slack, Microsoft Teams, Twilio (SMS), SendGrid (email), and many others. Customers install only the channels they want to use.
Use config variables for recipient info. Store webhook URLs, channel names, email addresses, and phone numbers in config variables so each customer's instance can be configured independently.
Keep messages concise and actionable. Notifications should tell the customer what happened and what to do next. Include a deep link back to the relevant record in your app where appropriate.