Bring landing page changes into campaign planning
When a landing page shifts in a meaningful way, give the update a campaign record and a place in the plan.
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
Landing pages can change without anyone updating the campaign context around them.
- Check campaign pages regularly.
- Create a campaign record for meaningful changes.
- Keep launch coordination connected to the live page.
Setup
Build it in a few focused steps.
- 1Connect Apiflash and HubSpot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis which landing page to monitor and when a change merits creating a HubSpot campaign.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real landing page update.
Questions about this workflow
Can the schedule detect every page change immediately?
No. The schedule starts periodic checks, so a change is found on a later scheduled run.
What determines whether a campaign is created?
Your instruction should describe the kinds of landing page changes that merit a campaign. Notis can analyze what it retrieves, but your launch objective should be supplied.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiflash to Hubspot. A trigger fires from one place; an action lands in another.
Apiflash 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.
Apiflash 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.