n8n social media with Postdom

Can you post to TikTok from n8n?

Yes, using a live Postdom path and a connected TikTok account—but the useful question is what happens after the request. Supply the finished video, keep the human's account and approval boundary intact, then read the returned post until TikTok reaches a terminal outcome.

A result such as requires_approval means the request is waiting for a human. Scheduled is not published. A green n8n execution only shows that the workflow step finished; it does not establish that a provider published the post.

How to set up a guarded Postdom workflow in n8n

Choose a path that is actually available, connect a human-owned workspace, supply the finished video, send one bounded request, and reconcile that same request before retrying.

1. 1

   Choose the live path

   For self-hosted n8n, install n8n-nodes-postdom 0.3.0 from npm and treat it as a community node without n8n verification. For n8n Cloud, use the hosted MCP endpoint. Do not search for a Postdom n8n listing or template-library install: neither is published.

2. 2

   Let a human connect the workspace

   A human creates the scoped Postdom agent key and connects the actual account in the Postdom dashboard. Store the key in an n8n credential, never in a workflow field or prompt. An agent can use that authority, but it cannot approve its own work, connect an account for the human, or widen policy.

3. 3

   Supply the approved finished video

   Start with the actual video and caption the human intends to publish. Postdom handles supplied finished video; it does not generate video. If your path uploads media, map the file's measured metadata instead of guessing dimensions or duration. Stop if the asset, destination, audience, disclosure, consent, or commercial-use requirements are unresolved.

4. 4

   Send one bounded request

   Select only the intended connected accounts, keep the human approval boundary visible, and preserve the request's returned ID. A requires_approval result is a designed review state, not a failure. A request marked scheduled is not published, and a successful n8n execution is not proof of a provider post.

5. 5

   Read the same request to its outcome

   Use the returned ID to read the same post until it reaches a terminal outcome. Inspect each destination independently before retrying so a partial result does not duplicate a successful destination. Read performance only when reported; null is not zero and must keep its availability reason.

Where does an AI agent fit?

The search phrase “AI agent social media n8n” usually describes an agent that chooses tools inside an n8n workflow. That agent can prepare a bounded request and interpret its result. It cannot approve itself, create its own authority, or turn an unchecked model response into permission to publish.

1. Read workspace guidance and connected-account state.
2. Propose the exact supplied asset, caption, destination and time.
3. Stop for missing consent, unsuitable audience or disclosure, commercial-use uncertainty, or a policy mismatch.
4. Send one request only after the human-owned boundary allows it.
5. Read the same request to its real terminal outcome before deciding what to do next.

For performance, keep Postdom's availability state beside each value. The metric availability reference explains why an unreported observation must stay null rather than becoming zero.

Which n8n workflow templates are planned?

These are the three ranked ideas in the marketplace-owned catalog. They are source proposals—not live n8n library pages, not executed workflows, and not promised releases. The public repository is useful for inspecting source, but its JSON files are not marketplace install links.

Questions before you connect n8n