Understand integrations and automation access

Integration groups

• Chrome extension: turn a webpage into a Studio video workflow.
• Publish integrations: LinkedIn, X, and YouTube connections.
• Create integrations: MCP, n8n, and Zapier entry points.
• Make.com: currently shown as Coming Soon in the deployed UI.

Authentication access

Every signed-in user can create and manage credentials from Settings → API Keys. Some connectors, including supported Claude and ChatGPT flows, complete authentication inside the connector instead; follow the setup screen for the surface you are connecting.

Before connecting an automation

• Confirm that the card has a live Connect, install, or setup action rather than a Coming Soon label.
• Choose a small test input that contains no secrets or customer data.
• Complete one creation and retrieve the result before building a larger workflow.
• Record which account owns the connection and where the generated project is saved.
• Keep API keys and access tokens in the automation service's secret store, never in a prompt or shared screenshot.

Developer documentation

Use the API credentials, API getting-started, MCP, Zapier, and n8n guides in the Automations and developer category. API-key creation is self-service for every signed-in user; the availability and permissions of third-party connectors still depend on the connector and its current setup flow.

A safe first pass

1. Confirm that the live integration has a Connect, install, or setup action.
2. Connect a test account or a self-service API credential using an approved secret store.
3. Run one minimal creation and retrieve its status and result.
4. Record ownership and error handling before expanding the automation to customer data or production volume.