Make incident response visible in HubSpot
Create a consistent CRM record when an incident needs customer, company, or deal follow-up.
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
Teams often resolve an incident but forget to preserve the response context where account owners can find it.
- Preserve the response summary in HubSpot.
- Associate the record with relevant existing CRM objects.
- Make post-incident follow-up easier to hand off.
Setup
Build it in a few focused steps.
- 1Connect Better Stack and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Ask Notis to create an email engagement summarizing the incident response and associate it with the supplied CRM object IDs.
- 4Choose the Better Stack webhook trigger and a channel for run reports.
- 5Test with one completed incident webhook and verify the engagement and associations.
Questions about this workflow
Does the action notify a customer?
No. It creates an email engagement record in HubSpot. It does not send an email.
What information is needed for associations?
The associated object IDs and association type IDs must be valid for the HubSpot account.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better stack to Hubspot. A trigger fires from one place; an action lands in another.
Better stack 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.
Better stack 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.