REST API

Make any n8n workflow publish

An HTTP Request node is all it takes. A new release, a form submission, an RSS item — anything that can trigger a workflow can end with a post on your calendar.

Start for free Full docs

Setup

Connect n8n in three steps

Create an API key

In SchedPilot, open API Access and generate a key. It starts with smm_.

Give your agent the endpoint

Point it at the developer API with your key as a bearer token.

Let it schedule

Posts land in your calendar for approval, exactly as they would from the app.

curl -X POST https://api.schedpilot.com/developers/v1/post \
  -H "Authorization: Bearer smm_your_key" \
  -H "Content-Type: application/json" \
  -d '{"content":"Shipping today","date":"2026-07-10","time":"09:00",
       "accounts":[{"id":12,"type":"linkedin"}]}'

Replace smm_your_key with the key from API Access in your SchedPilot account.

Once connected

What n8n can do

get_accounts

List every connected social account, with its id and type.

create_post

Schedule a post to one or many accounts, with media, a thread and a video title.

list_posts

Read scheduled and published posts, filtered by date or status.

delete_post

Cancel a scheduled post before it goes out.

upload_media

Upload an image or video from a URL and get a media id back.

get_analytics

Read impressions, reach, likes, comments and shares for a published post.

Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.

Why n8n

Triggers you already have, posting you did not

Most teams already have the trigger: the deploy hook, the CRM webhook, the RSS feed. What they lack is the last hop. One node closes it, and nothing has to be rebuilt.

Works with any trigger n8n supports
No custom node to install — a plain HTTP request
Chain it after an LLM node to draft the copy first

Try asking it

Things that work well once n8n is connected.

“POST to /developers/v1/post when a release tag appears”

“Draft with an LLM node, then schedule the result”

“Queue a post for every new RSS item”

Rate limits are per user: 150 read and 100 write requests an hour. A post with media costs two writes, so batch large runs accordingly.

FAQs

n8n questions

Is there an official n8n node?

Not yet. The HTTP Request node works today and is what the docs show.

How do I authenticate?

A bearer token — your SchedPilot API key, created under API Access.

Can it publish without my approval?

No. Scheduling queues a post; it waits in your calendar until you approve it. That holds for every agent and every connection method.

Using something else?

There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.

See all agents

Connect n8n to SchedPilot

Free to start, and every post waits for your approval.

Start for free