Create HubSpot companies from transcript research
Capture organizations surfaced in calls so company research does not remain trapped in audio notes.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a batch of companies
Creates multiple company records in hubspot crm in a single batch operation, processing up to 100 companies per request.
Why this helps
Useful company names and context mentioned on calls can be lost before anyone adds them to the CRM.
- Capture organizations explicitly named in the transcript.
- Add a concise description of why the company came up.
- Surface uncertainty rather than filling company details with guesses.
Setup
Build it in a few focused steps.
- 1Connect AssemblyAI and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to create company records only for organizations clearly identified in the transcript, and to report uncertain or missing details.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real transcript and inspect the company records.
Questions about this workflow
Can it find companies not mentioned in the transcript?
This workflow uses transcript content only. It cannot reliably identify organizations that the transcript does not name.
How should duplicates be handled?
Ask Notis to check for an existing matching company before creating a record, and to report ambiguous matches for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AssemblyAI to Hubspot. A trigger fires from one place; an action lands in another.
AssemblyAI 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.
AssemblyAI 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.