Turn queued launch briefs into campaign records
Create campaign records as part of a regular launch planning routine.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Launch briefs waiting in a queue may not receive a campaign record until someone remembers the setup.
- Make campaign setup part of a routine
- Reduce launch coordination overhead
- Keep queued launch plans visible
Setup
Build it in a few focused steps.
- 1Connect BytePlus Ark and HubSpot once in Notis.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Ask Notis to create a HubSpot campaign for each queued launch brief made available to it, using supplied campaign details.
- 4Choose the Notis cron trigger and set the recurring schedule, then select where run reports should go.
- 5Test with one real launch brief and inspect the campaign in HubSpot.
Questions about this workflow
Will this find launch briefs on its own?
The listed BytePlus Ark capabilities do not include trigger events. Make the queued briefs available to the scheduled automation.
Can it create campaigns for unrelated requests?
Describe the launch criteria in your instruction so Notis processes only matching briefs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BytePlus Ark to Hubspot. A trigger fires from one place; an action lands in another.
BytePlus Ark 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.
BytePlus Ark 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.