Answer: Prepare one final video file, then fan out with platform-specific Postifys endpoints (or n8n nodes). Expect different account types, fields, and outcomes—especially TikTok Direct Post review fields and no LinkedIn Company Pages.
Design rule
One media asset, six platform jobs - not one “magic” payload. Each network still needs the correct account type and fields.
| Platform | Account | Video path | Watch-out |
|---|---|---|---|
| Page | Feed / Reel fields | No personal profile wall | |
| Professional | type REEL | No personal accounts | |
| YouTube | Channel | Upload + title required | Provider processing after accept |
| Board | Image Pin today | Video Pin not claimed | |
| Member | Member video post | No Company Pages currently | |
| TikTok | Creator | Direct Post or Draft Upload | Settings must match creator capabilities |
Recommended pipeline
- Encode once (MP4/H.264 when possible) and host a stable URL.
- Validate size against Postifys temporary-media limits.
- Create six platform jobs (API or n8n fan-out).
- Track each lane in Post History; retry only failures.
- For TikTok, complete publish in the creator app/inbox when required.
Related: pipeline design · partial failure recovery · FB+IG fan-out template · compatibility matrix
What this means in a real publishing workflow
One source video can feed six platform branches, but each branch needs its own destination, text limits, media rules, and completion semantics. Reusing one undifferentiated payload creates avoidable validation and duplicate-post problems.
Recommended implementation
- Validate and store the source video once.
- Build separate Facebook, Instagram, YouTube, Pinterest, LinkedIn, and TikTok mappings.
- Stagger large downloads and account-specific browser work.
- Record and retry each destination independently.
How to verify the fix
A campaign is complete only when every required branch reaches its intended terminal state. TikTok inbox delivery, for example, may still require creator action.
Operational check: Test with one item, confirm the final destination and Postifys history state, and only then enable the recurring workflow. Keep the returned Postifys ID beside the source row so every result remains traceable.
Related Postifys resources
API documentation · Error reference · n8n automation guide · Safe retry guide · Compatibility matrix