n8n
Post to X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, and Telegram from an n8n workflow with the @chirpie/n8n-nodes-chirpie community node — posting, threads, scheduling, accounts, analytics, and AI Agent tool use.
@chirpie/n8n-nodes-chirpie is a community node that puts Chirpie in your n8n workflows. One node covers posting, threads, scheduling, listing accounts, and analytics — and it is available to n8n AI Agents as a tool, so an agent can look up your connected accounts and publish on its own.
Install
- Open Settings → Community Nodes.
- Select Install.
- Enter
@chirpie/n8n-nodes-chirpie. - Agree to the risks of using community nodes and select Install.
The Chirpie node then appears in the nodes panel.
cd ~/.n8n/nodes
npm install @chirpie/n8n-nodes-chirpieRestart n8n afterwards.
n8n Cloud only allows community nodes that n8n has verified. One-click install on Cloud is coming — until then, use a self-hosted n8n instance.
Add your credential
- Create an API key in the dashboard.
- In n8n, add a Chirpie API credential and paste the key.
- Leave Base URL as
https://chirpie.ai. - Select Test. The credential calls
GET /api/v1/accountsand confirms the key works.
Connect your social accounts once in the dashboard. The node publishes through whatever is connected there — no per-platform setup inside n8n.
Operations
| Resource | Operation | Description |
|---|---|---|
| Post | Create | Publish now, or schedule with Schedule At |
| Post | Get | Fetch a single post by ID |
| Post | Get Many | List posts, filtered by status or account |
| Post | Delete | Delete from Chirpie and from the platform |
| Thread | Create | Publish a 2–25 post thread, now or scheduled |
| Account | Get Many | List your connected social accounts |
| Analytic | Get | Engagement metrics for a published post |
Every operation returns the post, thread, account, or metrics object directly — id, status, platform_post_id and the rest are available on the output item without any extra unwrapping.
Create a post
Account ID is the id of a connected account. Run Account → Get Many once to find it, or copy it from the dashboard.
Optional settings live under Options:
- Media URLs — a comma-separated list of public image or video URLs. Chirpie downloads them and uploads them to the platform for you.
- Schedule At — publish at a future time instead of immediately. See Scheduling.
Create a thread
Posts is a list; add one entry per post in the thread, each with its own text and optional media URLs. On X, Bluesky, Threads, Mastodon, and Telegram each post replies to the one before it. On platforms without native threading, each is published as a standalone post.
Use it with an AI Agent
The Chirpie node is usable as a tool. Connect it to an AI Agent node's tool input and the agent can call it on its own.
A good setup is two Chirpie tool nodes:
- Account → Get Many, so the agent can resolve "my LinkedIn" to an account ID.
- Post → Create, with Account ID and Text set to
$fromAI(...)expressions so the agent fills them in.
Give the agent a system message telling it to list accounts before posting, and to respect the platform's character limit. Then "post 'shipping today' to X" is enough.
A ready-made workflow ships with the package as examples/ai-agent-social-posting.json — import it with Workflows → Import from File and set your credentials.
Example workflow: schedule a daily post
- Schedule Trigger — every day at 09:00.
- Chirpie — Resource Post, Operation Create.
- Account ID: the account you want to publish through.
- Text:
={{ $json.text }}from whatever built the copy upstream. - Options → Schedule At:
={{ $now.plus({ hours: 3 }) }}to queue it three hours out instead of publishing immediately.
- Chirpie — Resource Analytic, Operation Get, with Post ID set to
={{ $json.id }}from step 2, run later to pull engagement.
Schedule At accepts any n8n datetime — a picker value, an expression, or a $now calculation. The node converts it to UTC before sending, so workflow timezones are handled for you.
Errors
The node surfaces Chirpie's API errors directly. The common ones:
| Status | Meaning |
|---|---|
401 | The API key is invalid or was revoked |
404 | The account ID doesn't exist, or the account is disconnected |
429 | Monthly post limit reached, or more than 60 requests in a minute |
See Errors for the full list, and Rate limits for quotas.
FAQ
Can I use the Chirpie node on n8n Cloud?
Not yet — n8n Cloud only runs community nodes that n8n has verified, and one-click Cloud install is coming. On a self-hosted n8n instance you can install it today from Settings → Community Nodes.
Which platforms can the node post to?
X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, and Telegram. More platforms are coming soon, and the node picks them up automatically — it has no platform picker: you choose an Account ID, and the platform follows from whichever account that is.
Do I need separate credentials for each social network?
No. One Chirpie API credential covers every platform. You connect the social accounts once in the Chirpie dashboard, and the node publishes through them.
How do I find an Account ID?
Add a Chirpie node with Account → Get Many and run it once — each item's id is an account ID. You can also copy it from the dashboard.
Can an AI Agent use this node?
Yes. The node is exposed as a tool, so it can be attached to an AI Agent node's tool input. Use $fromAI(...) expressions on Account ID and Text to let the agent fill them in.
Can I post to several platforms at once?
Run one Chirpie node per account — for example a Loop Over Items node over a list of account IDs, or parallel Chirpie nodes. Each call publishes to a single account.
Does the node upload image files?
It takes public Media URLs, not binary data. Chirpie downloads each URL and uploads it to the platform. If your workflow produces a binary, put it somewhere publicly reachable first and pass that URL.
Is it free?
The node is MIT licensed and free. Posting counts against your Chirpie plan's monthly quota — see Rate limits.