Keep shipment update context in HubSpot
Send a shipment update to a Notis webhook and have it logged in HubSpot as an email record with the relevant association details.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a batch of emails
Creates multiple email objects for record-keeping (does not send emails) within hubspot crm in a single batch, allowing properties and associations to other crm objects to be set for each email.
Why this helps
Shipment updates may be visible in Baselinker but absent from the HubSpot record your team checks for customer context.
- Keep shipment context alongside related CRM activity.
- Reduce manual CRM history updates.
- Log updates without asking the automation to send a customer email.
Setup
Build it in a few focused steps.
- 1Connect Baselinker and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a HubSpot email record from each incoming shipment update and associate it with the supplied existing CRM record.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real shipment update and confirm its record and association in HubSpot.
Questions about this workflow
Does creating this record send an email?
No. This action creates an email engagement record for CRM history; it does not send an email.
What does the request need for an association?
It needs valid existing HubSpot record IDs and association type IDs. Provide these in the request or make them available to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Baselinker to Hubspot. A trigger fires from one place; an action lands in another.
Baselinker 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.
Baselinker 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.