Agility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms.
Agility CMS is a headless content management system that allows developers to build and manage digital experiences across various platforms. On Nagent, Agility CMS is exposed as a fully-configurable website builders integration that any agent can call — 9 actions, and API key authentication. No code is required to wire Agility CMS into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Agility CMS to automate the kinds of tasks website builders teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Agility CMS into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Agility CMS, with input parameters and output schema. Drop these into any step of an agent built in Helix.
AGILITY_CMS_GET_API_TYPESTool 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_CONTENT_ITEMTool to fetch details of a content item by Content ID. Use when you need item fields and metadata from Agility CMS.
Input parameters
The unique GUID identifier for your Agility CMS instance. If not provided, will be extracted from connection metadata.
Locale code for the content (e.g., 'en-us').
API type: 'fetch' for published content, 'preview' for draft/staging content. Default is 'fetch'.
Unique numeric ID of the content item.
Depth for expanding linked content (0=none to 5=full). Default is 1.
Whether to fully expand linked content objects. Default is False.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_CONTENT_LISTRetrieves 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.
Input parameters
Your Agility CMS instance GUID (found in Settings > API Keys). Required. Example format: '4582b5fa-u'
Number of items to skip for pagination. Default is 0.
Field name to sort results by (e.g., 'fields/date' or 'properties/modified'). Use with 'direction' parameter.
Number of items to retrieve per page. Default is 10.
Comma-separated list of specific fields to include in response (e.g., 'title,description'). If not specified, all fields are returned.
OData-style filter expression to apply (e.g., 'fields/category eq "News"'). Leave empty to retrieve all items.
Locale/language code for the content. Common examples: 'en-us' (US English), 'en-gb' (UK English), 'fr-fr' (French).
Content retrieval mode: 'fetch' (published content only, recommended for production) or 'preview' (includes unpublished/draft content for testing).
Sort direction: 'asc' or 'desc'.
Reference name of the content list to retrieve. MUST be lowercase. Use Get Content Models action to discover available reference names. Common examples: 'posts', 'authors', 'products', 'tags', 'categories'.
Depth to which linked content items should be expanded (0 to 5).
Whether to fully expand all linked content items.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_CONTENT_MODELSTool to retrieve content models and page modules. Use when you need schema definitions to dynamically build content structures.
Input parameters
The unique GUID identifier for your Agility CMS instance. If not provided, will attempt to extract from the configured base URL.
API type: 'fetch' for published content models, 'preview' for draft/staging models. Default is 'fetch'.
Optional. Return only models updated since this date/time. Format: ISO 8601 date-time, e.g., 2020-09-24T10:00:00.00-04:00.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_LOGSRetrieve 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)
Input parameters
The unique GUID identifier for your Agility CMS instance. If not provided, will attempt to extract from the configured base URL.
Locale code for sync (e.g., 'en-us').
Number of records per page. Overrides default if provided.
Sync token indicating where to resume sync. Use '0' for full sync.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_PAGETool to retrieve details of a Page, including metadata, content zones, and components. Use after you know the page_id to fetch.
Input parameters
Locale code for the page (e.g., 'en-us').
The unique numeric ID of the page to retrieve.
Depth for expanding linked content (0=none to 5=full). Default is 1.
Whether to fully expand linked content items. Default is False.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_PAGE_MODULESRetrieves 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.
Input parameters
The unique GUID identifier for your Agility CMS instance. If not provided, will attempt to extract from the configured base URL.
Locale code for retrieving the models (e.g., 'en-us'). Required by the API.
API type: 'fetch' for published page modules, 'preview' for draft/staging modules. Default is 'fetch'.
Optional. Return only modules updated since this date/time. Format: ISO 8601 date-time, e.g., 2020-09-24T10:00:00.00-04:00.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_GET_SITEMAP_FLATRetrieves 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.
Input parameters
Your Agility CMS instance GUID (found in Settings > API Keys). Format example: '4582b5fa-u'
Locale/language code for the content. Common examples: 'en-us' (US English), 'en-gb' (UK English), 'fr-fr' (French).
Content retrieval mode: 'fetch' (published content only, recommended for production) or 'preview' (includes unpublished/draft content for testing).
Reference name of the sitemap channel (configured in Settings > Sitemaps, typically lowercase). Common value: 'website'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGILITY_CMS_SYNC_PAGESRetrieves 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.
Input parameters
Locale code of the pages to retrieve (e.g., 'en-us').
Number of items per request, default 500, max 500.
Sync token from the previous sync call; use 0 to start a fresh sync.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 45 agents privately built on Nagent that already use Agility CMS.
Build on Nagent
Connect Agility CMS to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Agility CMS, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Agility CMS is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Agility CMS is connected, you configure its 9 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Agility CMS steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Agility CMS event fires, the agent kicks off automatically.
Every Agility CMS action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Agility CMS ships with 9 pre-built website builders actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Agility CMS together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Agility CMS-based workflows tailored to your business.