Add a privacy pass to ClickUp status handoffs
A status change can mark the moment work moves to another person or process. Use it to anonymize selected sensitive strings in the task text.
Trigger
Task Status Updated
Triggers when a task's status changes. `changes[]` carries `StatusChange` entries only — ClickUp pre-filters server-side by event type. Lower traffic than subscribing to `CLICKUP_TASK_UPDATED` and pattern-matching `StatusChange`.
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
Handoffs happen quickly, and sensitive details can travel with a task unless someone remembers to clean them up.
- Place privacy work at a meaningful handoff point.
- Reduce repeated manual checks on status transitions.
- Prepare chosen task text for safer sharing.
Setup
Build it in a few focused steps.
- 1Connect ClickUp and Anonyflow once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, describe which task strings to anonymize when the status changes and how to use the result.
- 4Pick the ClickUp Task Status Updated trigger and choose where run reports should go.
- 5Test with one real status change and sample sensitive text.
Questions about this workflow
Can I choose a particular status in the trigger setup?
The documented Notis flow lets you pick the event trigger and describe the desired outcome in your instruction. It does not provide a field-mapping or filter setup screen.
Does status change include the full task description?
The listed event is a task status update. Have Notis use available task data and specify the text values needed; do not assume unavailable fields are present.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Anonyflow. A trigger fires from one place; an action lands in another.
Clickup 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.
Folder Created
Triggers when a new Folder is created.
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>"]))`
Folder Deleted
Triggers when a Folder is deleted.
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())`
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
List Created
Triggers when a new List is created.
List Deleted
Triggers when a List is deleted.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Connect any two apps with Notis in the middle.
Clickup 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.