Keep leads worth reconnecting with on the follow-up list
Surface leads whose call history gives the team a clear reason to reconnect, then record the next step as a Salesforce task.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create task
Creates a new task in salesforce to track activities, to-dos, and follow-ups related to contacts, leads, or other records.
Why this helps
Leads who need a later check-in can disappear when their next step is not captured in the CRM.
- Capture explicit reasons to reconnect.
- Turn a supported re-engagement decision into a task.
- Keep timing and context tied to call history when available.
Setup
Build it in a few focused steps.
- 1Connect Callingly and Salesforce once in the Notis portal.
- 2Create an automation in Automations, New Automation, and describe the re-engagement review.
- 3Tell Notis to review available Callingly history and create tasks for identified leads only when the history supports a reason and next step to reconnect.
- 4Pick the Notis cron trigger and choose where run reports should go.
- 5Test with one real history item that includes a clear reason to reconnect.
Questions about this workflow
Can it decide when a lead is ready to re-engage?
Only from a rule or reason you provide and details available in Callingly history. The workflow should not invent a baseline or readiness signal.
Does it update Salesforce lead status?
No. The available Salesforce events do not include lead updates, so this workflow creates a follow-up task.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to Salesforce. A trigger fires from one place; an action lands in another.
Callingly triggers
Salesforce actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Callingly and Salesforce, 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 Salesforce.