Turn a Buildkite release request into HubSpot deals
Keep commercial follow-up attached to the release that prompted it. Send a release request to Notis and create the related HubSpot deals in one pass.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create batch of deals
Creates multiple deals in hubspot crm; ensure any associated object ids, deal stages, and pipeline ids specified are valid and exist within the hubspot account.
Why this helps
Release work can create customer commitments that never make it into the deal pipeline.
- Record release-driven opportunities without switching tools
- Keep deal context tied to the release request
- Reduce missed commercial follow-up
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 a name and an instruction to create HubSpot deals from approved release requests.
- 3Choose a Notis webhook as the trigger and send the release request to its endpoint.
- 4Choose where run reports should go, then test with one real release request and valid HubSpot pipeline and stage details.
Questions about this workflow
Does Buildkite provide a trigger event for this workflow?
No Buildkite trigger events are available here, so the workflow starts when an HTTP request reaches its Notis webhook.
Can this workflow invent a HubSpot pipeline or deal stage?
No. Supply valid pipeline and stage details in the request or the instruction so HubSpot can create the deals.
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.