Setup guide
Connect n8n to Postly with the HTTP Request node
Save your API key in n8n credentials, verify a read-only workspace request, and build a reviewed publishing workflow with delivery checks.
Postly Team · Updated October 25, 2026
1.Prepare a separate API key
Open Postly API access and create a key for this connection. Confirm the intended workspace and connected channel in Postly. Keep the key out of prompts, source records, screenshots, and shared workflow JSON.
2.Save a Header Auth credential in n8n
Add an HTTP Request node. Choose Generic Credential Type, then Header Auth. Set Name to X-API-Key and Value to your Postly API key. Save it in n8n credentials and select it on each Postly request.
3.Verify a read-only request first
Set Method to GET and URL to https://openapi.postly.ai/v1/workspaces. Execute only this node. Confirm the response includes the workspace you intend to use. This request does not create or schedule posts. If access fails, check the credential and Postly API eligibility before continuing.
4.Map an approved source record
Put a filter or approval gate before the publishing request. Use the Postly API reference to select the operation and JSON fields. Resolve the connected channel for the intended workspace. Preserve the source record ID and explicit future time with its timezone.
5.Test one publishing request deliberately
Use reviewed content and a controlled connected destination. Inspect the entire response, including any row-level errors. Store the returned post ID beside the source record and check the actual scheduled item in Postly before enabling the workflow.
6.Handle delivery and retries
An accepted request is not a published post. Use the returned ID for follow-up. On an ambiguous timeout, inspect the existing result before retrying. For the bulk-import operation, keep the original source ID, text, destination, and schedule unchanged when recovering a retry. Route failures for review and avoid aggressive polling.
Your first read-only request
GET https://openapi.postly.ai/v1/workspaces
X-API-Key: <stored n8n Header Auth credential>Save the real key in the Header Auth credential. The placeholder above is explanatory; it is not a literal header value.
Official references
Check the result
- The workspace discovery request succeeded without creating content.
- The API key is saved in credentials, not the URL or workflow body.
- Only reviewed records reach the publishing request.
- The channel, future time, and timezone are explicit.
- Post IDs and row-level errors are retained for delivery checks.