Create a batch of HubSpot campaigns from a new Jira project
A serious launch needs more than one campaign. Notis watches for new Jira projects and creates a batch of HubSpot campaigns at once, so the full go-to-market structure exists on day one instead of being assembled piece by piece under deadline.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Create a batch of campaigns
Creates up to 50 marketing campaigns in a single batch operation.
Why this helps
Multi-channel launches require several campaigns that never get built until the last panicked week.
- The whole launch structure exists from day one
- Multi-channel planning is scaffolded, not scrambled
- You avoid building campaigns one at a time under pressure
- Roadmap and marketing stay in lockstep
Setup
Build it in a few focused steps.
- 1Connect Jira and HubSpot to Notis once in the portal.
- 2Grab your portal link from Notis and start a New Automation.
- 3State the outcome: when a new Jira project starts, create a set of matching HubSpot campaigns.
- 4Choose the New Project trigger and pick the channel for run reports.
- 5Create a test project and confirm the campaigns appear in HubSpot.
Questions about this workflow
How many campaigns get created?
You describe the set you want in your instruction and Notis creates them together in one batch.
Does this run on new issues?
No. It fires only when a new project is added in Jira.
Is manual configuration involved?
No. Your single plain-language instruction defines everything.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Hubspot. A trigger fires from one place; an action lands in another.
Jira triggers
Hubspot actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Add asset association
Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Not just Jira and Hubspot. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Hubspot.