Keep lead status aligned with a content launch
When a launch changes what should happen next, keep the lead record current in the same flow.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Lead
Updates an existing lead’s contact details, status, or blocking settings.
Why this helps
A lead's next step can change after a launch, but the status update often gets lost between publishing and follow-up.
- Keep relevant lead records aligned with a launch-related decision.
- Reduce manual status updates after content goes live.
- Use context from the webhook and returned records before changing a lead.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and Callingly once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3In one instruction, describe the launch conditions, the lead to update, and the specific status or details to change.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real launch and lead, then verify the updated Callingly record.
Questions about this workflow
Can a content webhook identify which lead to update?
It can if the request includes a lead identifier or enough information to find the lead. Otherwise, provide the identification rule in your instruction; Notis should not guess.
Can this update any lead field?
The available action updates lead information, including status, contact details, or blocking settings. Specify only changes supported by the record and your workflow.
Does Agility CMS supply the webhook trigger?
No. Agility CMS has no listed trigger events here. A Notis webhook starts the workflow when an HTTP request is sent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Callingly. A trigger fires from one place; an action lands in another.
Agility cms triggers
Callingly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Activate/Deactivate Client Account
Activates or deactivates a client account to control access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Creates a new agent.
Create Outbound Call
Creates a call record and immediately places an outbound call, which may incur a cost.
Create Client
Creates a new client account under your agency.
Create Team
Creates a new team.
Create Webhook
Creates a webhook for real-time call or lead notifications.
Delete Agent
Permanently deletes an agent from an account.
Delete Client
Deletes an existing client from your account.
Connect any two apps with Notis in the middle.
Agility cms and Callingly, 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 Callingly.