One node, a native post everywhere
Post → Create takes one entry per account, each with its own text, so LinkedIn can read differently from X. They all share one post ID and one schedule. Save it as a draft, schedule it, or publish now.
Create, schedule and publish to X, LinkedIn, Instagram, TikTok, YouTube and more from one node. Start a workflow when a post goes live or fails.
Community Nodes → n8n-nodes-bulkitEvery Bulkit operation as an n8n node, plus a trigger for what happens after.
Post → Create takes one entry per account, each with its own text, so LinkedIn can read differently from X. They all share one post ID and one schedule. Save it as a draft, schedule it, or publish now.
An RSS feed, a form, a new spreadsheet row: whatever starts the workflow can post. Put Media → Upload first to attach a file, and set an idempotency key so a retry never posts twice.
The Bulkit Trigger starts a workflow when a post publishes, fails or partly fails, or when an account needs reconnecting. It registers its own webhook when you activate the workflow and checks every signature.
Give n8n's AI Agent the Bulkit node as a tool, and it can draft, schedule and publish posts, check how they did and answer comments from a chat.
On self-hosted n8n, go to Settings → Community Nodes → Install, enter n8n-nodes-bulkit and confirm. Then search for Bulkit in the nodes panel.
Create an API key in the Bulkit app under Developers → API & Webhooks. In n8n, add a Bulkit API credential and paste the key. Leave Base URL as it is.
Yes. A test key (bk_test_…) checks every request like a live key, but never posts and is never billed. Switch to a bk_live_… key when the workflow is ready.
No. Add one channel entry per account to a single Post → Create. Each entry has its own text, and they all share one post ID and one schedule. One node per channel makes separate posts, each with its own schedule.
Not yet. Publish Now and Post → Publish return as soon as the post is queued. Use Post → Get, or a Bulkit Trigger on Post Published and Post Failed, to find out how each channel did.
Bulkit has to reach your n8n, so the trigger needs a public https:// URL. An n8n on localhost won't receive events: use a tunnel or a hosted n8n. Post events fire once per channel.
Use n8n's HTTP Request node with Authentication set to Predefined Credential Type and choose Bulkit API. It can call any endpoint under https://api.bulkit.io/public/v1.
No. Its calls are billed like any other action, included in your 500 monthly actions, then $0.01 each.
$4.99/mo, 500 actions included. The n8n node is free on every plan.