Data & Storage · Integration
Anonyflow
Add Anonyflow to your product for your customers, and give your AI agents governed access to it.
Embed an Anonyflow integration so your customers can apply data privacy and anonymisation steps to their own data from inside your product, with credentials held per tenant and every call logged. Because payload shapes differ per customer, field mapping is configuration rather than code, and large jobs are throttled so an import does not exhaust a customer's allowance. fastn handles each customer's authentication and the API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Anonyflow account so privacy operations run under their credentials.
Submit data from your product for processing and read the result back into your workflow.
Map the fields your product sends per customer, so an unusual data shape needs no release from you.
Trigger the next step in your product when a submitted job completes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent submits a payload for processing within governed permissions and records what was sent.
An agent reads the status and result of a job before continuing a workflow.
An agent reacts to a completed job and hands the output to the next step.
Example prompt
Show jobs submitted in the last day, their status, and any that did not complete.
Set up Anonyflow in 4 steps
- 01Open the Anonyflow connector from your fastn dashboard.
- 02Have each customer authenticate their own Anonyflow account.
- 03Map the fields and payloads your product sends, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Anonyflow integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Anonyflow integration without building it. Your customers connect their own Anonyflow account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Anonyflow update is not your on-call problem.
- One integration serves your product and your agents. The same governed Anonyflow connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
AppViewX
NotionOften used alongside
Tools the same teams tend to run next to Anonyflow, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceAnonyflow integration FAQ
How do I add an Anonyflow integration to my product?
Enable the Anonyflow connector in your fastn dashboard, then let each customer authenticate their own Anonyflow account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Anonyflow client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Anonyflow account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Anonyflow account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Anonyflow integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent submits a payload for processing within governed permissions and records what was sent.
Who maintains the Anonyflow integration?
fastn does. When Anonyflow changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Anonyflow integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Anonyflow reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Anonyflow integration?
A common starting point: connect their own Anonyflow account so privacy operations run under their credentials. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Anonyflow integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Anonyflow does not change your per-connector cost. You can start free with 3 connected accounts.
Add Anonyflow to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.