Keep Callingly lead details current after a campaign response
When a response changes what you know about a lead, send the lead identifier and verified update details through a webhook. Notis applies the update in Callingly.
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
Lead records become unreliable when campaign responses are captured in one place but not carried into the calling workflow.
- Update a lead using response details supplied by your campaign process.
- Keep Callingly records aligned with verified lead information.
- Avoid retyping response details into the calling workflow.
Setup
Build it in a few focused steps.
- 1Connect Abyssale and Callingly once in the Notis portal.
- 2In Automations, choose New Automation and name it.
- 3Tell Notis to update the Callingly lead identified in the webhook using only the verified lead details included in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real response and an existing Callingly lead identifier.
Questions about this workflow
Can Notis infer a lead's new status from the creative asset?
No. The webhook request must include the verified lead update details, including any status change you want applied.
What happens if the request does not identify an existing lead?
The workflow needs a Callingly lead identifier and update details. Supply both in the request so Notis can target the intended record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abyssale to Callingly. A trigger fires from one place; an action lands in another.
Abyssale 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.
Abyssale 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.