What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
Integrations
Connect Agility to the rest of your stack: composable architecture, the five places an integration plugs in, proven patterns for search, commerce, CRM, DAM and more, and how AI helps you design, build and run it.
No single platform does everything well. Your commerce platform is great at carts, your CRM at leads, your search engine at relevance. Agility is great at content: modeling it, editing it, approving it and delivering it fast. A composable architecture lets each system do its job and connects them through APIs, so you can swap one piece without rebuilding the rest.
This page explains where Agility plugs into that architecture, which pattern fits which job, and how AI agents can help you design, build and run the whole thing.
In a composable stack, each capability comes from a service that's best at it, and your front end puts them together.
| Capability | Typically owned by | How it meets Agility content |
|---|---|---|
| Pages, navigation, articles, campaigns | Agility | Your front end reads them from the Fetch or GraphQL API |
| Products, prices, cart, checkout | Commerce platform | Agility stores product IDs; the front end looks up the rest |
| Search | Search service | Agility webhooks keep the index current |
| Leads, contacts, forms | CRM or form provider | The front end sends submissions straight to the CRM |
| Images, video, brand assets | Agility media, or a DAM | A picker app stores the asset reference |
| Private files (member downloads, gated PDFs) | Your own Azure Blob Storage or AWS S3 | A Secure Files app stores the file reference; your front end gives allowed readers a short-lived signed URL |
| Documents managed in Microsoft 365 | SharePoint | Agility stores a link |
| Sign-in and audiences | Identity provider | Your front end decides what each reader sees |
| Analytics and experiments | Analytics platform | The front end reports; apps show results to editors |
Good patterns to follow:
How Agility Works: A 10-Minute Architecture Tour and Reference Architectures show complete designs.
Most integrations use one or two of these.
| Where | Direction | Use it for | Start here |
|---|---|---|---|
| 1. Your front end or app | Agility → your code | Combining Agility content with other services at render time | Content Fetch API, GraphQL API |
| 2. Webhooks | Agility → other systems | Reacting when content is published, unpublished or changes workflow state | Webhooks |
| 3. Management API | Other systems → Agility | Importing, syncing or updating content from a system of record | Content Management API |
| 4. Apps inside Agility | Inside the editor | Custom fields, pickers and sidebars that bring other systems into the editing experience | Apps SDK |
| 5. AI agents (MCP) | Both ways | Letting AI assistants read, create and manage content with your permissions | Agility CMS MCP Server |
This is where composition usually happens. Your site reads pages and content from Agility and calls other services for the rest: product data from commerce, results from search, personalization from your audience data.
Webhooks tell other systems the moment content changes, so nothing has to poll. They clear caches, update search indexes, trigger builds and post to social channels.
The Management API writes to Agility: create and update content, upload media, manage pages and run workflow. Use it to import content, keep a list in sync with a system of record, or automate publishing.
Apps bring other systems into the editor, so editors don't copy and paste IDs between browser tabs. A product picker, a DAM browser, a secure file field, a translation button or an analytics sidebar are all apps.
The Agility CMS MCP Server lets AI assistants such as Claude, ChatGPT or Microsoft 365 Copilot work with your instance: read content, create models, draft items and move them through workflow, always with the signed-in user's permissions. See Connect the Agility MCP Server to Microsoft 365 Copilot.
| You want to | Pattern | Guides |
|---|---|---|
| Add site search | Webhooks keep an index current; the front end queries it | Indexing Agility Content for Search, Algolia, Coveo, Elastic, Azure AI Search |
| Sell products | Commerce owns the catalog; Agility stores product IDs; a picker app helps editors | Reference Architecture: Headless Commerce, BigCommerce, Commercetools |
| Capture leads | The front end posts forms to your CRM or form provider | HubSpot, Salesforce Sales Cloud, Formstack, TypeForm |
| Manage images and video | Use Agility media, or a DAM through a picker app | Cloudinary, Bynder, Vimeo, YouTube |
| Protect files and downloads | Files stay in your private cloud storage; editors attach them with a secure file field; the front end checks the reader and hands out a short-lived signed URL | Secure Files - Azure, Secure Files - AWS, Reference Architecture: Member Portal and Intranet |
| Translate content | A translation app or automation writes to other locales | DeepL, Google Translate, Zapier Translate |
| Run an intranet | A Microsoft front end reads Agility; documents stay in SharePoint | Microsoft Power Pages, SharePoint, Reference Architecture: Member Portal and Intranet |
| Measure and experiment | The front end reports; an app shows results to editors | PostHog, Google Analytics |
| Publish to social channels | Webhooks trigger posts when content goes live | Publishing to Social Channels |
| Deploy and rebuild | Webhooks trigger builds or cache clears on your host | Vercel, Netlify |
| Serve many channels | One content hub, many front ends | Building a Content Hub, Reference Architecture: Multi-Channel Delivery |
A Secure Assets app for the Agility marketplace is on the roadmap. Until it ships, use the Secure Files apps for Azure or AWS.
AI agents are good at exactly the work integrations need: reading APIs, writing glue code, mapping fields and checking results. Use them at every stage, and keep people in charge of what goes live.
| Stage | What an agent does | Guides |
|---|---|---|
| Evaluate and design | Connects to your instance, explains what's there, proposes content models and an integration plan | Evaluate Agility with an AI Agent in 30 Minutes, Make Your Content Model Agent-Friendly |
| Build the integration | Writes front-end code, webhook handlers and sync scripts against Agility and the other system's API | Building an Agility Site with AI Coding Tools, Agility Skills for Your Coding Agent, Writing an AGENTS.md for Agility Projects |
| Build apps for editors | Scaffolds and builds Agility apps with the Apps SDK | Building Apps with AI Coding Tools, How We Built the Google Analytics Page Sidebar with Claude |
| Move content in | Inventories the old system, maps fields and imports a reviewable sample, then writes the bulk import script | Migrating Content into Agility with an AI Agent, Migrating to Agility |
| Test and ship | Checks the integration end to end, in the browser and in CI | Letting Agents Drive the Browser, Test Your Agility Integration in CI, From Proof of Concept to Production |
| Run day to day | Drafts and updates content through the MCP Server, for editors to review and publish | Agility CMS MCP Server, MCP and Agility Gotchas to Know Before You Build |
| Serve AI readers | Makes your content easy for AI assistants and search to use | Search for People and for AI Agents, Build an MCP Server over Your Agility Content, Making Your Agility-Powered Site Readable by AI |
Guardrails that keep this safe:
Managing a Team of Coding Agents and Training Your Team to Build with Agents cover running this as a team.
Working on an integration and want a second opinion on the approach? Contact us and we'll help.
