Skip to content
Notis

Send Customer.io incident updates from Jira

Get a customer incident update moving from the Jira issue that records it, without switching tools to start the broadcast.

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

Trigger Broadcast

Tool to manually trigger a broadcast. use when you need to override the default audience and provide personalization data after confirming the broadcast id.

Why this helps

When an incident is logged, preparing and starting a customer update can get lost among investigation work and handoffs.

  • Start an approved incident broadcast from the Jira record.
  • Keep the incident update tied to the issue that prompted it.
  • Reduce the chance of delaying a customer communication while coordinating response work.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Customer.io once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3In one instruction, tell Notis to use a new issue only when it documents a customer-impacting incident and provides the approved broadcast ID, audience override, and personalization data, then trigger that broadcast.
  • 4Pick Jira New Issue as the trigger and choose where run reports should go.
  • 5Test with one real issue that contains the approved broadcast details.

Questions about this workflow

Will this broadcast every new Jira issue?

The instruction should limit broadcasts to issues that document a customer-impacting incident and include the required approved broadcast and audience details.

Does Customer.io need a broadcast to exist already?

Yes. The Trigger Broadcast action needs an identified broadcast. Provide its ID and the intended audience override and personalization data in the issue or instruction.

Can Notis determine which customers were affected?

Only if the issue or your instruction supplies that audience information. Do not assume Jira provides a customer impact list.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Customerio. A trigger fires from one place; an action lands in another.

Jira triggers

Customerio actions

Recurring trigger

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

TriggerScheduled

Suppress Customer Profile

Tool to suppress a person. use when you need to permanently delete a customer's profile and prevent them from being re-added.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Integrations

Tool to retrieve a list of integrations in your workspace. use when you need to discover configured integrations.

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

Get Messages

Tool to retrieve a list of messages sent from your workspace. use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Get Segment Details

Tool to retrieve details of a specific segment. use after identifying the segment id from list segments.

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

Get Segment Membership

Tool to retrieve people in a specific segment. use when you need to page through segment membership after identifying segment id.

ActionInstant

Get Segments

Tool to retrieve a list of segments in your workspace. use when you need to fetch all segments after configuring segment rules.

ActionInstant

Get Trigger

Tool to retrieve details about a specific trigger. use after triggering a broadcast to confirm its status and metadata.

ActionInstant

Get Triggers

Tool to retrieve a list of triggers for a specific broadcast. use after identifying broadcast id to inspect associated triggers.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Customerio, 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 Customerio.