Keep deployment follow-up in the customer record
Make deployment communication easier to find later by recording the follow-up as a HubSpot email engagement tied to existing CRM records.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create email
Creates a new email engagement record in hubspot, requiring portal-specific `properties` (e.g., `hs timestamp` as a utc millisecond timestamp), and that association `to id`s and `associationtypeid`s are valid and existing.
Why this helps
Deployment updates and customer history can end up separated across tools.
- Keep deployment follow-up in the CRM record
- Make communication context easier to find
- Reduce manual record keeping after a release
Setup
Build it in a few focused steps.
- 1Connect Buildkite and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, instructing Notis to create a HubSpot email engagement for a deployment follow-up request.
- 3Choose a Notis webhook and send a request containing the engagement details and valid existing association IDs and association type IDs.
- 4Choose where run reports should go, then test with one real request and verify the record in HubSpot.
Questions about this workflow
Does creating this record send an email?
No. This action creates an email engagement record in HubSpot; it does not send an email.
What must associations reference?
The association IDs and association type IDs must be valid and exist in the HubSpot account.
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.