Turn launch requests into HubSpot campaigns
Let a webhook carry campaign requests into Notis, where the supplied plan can become a HubSpot marketing campaign record.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a campaign
Creates a new marketing campaign in hubspot with the specified properties, returning the created campaign data including its `campaignguid`.
Why this helps
Campaign requests arrive in different places, making it easy to lose ownership and launch context before work begins.
- Give campaign requests a home in HubSpot.
- Reduce repeat entry of launch information.
- Keep campaign setup connected to the original request.
Setup
Build it in a few focused steps.
- 1Connect BrowserAct and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to review the campaign request supplied to the webhook and create a HubSpot marketing campaign from its available details.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real campaign request and review the created campaign.
Questions about this workflow
Does this publish or launch the campaign?
No. This action creates a marketing campaign record in HubSpot. It does not itself publish campaign materials.
Can Notis add assets to the campaign too?
This workflow creates the campaign record. Associating existing assets requires a separate action, and those assets must already exist.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BrowserAct to Hubspot. A trigger fires from one place; an action lands in another.
BrowserAct 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.
BrowserAct 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.