Record Botpress follow-up context in HubSpot
Keep the reason for a follow-up close to the HubSpot record, using email engagement entries for CRM history.
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
When conversation context stays in Botpress, a teammate opening HubSpot may not know why a follow-up matters.
- Keep follow-up context with associated CRM records.
- Create engagement records in batches from a webhook payload.
- Give teammates a concise history to consult before reaching out.
Setup
Build it in a few focused steps.
- 1Connect Botpress and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis in one instruction to create HubSpot email engagement records from Botpress follow-up context and associate them with valid records when supplied.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real conversation and valid CRM associations.
Questions about this workflow
Does this action send the email?
No. It creates HubSpot email objects for record-keeping and does not send messages.
What is needed to associate a record?
The webhook must provide valid existing CRM object IDs and association type IDs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to Hubspot. A trigger fires from one place; an action lands in another.
Botpress 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.
Botpress 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.