Skip to content
Notis

Draft a HubSpot marketing email from a new Jira issue

The blank page is where launch announcements go to die. Notis watches for new launch issues in Jira and creates a draft marketing email in HubSpot, so the announcement already exists as a draft the moment the work is scoped.

Trigger

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

Action

Create a new marketing email

Creates a new marketing email in hubspot, allowing comprehensive configuration of content, recipients, sender details, a/b testing, scheduling, web version, and other settings; the internal `name` for the email is required.

Why this helps

Launches ship without an announcement because writing the email always starts from nothing and gets pushed off.

  • Every launch gets an announcement draft ready to go
  • You start from a real draft, not a blank page
  • Marketing and product move in the same rhythm
  • Announcements stop being an afterthought

Setup

Build it in a few focused steps.

  • 1Connect Jira and HubSpot to Notis once in the portal.
  • 2Open your portal link and select New Automation.
  • 3State the outcome: when a new launch issue is created in Jira, draft a marketing email in HubSpot.
  • 4Choose the New Issue trigger and set your run-report channel.
  • 5File a test launch issue and confirm the draft email in HubSpot.

Questions about this workflow

Does it send the email automatically?

No. It creates a draft marketing email you can review and refine before anything goes out.

Can I limit it to launch issues only?

Yes. Describe which issues qualify in your instruction and Notis will interpret it.

Do I write the email content in Notis?

Notis drafts from the issue based on your instruction. You keep full control to edit in HubSpot.

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

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add asset association

Associates an existing asset ('form', 'object list', or 'external web url') with a specified hubspot marketing campaign.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Archive email

Archives the hubspot email specified by `emailid` by moving it to the recycling bin, making it inaccessible unless restored.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Archive a batch of emails by ID

Archives multiple hubspot crm emails by id; ids must exist as archiving is irreversible.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Jira 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.