Respond to CMS correction requests with context
Keep the conversation attached to the original message while using CMS content to understand the requested correction.
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
Correction requests can get separated from the content they refer to, making follow-up slower and harder to track.
- Reply in context to the specific WhatsApp message.
- Use the CMS item as reference for the response.
- Reduce time spent searching for the content under discussion.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and WhatsApp once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to use the CMS item context to draft a concise reply to the specified WhatsApp message when the webhook arrives.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real correction request and verify the reply is tied to the right message.
Questions about this workflow
Will this work without a WhatsApp conversation?
No. WhatsApp delivers a reply only when the recipient has texted first.
What starts this workflow?
A Notis webhook starts it when an HTTP request arrives with the correction request context.
Does the workflow edit the CMS item?
This workflow sends a WhatsApp reply. Make any CMS changes separately or create an automation with an appropriate content update instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Whatsapp. A trigger fires from one place; an action lands in another.
Agility cms 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.
Agility cms 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.