Carry Callingly lead status into HubSpot intake
Use the status context in a handoff to decide whether a new lead belongs in HubSpot.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A status change is easy to miss when it lives in a calling workflow and the CRM is managed separately.
- Use lead status as part of a CRM intake decision
- Keep new prospects visible for follow-up
- Reduce repeated manual checks across tools
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 supplied status and lead details and create a HubSpot contact when the status means the lead should be tracked.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real status update and confirm the result in HubSpot.
Questions about this workflow
Does this update a HubSpot contact's status?
No. The available action creates contacts. For an existing contact, this workflow does not update its properties.
Which statuses can start the workflow?
The webhook starts it. Include status information in the request and describe the outcome your team wants Notis to treat as a new lead.
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.