Record Botbaba follow-up commitments in HubSpot
Keep a searchable record of what someone promised to send or discuss after a chatbot conversation.
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
A promised follow-up is easy to drop when it is left in a conversation transcript.
- Keep a record of specific commitments made in chat.
- Preserve the conversation date and summary for reference.
- Make account follow-up easier to coordinate.
Setup
Build it in a few focused steps.
- 1Connect Botbaba and HubSpot once in the Notis portal.
- 2Create an automation and instruct Notis to create an email engagement record only when a specific follow-up commitment appears, using a valid UTC timestamp and available valid associations.
- 3Choose a webhook trigger and a report channel.
- 4Test with one real conversation containing a clear commitment and review the engagement.
Questions about this workflow
Does this action send the promised email?
No. It creates an email engagement record in HubSpot for record-keeping and does not send an email.
What if no timestamp or contact ID is available?
Provide the required timestamp and any associations from available conversation data or your instruction. Skip creation when required details are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botbaba to Hubspot. A trigger fires from one place; an action lands in another.
Botbaba 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.
Botbaba 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.