Content & Documents · Integration
Agility CMS
Add Agility CMS to your product for your customers, and give your AI agents governed access to it.
Agility CMS separates reading from writing: the Fetch API lives on api.aglty.io and needs the instance GUID, a locale and an APIKey header on every call, while content management is a different service with its own auth. The key you use decides what you see, because a fetch key returns published content only and a preview key returns unpublished and staged content from the same paths, so a working integration that shows stale content is nearly always the wrong key rather than a caching bug. Content is addressed either as a single content item by id or as a content list by its reference name, and pages and the sitemap are separate endpoints again, so rendering a page means combining several calls. Instances can be pinned to a region, which changes the hostname to something like api-ca.aglty.io, and calls to the wrong regional host will not find the instance. fastn stores each customer's GUID, locale and keys as one connection and keeps it working as keys are rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Agility CMS instance, including its GUID and locale, so your product reads their content
Pull a content list by reference name to populate a customer facing page in your app
Offer a preview mode that swaps in the preview key so editors see unpublished content before it goes live
Resolve media and asset URLs from the instance so images stay in step with the customer's CMS
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent fetch a content item by id and summarise what changed since the last published version
Have an agent list the entries in a named content list so an editor can find the right one in conversation
Audit per tenant which instance and which key type an agent read from, so preview content never leaks into published output
Example prompt
What is currently published in the blog posts list for this instance?
Set up Agility CMS in 4 steps
- 01Enable the Agility CMS connector from your fastn dashboard.
- 02Have each customer authorise their own Agility CMS 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 Agility CMS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Agility CMS integration without building it. Your customers connect their own Agility CMS 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 an Agility CMS update is not your on-call problem.
- One integration serves your product and your agents. The same governed Agility CMS 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 Agility CMS, across other categories.
Shopify
Stripe
Jira
AsanaAgility CMS integration FAQ
How do I add an Agility CMS integration to my product?
Enable the Agility CMS connector in your fastn dashboard, then let each customer authenticate their own Agility CMS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Agility CMS client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Agility CMS account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Agility CMS 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 Agility CMS 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 fetch a content item by id and summarise what changed since the last published version
Who maintains the Agility CMS integration?
fastn does. When Agility CMS 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 Agility CMS integration run under?
Each customer's own Agility CMS grant. Where Agility CMS 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 Agility CMS automatically?
Where Agility CMS 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 Agility CMS integration?
A common starting point: let a customer connect their own Agility CMS instance, including its GUID and locale, so your product reads their content. 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 Agility CMS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Agility CMS does not change your per-connector cost. You can start free with 3 connected accounts.
Add Agility CMS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.