n8n
n8n is a workflow automation tool that connects Schedulin to hundreds of other apps. Use it to create posts from events, build multi-step automations, and fold Schedulin into pipelines you already run.
There are two ways to connect, and they suit different jobs:
- The Schedulin community node calls the Schedulin API directly. Every field is explicit and the result is predictable — this is what you want for a fixed pipeline like "new RSS item → draft post".
- The MCP client lets an AI model decide which Schedulin tools to call. Better for open-ended agent workflows, less predictable for a fixed pipeline.
Both authenticate with a Schedulin API key.
Option 1: The Schedulin community node
Setup
- Get an API key. In Schedulin, go to Settings → API keys and create one (or copy an existing key).
- Install the node. In n8n, go to Settings → Community Nodes → Install and enter
n8n-nodes-schedulin. - Add the credential. Add a Schedulin node to a workflow, create a new Schedulin API credential, and paste your API key. Leave Host and Media CDN URL at their defaults unless you self-host Schedulin.
- Pick a resource and operation — see the table below.
What the node can do
| Resource | Operations |
|---|---|
| Post | Create, Get, Get Many, Update, Delete, Publish Draft, Get Analytics |
| Social Account | Get Many, Get Next Queue Slots |
| Tag | Get Many, Create |
| Media | Upload, Get, Get Many, Delete |
| Platform | Get Many |
Your connected channels and tags load into dropdowns automatically, so you pick them by name instead of pasting IDs.
Creating a post
The Action field decides what happens:
| Action | Result |
|---|---|
| Draft | Saved, not published (the default) |
| Queue | Added to the channel's next free queue slot |
| Schedule | Published at the date and time you set |
| Now | Published immediately |
Action defaults to Draft, so a workflow you are still building never publishes by accident.
Adding images and video
Media is attached by URL. If your file is already on the public internet, paste its URL into the Media field.
To host the file with Schedulin instead, put a Media → Upload node in front of your Create node. It takes a file from the previous step and returns a hosted URL you can reference.
Platform-specific settings
Some platforms need extra details — a Pinterest board, an Instagram placement. Those go in Additional Fields → Platform Configuration (JSON). Use the Platform → Get Many operation to see what each platform requires.
Option 2: The MCP client
Use this when you want an AI model to decide what to do, rather than wiring up each field yourself.
- Get an API key. In Schedulin, go to Settings → API keys.
- Add an MCP Client node inside your n8n workflow.
- Configure the node:
- Server Transport: HTTP Streamable
- MCP Endpoint URL:
https://mcp.schedulin.app/mcp - Authentication: Bearer Auth
- Add your credentials. Click Credential for Bearer Auth → Create new credential, paste your API key as the token, click Save, and close the modal.
- Select the tools you want the workflow to use from the available Schedulin MCP tools, then configure each as needed.
This option uses large language models to generate responses, which may occasionally be inaccurate or incomplete — verify important details before taking action.
Example workflows
- RSS → Schedulin. When a new feed item appears, create a draft with the article title and link.
- Weekly digest. Every Friday, pull next week's scheduled posts and send a summary to Slack.
- Form → draft. When a form submission comes in, create a draft from the submitted content.
Good to know
- The API key's scope is the workspace it belongs to — the workflow can only see and act on that workspace.
- Rotate or revoke keys any time under Settings → API keys.
- Self-hosted n8n needs community packages enabled (
N8N_COMMUNITY_PACKAGES_ENABLED=true, which is the default). On n8n Cloud, community nodes require a paid plan. - The public API allows 300 requests per minute per key.