Add useful context to pipeline change reviews
Review the pipeline history with a concise view of relevant market developments that could help explain what changed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Audit pipeline changes by id
Retrieves a reverse chronological audit log of all changes for a specific, existing hubspot crm pipeline, which is identified by its `pipelineid` and a valid `objecttype` that supports pipelines (e.g., 'deals', 'tickets').
Why this helps
Pipeline audits show what changed, but teams still spend time searching for outside context before discussing it.
- Bring external context into pipeline reviews
- Focus attention on changes that may need discussion
- Keep a recurring audit easier to scan
Setup
Build it in a few focused steps.
- 1Connect Autom and HubSpot once in the Notis portal.
- 2Create an automation in Automations and name the pipeline review.
- 3Tell Notis to audit the specified HubSpot pipeline, research relevant market context with Autom, and summarize findings without assuming causation.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real pipeline and confirm the audit and research are clearly distinguished.
Questions about this workflow
Can the workflow prove a market event caused a pipeline change?
No. It can report a possible connection, but the audit and research do not establish causation.
What if the pipeline has no changes?
The report can say that the audit returned no relevant changes for the review period.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Autom to Hubspot. A trigger fires from one place; an action lands in another.
Autom 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.
Autom 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.