Keep market alerts with the right HubSpot records
Send an alert to Notis and keep the headline, source, and context alongside the HubSpot records your team already uses.
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
Market news arrives in one place while customer context and follow-up live in another, making useful alerts easy to lose.
- Keep important headlines with relevant CRM history.
- Reduce manual copying between market news and HubSpot.
- Give teammates a shared place to review alert context.
Setup
Build it in a few focused steps.
- 1Connect Benzinga and HubSpot once in the Notis portal.
- 2Create an automation by telling Notis to log incoming Benzinga alerts as HubSpot email engagement records.
- 3Pick the webhook trigger and provide the alert through an HTTP request.
- 4Choose where Notis should send run reports.
- 5Test with one real alert and valid existing HubSpot association IDs.
Questions about this workflow
Does this send a marketing email?
No. It creates HubSpot email engagement records for record-keeping and does not send emails.
How are alerts linked to HubSpot records?
Include valid existing association IDs and association type IDs in the webhook data. Notis can use those supplied details when creating the record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Benzinga to Hubspot. A trigger fires from one place; an action lands in another.
Benzinga 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.
Benzinga 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.