Automation

Choose the tool that fits where your work starts. Each uses OpenPost's workspace access rules. For unattended automation, create a separate token for each integration and bind it to one workspace when possible.

• JavaScript and TypeScript scripts, CI jobs, and agents calling over HTTP: TypeScript SDK.
• Shell commands, scripts, and CI: Command-line interface, including the openpost-cli agent skill.
• AI assistants such as ChatGPT, Claude, and Cursor: MCP.
• Timers and webhooks: the n8n workflow below.

Connect an AI assistant

Connect OpenPost to Cursor, ChatGPT, or Claude through MCP. Each guide covers sign-in, workspace access, a first test, and connection troubleshooting.

Grant mcp:read for inspection and reports. Grant mcp:full only when the assistant needs to create, edit, schedule, or publish. The MCP overview explains remote sign-in, developer tokens, and the local bridge.

Build an n8n workflow

Install @getopenpost/n8n-nodes-openpost from Settings → Community nodes in n8n. The package requires Node.js 22.22 or newer in the n8n runtime.

Create an OpenPost credential in n8n with Base URL https://app.openpo.st and an OpenPost API token. Do not add /api or /api/v1 to the base URL. For a workflow that writes, use a workspace-bound api:write token.

The node includes workspace, account, media, schedule, and publication actions. Create, Schedule, and Publish Now are separate actions. Use n8n's Schedule Trigger or Webhook node to start a workflow. Import the package's list-workspaces example first to verify the credential, then replace its workspace ID with yours.

If n8n runs in Docker, localhost means the n8n container. Use the OpenPost Compose service name or host.docker.internal when the services share a machine.