Make priority Callingly calls visible in HubSpot
Give urgent opportunities a pipeline record as soon as their details reach Notis.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of deals
Creates multiple deals in hubspot crm; ensure any associated object ids, deal stages, and pipeline ids specified are valid and exist within the hubspot account.
Why this helps
Priority calls compete with routine work, making it harder to remember which opportunity needs attention first.
- Put priority opportunities in a trackable place
- Reduce reliance on remembering call urgency
- Create a repeatable route for important conversations
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 create a HubSpot deal from a webhook when the supplied Callingly details mark a call as a priority opportunity.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real priority call example and review the deal in HubSpot.
Questions about this workflow
Does creating a deal set its priority in HubSpot?
The listed action creates deals. Include any writable deal properties you want set and supported by your HubSpot account.
Where does the priority flag come from?
Include it in the webhook request. Callingly has no trigger events in this workflow context.
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.