Keep Callingly leads from slipping past follow-up
Give Notis a recurring moment to turn supplied lead details into HubSpot contacts that need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create batch of contacts
Creates up to 100 new contact records in hubspot crm, optionally associating them with existing crm objects; ensure associated object ids are valid.
Why this helps
When follow-up is handled between calls and meetings, leads can sit outside the CRM longer than intended.
- Create a regular review point for leads
- Bring supplied prospects into HubSpot
- Make follow-up less dependent on remembering a separate admin task
Setup
Build it in a few focused steps.
- 1Connect Callingly and HubSpot once in the Notis portal.
- 2Create an automation in Automations > New Automation and give it a clear name.
- 3Tell Notis to review the Callingly lead information you provide and create contacts that still need follow-up.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real lead example and confirm the contact is created as expected.
Questions about this workflow
Can Notis retrieve Callingly call history automatically on a schedule?
The listed Callingly source has no trigger events, so this workflow relies on lead information supplied to Notis rather than an unlisted history trigger.
What should I include in the supplied lead information?
Provide the lead details needed to identify the person and enough follow-up context for Notis to decide whether a HubSpot contact should be created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to Hubspot. A trigger fires from one place; an action lands in another.
Callingly triggers
Hubspot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add token to event template
Adds a new custom data token to an existing event template for a specified hubspot application, optionally populating a crm object property if objectpropertyname is provided.
Archive email
Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.
Archive a batch of emails by ID
Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.
Archive a batch of quotes by id
Archives a batch of existing, non-archived quotes by their ids; this action is irreversible and useful for managing outdated or irrelevant quotes.
Archive batch of companies by id
Archives a batch of companies by their unique ids; targeted companies must exist, not be previously archived, and this api operation is irreversible.
Archive batch of contacts by id
Archives a batch of existing contacts by their hubspot crm ids, rendering them inactive; this action is irreversible via the api and requires manual restoration or a separate unarchive endpoint.
Archive batch of deals by id
Archives a batch of existing deals by their unique hubspot ids, removing them from active views and reports (soft delete); archived deals may be restorable.
Connect any two apps with Notis in the middle.
Callingly and Hubspot, 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 Hubspot.