Keep sensitive details out of new Jira issue summaries
A new ticket should move work forward, not spread private details. Have Notis anonymize sensitive text before it is shared.
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
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Why this helps
Founders often discover personal or confidential details in a ticket only after it has already been copied into another tool.
- Reduce exposure of sensitive strings when issue details are passed onward.
- Avoid manually reviewing every new ticket for private text.
- Keep the original issue as the source while using anonymized values in downstream handling.
Setup
Build it in a few focused steps.
- 1Connect Jira and Anonyflow once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, tell Notis which sensitive strings from a new issue to anonymize with Anonyflow and how to use the returned values.
- 4Choose the Jira New Issue trigger, then select where run reports should go.
- 5Test with one real issue that contains safe sample sensitive text.
Questions about this workflow
Does this edit or redact the Jira issue?
The Anonyflow action anonymizes supplied strings and returns values. This event and action do not describe writing changes back to the Jira issue.
Can it anonymize a whole nested Jira issue automatically?
No. Anonymize Value supports a list of strings, not nested structures. Tell Notis which strings to process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Anonyflow. A trigger fires from one place; an action lands in another.
Jira triggers
Anonyflow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Deanonymize Packet
Tool to deanonymize a json data packet using your private key. use after receiving an anonymized packet to recover specific fields.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Deanonymize Value
Tool to deanonymize one or more anonymized string values. use when you need to recover the original plaintext values after encryption-based anonymization. example: `deanonymizevalue().execute(deanonymizevaluerequest(data=["<anonymized string>"]))`
New Project
Triggered when a new project is added in Jira
Test Connection
Tool to test the connection to the anonyflow api. use when verifying that the anonyflow service is reachable and operational before performing anonymization tasks. example: `testconnection().execute(testconnectionrequest())`
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.
Connect any two apps with Notis in the middle.
Jira and Anonyflow, 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 Anonyflow.