Open your integration, connect your account, and test access with copyable setup steps.

Choose your integration

Select a card to open its setup steps. Use the Open button to launch the destination and Copy for the field, URL, command, or first message you need. Copying requires clipboard permission; you can select the text manually if your browser blocks it.

Integration	Connection
ChatGPT	Plugins → Add → Add custom MCP server, then OAuth
Claude	Customize → Connectors, then OAuth
OpenClaw	Your Gateway's MCP settings and OAuth
Hermes	Remote MCP configuration and a secret environment key
CLI	Interactive key login and workspace selection
Make	HTTP credential and read-only request
n8n	Header Auth credential and HTTP Request
Zapier	Private beta invite or Webhooks
REST API	Integration key and read-only request
Slack	App installation and account linking
Telegram	Supplied short-lived connection code

Availability varies by deployment, tenant, account permissions, and provider controls. ChatGPT and Claude's OAuth flows do not need a manually generated integration key. API-key integrations require an eligible plan.

ChatGPT and Claude

For ChatGPT, open Plugins, choose Add → Add custom MCP server, and enter Name Aidelly and Server URL https://app.aidelly.ai/mcp. Choose OAuth and keep advanced discovery defaults. Review the trust notice, acknowledge it if you agree, and select Create as a plugin. Sign in to Aidelly when prompted.

For Claude, open Customize → Connectors, add Aidelly with the same server URL, and sign in through OAuth. Organization owners may need to add the connector before members connect.

Start a new conversation and use this first message:

List my Aidelly workspaces and connected social accounts. Ask me which workspace to use before making changes.

API-key integrations

Use Create integration key in the relevant integration's setup panel, or open Aidelly API Keys. Create a key with the access your integration needs and copy it into the destination's credentials or secret environment.

For a read-only test, set AIDELLY_API_KEY in your secret environment and run:

curl --fail-with-body https://app.aidelly.ai/api/public/v1/workspaces \
  -H "Authorization: Bearer $AIDELLY_API_KEY"

Choose the intended workspace from the response before using write operations. Missing or invalid credentials can produce 401; insufficient access can produce 403. Use the API reference for endpoint requirements.

CLI setup

npm install -g @aidelly/cli
aidelly auth login
aidelly workspaces list
aidelly use workspace YOUR_WORKSPACE_ID
aidelly connections list

Paste your integration key at the login prompt. The CLI's key option is --key; interactive login keeps credentials out of shell history. CLI commands

Automations and messaging

Make and n8n use saved credentials and a GET workspaces request first. Use Zapier's invite only when one has been supplied; otherwise follow its Webhooks guide. For n8n Cloud, use HTTP Request unless a verified Aidelly node is available; unverified npm community packages require self-hosting.

Install Slack from its integration card, review the requested workspace/channel permissions, and return to Aidelly. Telegram uses an account-linking code, not your API key; contact support if no linking flow is available. The current page does not expose custom messaging targets or notification-category switches.

Manage credentials

Manage keys in Aidelly API Keys. To rotate an API-key integration, create a replacement, update the destination and test access, then revoke the old key. For OAuth integrations, reconnect when prompted rather than copying an API key into the client.

REST API reference · MCP overview · Account settings