Content & Documents · Integration
Placid
Add Placid to your product for your customers, and give your AI agents governed access to it.
Placid works from templates built in its editor, where every element is a named layer, and the API generates output by posting a template identifier plus a layers object keyed by those exact layer names. Rename a layer in the editor and every existing API call silently stops filling it, which is the most common breakage in production. There are separate endpoints for images, PDFs and videos, and by default a request is queued and returns a status you poll until a finished URL appears, rather than returning the file inline. Video and PDF jobs in particular take long enough that treating the first response as the result produces empty output. fastn holds each customer's Placid token, keeps their template and layer maps separate per tenant, and handles credential upkeep as keys rotate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Placid account so generated assets use their templates and their quota
Render personalised social or ad images from record data at the moment a campaign is created
Produce branded PDF certificates or summaries from a template rather than hand-built HTML
Regenerate a customer's asset set automatically when their template or brand colours change
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent generate assets only from approved templates and reject unknown layer names
Have an agent poll a queued render and return the finished URL once it is ready
Audit per tenant which templates an agent used and what layer values it supplied
Example prompt
Generate the launch announcement image from our Placid template with this headline and product shot.
Set up Placid in 4 steps
- 01Enable the Placid connector from your fastn dashboard.
- 02Have each customer authorise their own Placid account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Placid integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Placid integration without building it. Your customers connect their own Placid 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 Placid update is not your on-call problem.
- One integration serves your product and your agents. The same governed Placid 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
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Placid, across other categories.
Shopify
Stripe
Jira
AsanaPlacid integration FAQ
How do I add a Placid integration to my product?
Enable the Placid connector in your fastn dashboard, then let each customer authenticate their own Placid account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Placid client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Placid account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Placid 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 Placid integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent generate assets only from approved templates and reject unknown layer names
Who maintains the Placid integration?
fastn does. When Placid 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 Placid integration run under?
Each customer's own Placid grant. Where Placid 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 Placid automatically?
Where Placid 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 Placid integration?
A common starting point: let a customer connect their own Placid account so generated assets use their templates and their quota. 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 Placid integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Placid does not change your per-connector cost. You can start free with 3 connected accounts.
Add Placid to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.