Skip to content
Postbroad
Sign inStart for $0

Automate social posting with n8n. The HTTP Request node and a webhook.

n8n talks to the Postbroad API with its HTTP Request node. Create a draft from any workflow, let a person approve it in Postbroad, and use a Webhook node to react when a post goes live or fails. Postbroad nodes for n8n are coming soon.

REST APIAutomation
n8n, connected to PostbroadWhat it can do
Create drafts from anythingTurn a new article, a product update or a form entry into a Postbroad draft for the channels you pick.
Schedule or publishPreview the post, then schedule it for its time or send it now. Posts that fail the checks stop with the reason.
Leave the decision to a personCreate drafts and let your team approve and schedule them in Postbroad.
React to what happenedStart a workflow when a post goes live on a network, when one fails, or when an approval is asked for or decided.

Connect n8n in three steps.

n8n works with Postbroad through the Postbroad API, with an API key you make in Postbroad.

  1. Make an API keyIn Postbroad, open your organization settings, then API keys. Give the key only the brands this workflow needs, and keep it out of shared files.
  2. Create a draft with HTTP RequestAdd an HTTP Request node that posts to /v1/posts with your key in the Authorization header. The post is saved as a draft for the channels you list.
  3. React with a Webhook nodeAdd a Webhook node, then add its production address in Postbroad as a webhook endpoint for the events you want, such as delivery.published.
n8n: HTTP Request node
POST  https://app.postbroad.com/v1/posts

Headers
  Authorization    Bearer prk_...
  Idempotency-Key  {{ $execution.id }}
  Content-Type     application/json

Body
{
  "brandId": "<brandId>",
  "baseText": "{{ $json.title }} {{ $json.link }}",
  "destinations": [{ "channelId": "<channelId>" }]
}
  • Scheduling from n8n takes a preview, then a schedule call with the receipt the preview returns. Many teams let n8n create drafts and schedule them in Postbroad.
  • Keep the key in an n8n credential, such as Header Auth, not in the node itself.

Workflows to start with.

Each one is a few steps. Drafts and approvals stay in Postbroad, where a person can read them.

New article in an RSS feed, then create a draft for Bluesky and LinkedIn.
Webhook for delivery.failed, then post a message to your team chat with the network and the reason.
Webhook for approval.decided, then log the decision in a sheet.

Every channel you connect.

n8n posts to the channels you connected in Postbroad, each with its own limits and its own state.

See every channel

n8n questions.

Are there Postbroad nodes for n8n?

They are coming soon. Until then, n8n uses the Postbroad API through its HTTP Request node, with an API key you make in Postbroad.

How do I know a webhook really came from Postbroad?

Every webhook is signed in the Standard Webhooks format, with a signing secret Postbroad shows once when you add the endpoint. Check the signature and the time before the workflow acts.

Which networks can it post to?

The channels you have connected in Postbroad. Each network keeps its own limits and its own state. See every channel.

Can I take the access away?

Yes. Remove the connection in the client, or revoke its grant or its API key in Postbroad, and the access ends.

Other agents.

The same Postbroad, the same rules, from another client.

Read the guide

Let n8n draft the week.