Keep track of support pipeline changes
Have Notis check the audit history for an existing HubSpot ticket pipeline on a schedule and report the changes worth reviewing.
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
Support process changes can affect open work, but the reasons and timing are easy to miss in day-to-day operations.
- Review support pipeline changes regularly.
- Keep process changes from going unnoticed.
- Reduce manual audit history checks.
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to audit an existing ticket pipeline and summarize the returned changes that matter to support follow-up.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real ticket pipeline audit and review its history summary.
Questions about this workflow
Can the ticket pipeline be created by this workflow?
No. The pipeline audit action reads change history for a specific existing pipeline.
What does the automation need to know?
Provide the existing pipeline ID and the supported object type, such as tickets.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BrowserAct to Hubspot. A trigger fires from one place; an action lands in another.
BrowserAct 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.
BrowserAct 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.