Keep pipeline changes visible beside release work
Get a recurring view of changes to a HubSpot deal or ticket pipeline, with Buildkite release context supplied in your instruction when needed.
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 changes can be easy to miss when release and customer work compete for attention.
- Review pipeline changes without starting from scratch
- Spot shifts that may need release follow-up
- Receive a recurring report in a chosen channel
Setup
Build it in a few focused steps.
- 1Connect Buildkite and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, with an instruction to retrieve the audit log for a specific HubSpot pipeline.
- 3Choose a recurring Notis schedule and provide a valid pipeline ID and supported object type, such as deals or tickets.
- 4Choose where run reports should go, then test with one real pipeline audit.
Questions about this workflow
What information is needed to retrieve the audit log?
Provide the existing HubSpot pipeline ID and a supported object type, such as deals or tickets.
Does this schedule automatically find Buildkite releases?
No. Buildkite has no trigger events in this package. Include any release context you want Notis to consider in the instruction or input.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Hubspot. A trigger fires from one place; an action lands in another.
Buildkite 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.
Buildkite 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.