Skip to content
Notis

Handle approved suppression requests from Jira

For an explicitly approved request, use the Jira issue as the record that prompts Customer.io profile suppression.

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

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.

Why this helps

A privacy or compliance request can be easy to miss when the request record and the customer profile live in separate tools.

  • Route an explicitly approved suppression request to Customer.io.
  • Keep the request connected to its Jira issue for review.
  • Avoid acting on unrelated Jira issues by requiring clear approval and identity details.

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 permanently suppress a profile only when the new issue explicitly confirms approval for suppression and identifies the exact person.
  • 4Pick Jira New Issue as the trigger and choose where run reports should go.
  • 5Test with one real approved request and confirm the identity is unambiguous.

Questions about this workflow

Will this suppress profiles for every Jira issue mentioning a customer?

No. The instruction should require an explicit approved suppression request and an unambiguous person identity.

Can suppression be undone automatically?

The available action permanently suppresses a profile and prevents re-addition. Do not use it for routine account updates or uncertain requests.

What if the Jira issue does not identify the person clearly?

Do not suppress a profile. The request needs to supply an exact identity that Notis can use to identify the Customer.io person.

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.