Home | Connectors | Agility | Agility - Axiell Integration and Automation
Agility CMS and Axiell complement each other well in cultural heritage and public-facing digital experiences. Axiell manages authoritative collection, metadata, and preservation records, while Agility delivers those assets and stories across websites, campaign pages, and digital channels. Together, they help museums, libraries, and archives publish richer content faster, reduce manual re-entry, and keep public-facing information aligned with collection systems.
Data flow: Axiell to Agility
Curators and collection managers maintain object metadata, descriptions, provenance, and classification in Axiell. Agility consumes approved records through API integration and publishes them on exhibition pages, collection search pages, and object detail pages on the institution?s website.
Data flow: Axiell to Agility, with optional bi-directional status updates
Axiell often stores or references images, scans, audio, and video tied to collection items. Agility can pull approved media references and metadata to build rich exhibit pages, educational content, and gallery highlights. If needed, Agility can send back publication status or page references for governance tracking.
Data flow: Axiell to Agility
When a museum launches a temporary exhibition or themed digital campaign, Agility can automatically assemble landing page content from Axiell records such as object titles, artist names, dates, and related collection items. Marketing and communications teams can then add editorial copy, calls to action, and event details in Agility.
Data flow: Axiell to Agility
Axiell can provide structured metadata for search facets such as creator, period, location, material, and subject. Agility uses this data to power public discovery interfaces, allowing visitors to browse and filter collections on the website. This is especially useful for institutions offering online catalogs or digital archives.
Data flow: Axiell to Agility
When collection records are updated in Axiell, such as corrected dates, revised descriptions, or new rights information, Agility can automatically refresh the corresponding website content. This keeps public pages accurate without requiring manual edits by web editors.
Data flow: Bi-directional
Educators and content editors use Agility to create interpretive articles, lesson pages, and thematic stories. These pages can link back to Axiell object records, while Axiell can store references to related educational content for internal use or future reuse. This creates a connected experience between scholarly records and public storytelling.
Data flow: Bi-directional
Axiell can remain the system of record for collection approval, while Agility manages content publishing workflows for web pages and campaigns. Integration can pass approval status, publication readiness, or content identifiers between systems so that only approved records are exposed publicly.
Overall, integrating Agility with Axiell helps cultural institutions deliver accurate, engaging, and scalable digital experiences while preserving the integrity of collection data and reducing manual coordination across teams.