# Agility CMS AI integration on Definable

> Agility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms.

## What this connects

Agility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms.

Vendor: https://agilitycms.com/

## Tools available

**9** tools available. First 9:

- `AGILITY_CMS_GET_API_TYPES` — Get API Types — Tool to retrieve all enum types used throughout the Agility CMS Management API. Use when you need to understand available values for status codes, types, permissions, and other enumerated fields.
- `AGILITY_CMS_GET_CONTENT_ITEM` — Get Content Item — Tool to fetch details of a content item by Content ID. Use when you need item fields and metadata from Agility CMS.
- `AGILITY_CMS_GET_CONTENT_LIST` — Get Content List — Retrieves a paginated list of content items by reference name from Agility CMS. Use this action to: - Fetch multiple content items of a specific type (e.g., blog posts, products, authors) - Retrieve content with pagination, filtering, and sorting capabilities - Expand linked content to specified depths Required parameters: instance GUID, API type (fetch/preview), locale code, and lowercase reference name. Tip: Use Get Content Models action first to discover available reference names for your instance.
- `AGILITY_CMS_GET_CONTENT_MODELS` — Get Content Models — Tool to retrieve content models and page modules. Use when you need schema definitions to dynamically build content structures.
- `AGILITY_CMS_GET_LOGS` — Get Logs — Retrieve sync items (content change logs) from Agility CMS using the Content Sync API. This tool implements incremental content synchronization: - Use syncToken='0' for initial full sync (retrieves all content) - Use the returned syncToken in subsequent calls to get only new/updated content - Maximum pageSize is 500 items per request - Continue pagination until syncToken='0' is returned (indicating you're up to date) Typical workflow: 1. Call with syncToken='0' to get initial content batch 2. Store the returned syncToken 3. On next sync, pass the stored syncToken to get only changes since last sync 4. Repeat until syncToken='0' (no more updates)
- `AGILITY_CMS_GET_PAGE` — Get Page — Tool to retrieve details of a Page, including metadata, content zones, and components. Use after you know the page_id to fetch.
- `AGILITY_CMS_GET_PAGE_MODULES` — Get Page Modules — Retrieves page module definitions from Agility CMS. Page modules are UI components that can be added to pages. This action fetches all model definitions and filters to return only page modules (definitions without contentReferenceNames). Use this to understand what page modules are available for building pages. For content type definitions, use Get Content Models instead.
- `AGILITY_CMS_GET_SITEMAP_FLAT` — Get Sitemap Flat — Retrieves the flat sitemap for a specific channel and locale in Agility CMS. Returns a dictionary mapping page paths to sitemap items containing page metadata, SEO info, and routing details. Use this when you need to get all pages and their URLs for implementing page routing, generating sitemaps, or navigating the site structure. Required: instance GUID, API type (fetch/preview), locale code, and channel name.
- `AGILITY_CMS_SYNC_PAGES` — Sync Pages — Retrieves all page items from Agility CMS in paged format with sync tokens for incremental updates. Use this to synchronize local page data with the CMS. Start with syncToken=0 for initial sync, then use the returned syncToken in subsequent calls to get only changed pages. Each response includes page metadata, SEO fields, visibility settings, and script configurations.

## Auth

Auth schemes: `API_KEY`.

## How agents use Agility CMS

Inside a Definable workflow, Agility CMS is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Agility CMS** — the Researcher (GPT-5.5) pulls context from Agility CMS (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Agility CMS** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Agility CMS (create record, post message, draft email).
- **Designer / Engineer → Distributor → Agility CMS** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Agility CMS (attach file, open PR comment, post status).

The Verifier checks every Agility CMS call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- website builders — https://definable.ai/apps/category/website-builders/
- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/agility_cms/
- Same category (website builders): https://definable.ai/apps/category/website-builders/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt