Keep inquiry email context with HubSpot records
Send inquiry details to Notis and create a HubSpot email engagement linked using valid supplied association identifiers.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create email
Creates a new email engagement record in hubspot, requiring portal-specific `properties` (e.g., `hs timestamp` as a utc millisecond timestamp), and that association `to id`s and `associationtypeid`s are valid and existing.
Why this helps
Inquiry context can be lost when it is not recorded alongside the relevant CRM record.
- Keep inquiry details near CRM history
- Avoid manual engagement entry
- Catch missing association information
Setup
Build it in a few focused steps.
- 1Connect Builder.io and HubSpot once in Notis.
- 2Create an automation and describe when an inquiry should be logged as an email engagement.
- 3Choose a Notis webhook and send one real inquiry with valid association details.
- 4Choose where run reports should go.
- 5Test with one real example and verify the engagement is associated correctly.
Questions about this workflow
Will this send an email to the inquiry contact?
No. It creates an email engagement record in HubSpot.
Can the workflow guess which record to associate?
Tell Notis to use supplied valid identifiers and report when it cannot determine a valid association.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Builder.io to Hubspot. A trigger fires from one place; an action lands in another.
Builder.io 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.
Builder.io 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.