Content & Documents · Integration
Percolate
Add Percolate to your product for your customers, and give your AI agents governed access to it.
Embed a Percolate integration so your customers can work their own marketing content from inside your product rather than exporting it. Percolate is marketing content operations, now part of the Seismic platform, and the records teams work with are campaigns, the content items planned inside them, the assets attached to that content, and the approval steps a piece has to clear before it goes out. Permissions and versions are easy to get subtly wrong in a content system, so access runs through each customer's own grant and your product cannot read content the connected account could not read itself. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Percolate account so your product reads their campaigns, content items and attached assets in place.
Create or update a content item from your product so work started elsewhere lands in the customer's own marketing plan.
Read approval state so your product can show whether a piece of content is cleared to publish.
Respect each customer's own permissions and asset structure as configuration rather than a special case in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the approved asset for a campaign within scoped permissions, with every read audited.
An agent drafts or updates a content item and leaves it for a human to approve, with the write attributed.
An agent reports which content items are still waiting on approval before a launch date.
Example prompt
List content scheduled for next week that has not cleared approval and show who it is waiting on.
Set up Percolate in 4 steps
- 01Open the Percolate connector from your fastn dashboard.
- 02Have each customer authorise their own Percolate account.
- 03Map the campaigns, content types and asset fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Percolate integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Percolate integration without building it. Your customers connect their own Percolate account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Percolate update is not your on-call problem.
- One integration serves your product and your agents. The same governed Percolate connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
ContentfulWorks well with
Hootsuite
MarketoOften used alongside
Tools the same teams tend to run next to Percolate, across other categories.
Shopify
Stripe
Jira
AsanaPercolate integration FAQ
How do I add a Percolate integration to my product?
Enable the Percolate connector in your fastn dashboard, then let each customer authenticate their own Percolate account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Percolate client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Percolate account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Percolate account and only ever sees their own files, documents and versions. 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 Percolate 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 finds the approved asset for a campaign within scoped permissions, with every read audited.
Who maintains the Percolate integration?
fastn does. When Percolate 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.
Whose permissions does the Percolate integration run under?
Each customer's own Percolate grant. Where Percolate holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Percolate automatically?
Where Percolate supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Percolate integration?
A common starting point: connect their own Percolate account so your product reads their campaigns, content items and attached assets in place. 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 Percolate integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Percolate does not change your per-connector cost. You can start free with 3 connected accounts.
Add Percolate to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.