Keep regression updates attached to the WhatsApp conversation
Share a clear regression update where your team is already discussing the incident.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send reply
Send a reply to a specific message in a whatsapp conversation. this creates a contextual reply that shows which message you're responding to. note: the reply will be delivered to the recipient only if they have texted first.
Why this helps
A new regression update can be detached from the conversation where the response is being coordinated.
- Keep an update connected to the message it concerns.
- Make regression context visible to people following the conversation.
- Avoid manually rewriting the same incident update.
Setup
Build it in a few focused steps.
- 1Connect Bugsnag and WhatsApp once in the Notis portal.
- 2Create an automation for regression updates.
- 3Tell Notis to read each incoming Bugsnag regression webhook and reply with a concise summary to the matching WhatsApp message when the conversation context is available.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real webhook and a WhatsApp conversation that has an identifiable message to reply to.
Questions about this workflow
Does the webhook itself identify a WhatsApp message?
That is not specified. Supply the conversation and message context in the event or prompt; otherwise Notis cannot infer which message should receive a contextual reply.
Does the recipient need to have started a WhatsApp conversation?
Yes. The listed Send reply action delivers only if the recipient has texted first.
What if there is no matching WhatsApp message?
Have Notis report the missing context instead of sending a reply to an unrelated conversation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugsnag to Whatsapp. A trigger fires from one place; an action lands in another.
Bugsnag triggers
Whatsapp actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create message template
Create a new message template for the whatsapp business account. templates must be approved by whatsapp before they can be used. templates are required for marketing messages and messages sent outside the 24-hour window.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete message template
Delete a message template from the whatsapp business account. this permanently removes the template and it cannot be recovered. only delete templates that are no longer needed.
Get business profile
Get the business profile information for a whatsapp business phone number. this includes business details like description, address, website, and contact info.
Get media
Get information about uploaded media including a temporary download url. the download url is valid for 5 minutes and can be used to retrieve the actual media file. this is useful for downloading media that was sent to your whatsapp number.
Get media info
Get metadata about uploaded media without generating a download url. this is useful for checking file size, type, and hash without downloading the file. use get media if you need the actual download url.
Get message templates
Get all message templates for the whatsapp business account. templates are required for sending messages outside the 24-hour window and for marketing/utility messages.
Get phone number
Get details of a specific phone number associated with a whatsapp business account.
Get phone numbers
Get all phone numbers associated with a whatsapp business account (waba).
Connect any two apps with Notis in the middle.
Bugsnag and Whatsapp, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Whatsapp.