Help centre

Integrations

Other tools can start posts in Release Social, and hear when a post went out or didn't. Whatever they send arrives as a draft: it is approved and scheduled here, like any other post. Everything below is in Settings → Integrations.

API keys, the webhook and the tools that use them come with Agency and Enterprise. On a smaller plan, keys and the webhook are kept but stop working until the plan has them again; Settings says which plan has them.

What every tool needs

• An API key. Choose New key, name it after the tool (for example "Zapier"), and Copy it: it is shown once. A key can create drafts and read them, never approve or post. Revoke it the moment the tool stops using it.
• The API address, shown under the keys with Copy.
• The webhook, if the tool should hear about posts. Paste the address the tool gives you into Webhook. A workspace has one webhook address.

Making a draft

Every tool makes a draft the same way: a POST to the API address followed by /api/v1/drafts, with the header Authorization set to Bearer, a space and your key, and a JSON body with three fields:

• title: the post's name in Release Social.
• base_text: the post's words. It may be empty.
• content_intent: feed, reel or story.

The answer has the new draft's id. A GET to /api/v1/drafts/ followed by that id reads it back.

Hearing about posts

With a webhook saved, Release Social sends a POST to it when a post went out (job.published) and when it didn't (job.failed). The JSON says the event, the post's draft_title and draft_id, the network (provider) and, for a failure, why (detail).

Each delivery is signed. The x-autosocial-signature header is sha256= followed by an HMAC-SHA256 of the body, made with the webhook's signing secret, which is shown once when you save the webhook. A tool that checks it knows the message came from your workspace.

Zapier

Release Social isn't in Zapier's app list yet, so use Zapier's own Webhooks by Zapier steps.

1. To make drafts: add the action Webhooks by Zapier → Custom Request. Method POST, the URL as in Making a draft, the Authorization and Content-Type: application/json headers, and the JSON body, filled from the earlier steps of your Zap.
2. To hear about posts: start a Zap with Webhooks by Zapier → Catch Hook, copy the address Zapier shows, and paste it into Webhook in Settings → Integrations. Add a Filter on event to act only on posts that went out, or only on those that didn't.

Make

Release Social isn't in Make's app list yet, so use Make's own HTTP and webhook modules.

1. To make drafts: add HTTP → Make a request. Method POST, the URL as in Making a draft, the Authorization header, body type Raw, content type JSON, and the three fields.
2. To hear about posts: start a scenario with Webhooks → Custom webhook, copy its address into Webhook in Settings → Integrations, and add a filter on event.

n8n

1. To make drafts: add an HTTP Request node. Method POST, the URL as in Making a draft, the Authorization header (or a Header Auth credential), and a JSON body with the three fields.
2. To hear about posts: start a workflow with a Webhook node set to POST, and paste its production address into Webhook in Settings → Integrations. To check the signature, make an HMAC-SHA256 of the raw body with the signing secret (the Crypto node does this) and compare it with the header.

ChatGPT

A custom GPT can make drafts for you through an action. In the GPT's settings choose Create new action, then Import from URL with the API address followed by /api/v1/openapi.json. Under Authentication choose API Key, then Bearer, and paste a key. Ask the GPT to write a post, and it arrives in Release Social as a draft. It can read drafts and whether a post went out, never approve or post.

Claude and MCP

Release Social's connector for Claude and other tools that speak the Model Context Protocol isn't published yet. Until it is, ask Claude to write the post and paste it into Create, or connect a tool that can call a web address, as in Making a draft.