Create a HubSpot property group from a new Jira project
New engagements often need their own way of being tracked. Notis catches each new Jira project and creates a HubSpot property group to hold the fields that matter for it, so your CRM stays organized instead of accumulating one-off properties in a heap.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Create a new property group
Creates a new, empty property group for a specified crm object type in hubspot, requiring a unique group name for that object type; properties must be added separately.
Why this helps
Every new engagement adds scattered custom fields to HubSpot, and the CRM slowly turns into a mess.
- Tracking structure exists before the first record does
- Custom fields stay grouped instead of scattered
- Your CRM stays tidy as engagements multiply
- Setup work happens automatically, not manually
Setup
Build it in a few focused steps.
- 1Connect Jira and HubSpot to Notis once in the portal.
- 2Ask Notis for your portal link and select New Automation.
- 3State the outcome: when a new Jira project starts, create a matching property group in HubSpot.
- 4Choose the New Project trigger and pick your run-report channel.
- 5Create a test project and confirm the property group appears in HubSpot.
Questions about this workflow
Does this add the properties too?
It creates the group as an organized container. Properties are added separately, which keeps your structure clean and intentional.
What triggers it?
A brand new project added in Jira. It does not run on issue changes.
Is any manual mapping needed?
No. You describe the outcome once and Notis handles the setup.
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.