Keep a record of the call outcomes behind sales decisions
Capture outcome context in HubSpot so the reason behind a next step is easier to understand later.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a batch of emails
Creates multiple email objects for record-keeping (does not send emails) within hubspot crm in a single batch, allowing properties and associations to other crm objects to be set for each email.
Why this helps
A CRM decision can lose its context when call outcomes are not recorded where the team tracks prospects.
- Make supplied outcome context available in HubSpot
- Help teammates understand why a next step was chosen
- Support more consistent prospect handoffs
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 email engagement record from each webhook with a Callingly outcome summary and valid associations.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real outcome and verify the saved context.
Questions about this workflow
Does this update an existing HubSpot record?
No. The selected action creates email engagement records. It does not update existing contacts or deals.
What outcome information should the webhook carry?
Include the outcome and any relevant summary or follow-up context your team wants to preserve.
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.