> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/integrations/overview/integrations.md).

# CMS

Integrate workflows with content management systems

CMS Steps enable direct connections between your AirOps workflows and popular content management systems. These integrations allow you to publish, update, and retrieve content without manual copying and pasting, creating end-to-end automation for your content operations.

The CMS Steps include:

1. [**Builder.io**](/integrations/overview/integrations/builder-io.md) -- create and manage content entries and models in Builder.io
2. [**ContentStack**](/integrations/overview/integrations/contentstack.md) -- create and manage content in ContentStack spaces
3. [**Contentful**](/integrations/overview/integrations/contentful.md) -- create and update entries in Contentful spaces
4. [**Craft CMS**](/integrations/overview/integrations/craft-cms.md) -- create and manage entries and assets in Craft CMS
5. [**Framer**](/integrations/overview/integrations/framer.md) -- manage CMS collections and publish sites in Framer
6. [**Ghost**](/integrations/overview/integrations/ghost.md) -- publish and manage posts on Ghost publications
7. [**HubSpot CMS**](/integrations/overview/integrations/hubspot-cms.md) -- create, update, and publish blog posts and site pages in HubSpot
8. [**Sanity**](/integrations/overview/integrations/sanity.md) -- fetch, create and update documents in Sanity projects
9. [**Shopify**](/integrations/overview/integrations/shopify.md) -- create articles and custom collections, and update products in Shopify
10. [**Storyblok**](/integrations/overview/integrations/storyblok.md) -- create and manage stories and content in Storyblok spaces
11. [**Strapi**](/integrations/overview/integrations/strapi.md) -- integrate with Strapi's headless CMS platform
12. [**Webflow**](/integrations/overview/integrations/webflow.md) -- create, update, and manage content on Webflow sites
13. [**WordPress**](/integrations/overview/integrations/wordpress.md) -- publish and update posts and pages on WordPress sites

CMS Steps transform how you manage content across your digital ecosystem by bridging the gap between AI-powered content generation and your publishing platforms. These connections allow you to automate the entire content lifecycle, from ideation and creation to publication and updates.

With CMS Steps, you can build workflows that automatically push optimized content to your website, maintain consistent brand messaging across multiple platforms, and implement large-scale content strategy changes without manual intervention.

{% hint style="info" %}
Note: CMS Steps are designed for Workflow applications. Authentication requires appropriate admin permissions for each respective platform.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.airops.com/integrations/overview/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.