Protect Sensitive Text Submitted to a Webhook
Send a request to start a Notis run, then anonymize the sensitive strings it provides before using those values elsewhere.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Sensitive text submitted for processing can be copied onward before anyone has time to redact it.
- Start the process from an HTTP request.
- Use one prompt to specify the sensitive string values that need protection.
- Reduce hand redaction before downstream use.
Setup
Build it in a few focused steps.
- 1Connect Anonyflow once in the Notis portal and make sure your webhook sender can start a Notis automation.
- 2Create an automation in the portal or tell Notis from any channel, then provide a name and prompt.
- 3In one instruction, ask Notis to anonymize the sensitive string values supplied with each request before making them available for the intended next step.
- 4Pick the webhook trigger and choose a channel for run reports.
- 5Test with one real request containing example text that is appropriate to process.
Questions about this workflow
What starts this workflow?
An HTTP request starts a Notis webhook automation. The request must provide the text values the prompt asks Notis to process.
Can the webhook submit a nested object for anonymization?
Anonyflow's Anonymize Value action supports a string or array of strings, not nested structures. Supply values in a form the action supports.
Does this workflow define where anonymized values are stored?
No storage destination is specified by the available action. The prompt can describe the intended next step only if that destination is available in the automation context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gmail to Anonyflow. A trigger fires from one place; an action lands in another.
Gmail 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.
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
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 Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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())`
Connect any two apps with Notis in the middle.
Gmail 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.