Keep project scope changes visible to account owners
Preserve the reason and context for a meaningful project change where the relationship team can find it.
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
Scope changes can affect client expectations and follow-up, yet be difficult for account owners to spot.
- Make important project changes visible in client history.
- Reduce context hunting across tools.
- Create a record without sending a message.
Setup
Build it in a few focused steps.
- 1Connect Bonsai and HubSpot once in Notis.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to summarize the scope change from the webhook context and create a HubSpot email engagement record with a valid association when available.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real scope change.
Questions about this workflow
Will this send the summary to the client?
No. It creates a HubSpot email engagement record for CRM history and does not send email.
What qualifies as a scope change?
Specify the Bonsai status or change details that should trigger the webhook. Notis cannot infer a change that is not present in the available data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bonsai to Hubspot. A trigger fires from one place; an action lands in another.
Bonsai 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.
Bonsai 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.