Keep scheduled incident follow-up on the CRM record
Turn the incident follow-up information you provide to Notis into a HubSpot record on a recurring schedule.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Follow-up notes can remain scattered across incident channels instead of being available in account records.
- Create a predictable record for periodic follow-up.
- Keep supplied incident context in HubSpot.
- Reduce manual copying into customer records.
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.
- 3Tell Notis to create an email record from the incident follow-up details provided for each run and associate supplied CRM object IDs.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test with one real follow-up example and check the HubSpot record.
Questions about this workflow
Does the schedule fetch Better Stack incidents automatically?
The trigger is a Notis schedule. Provide the incident follow-up information to Notis for each run unless your setup supplies it through another supported input.
Does the action send a customer email?
No. It creates an email record in HubSpot without sending an email.
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.