Keep BotMape escalation context with the customer record
Give the teammate handling an escalation the conversation context without making them search through the entire agent 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
Escalation context can be missing when a customer record only shows the final handoff.
- Preserve supplied escalation summaries in CRM history.
- Make the reason for a handoff easier to find.
- Require an existing valid CRM association for the record.
Setup
Build it in a few focused steps.
- 1Connect BotMape and HubSpot once in the Notis portal.
- 2Create an automation and ask Notis to summarize supplied escalation context into a HubSpot email engagement record.
- 3Pick a Notis webhook trigger and choose where run reports should go.
- 4Send one real escalation example with a valid HubSpot association and test it.
- 5Review the engagement on the associated CRM record.
Questions about this workflow
Does this notify or email the assigned person?
The selected action creates an email engagement record and does not send an email. Use your report channel to see the run report.
What should the webhook send?
Send the BotMape escalation summary and valid association identifiers for an existing HubSpot record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to Hubspot. A trigger fires from one place; an action lands in another.
BotMape 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.
BotMape 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.