Ctrlk
HomeSign In
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Integrations

Connect Playbooks to Grids, Slack, and CMS publishing

Playbooks can use AirOps integrations to read context, notify teams, prepare content for publishing, and coordinate work across your stack.

Grids

Grids and Playbooks compose for batch work. Add a Playbooks column to a Grid to run a published Playbook for each row.

To add a Playbooks column:

  1. Open the Grid.

  2. Click + Add Column.

  3. Select the Playbooks tab.

  4. Choose the Playbook.

  5. Map Grid columns, static values, or Brand Kits to Playbook Inputs.

If the workspace has no published Playbooks, the Playbooks tab does not have a Playbook to add.

Slack

Connect Slack to receive AirOps notifications when a Playbook is triggered or when Human Review is required.

  1. Integrate Slack in your AirOps workspace settings.

  2. Install the AirOps app in your Slack workspace.

Use the Slack Tool when a Playbook needs to read channel history or send messages. Slack can also receive AirOps notifications for triggered runs and Human Review.

CMS publishing

Best practice is to keep content creation and CMS publishing as separate steps. Use Playbooks to create, refresh, and review content, then publish from a Grid column, a separate publishing Playbook, or a CMS MCP.

Native CMS publishing options include:

  • Webflow: Native export. The export pushes the full rich-text field, so custom embeds or tables in that field can be replaced.

  • WordPress: Direct publishing.

  • Contentful: Field-level content push.

  • Sanity: Structured content push.

  • Ghost: Article publishing.

If you use a CMS MCP or another custom publishing path, call the AirOps MCP track_aeo_page_content_update tool after the page is published or refreshed. Pass the page URL and update type. This records the content update in AirOps Insights so you can connect future AI visibility, citation, mention, and traffic changes to the publish event.

Images created with the Image Generation tool are hosted. Other images generated or attached during a Session can be local to the Session. For CMS publishing that requires hosted images, use the Image Generation tool, stock image URLs, or add a manual image upload step to your process.

Last updated

Was this helpful?