Verify your connection
Use an authenticated GET request to list your accessible Postly workspaces.
Postly + n8n
Bring your n8n workflows into your Postly publishing plan.
Connect the workflows you already run in n8n to your publishing workspace. Keep your AI agent in charge of preparation, your team in charge of approval, and Postly in charge of the publishing schedule.
Connect through the HTTP Request node and Postly API. Postly API access is required. Your automation platform’s plan and limits also apply.
The outcome
A deliberate API workflow with reviewed content, an explicit destination, and a stored Postly post ID.
Map approved content
Use n8n filtering and mapping before sending a documented publishing API request.
Keep a delivery reference
Store the returned post ID and inspect the post through the documented API or Postly calendar.
A clear path from input to outcome.
- 01
Your agent or source
Prepare content and keep it in an approval queue.
- 02
n8n
Filter approved records, validate fields, and call the Postly API.
- 03
Postly
Accept a valid publishing request and return a reference.
- 04
Follow through
Record the post ID and check the actual publishing outcome.
Start with the right setup.
- A Postly account with API access and permission to the target workspace.
- An n8n instance that can reach https://openapi.postly.ai over HTTPS.
- A connected publishing channel and reviewed content with an explicit future publishing time.
Put it to work.
AI brief → approved publishing queue
Prepare content with an agent and require approval before your HTTP Request step.
Read the workflowContent database → scheduled campaign
Map reviewed records and explicit destinations to documented publishing requests.
Read the workflowPost ID → delivery follow-up
Link each source record to the Postly post so retries and delivery checks remain traceable.
Read the workflowQuestions about Postly + n8n
Do I need a native Postly node?
This guide uses n8n’s built-in HTTP Request node with the Postly API. It does not require or claim a native Postly node or an approved n8n marketplace listing.
How do I authenticate?
Use Generic Credential Type and Header Auth. Set the header name to X-API-Key and save your Postly API key as its value in n8n credentials. Do not put the key in a URL or a shared workflow export.
Can an n8n workflow prepare and publish content with an AI agent?
An agent can prepare content upstream. Put an explicit approval gate before the Postly publishing request, and validate the final content, workspace, channel, and publishing time.
Is an HTTP success response proof of publication?
No. Inspect the response and any row-level errors, retain the returned post ID, and check delivery. An accepted request may still encounter destination validation or provider errors.