Answer: Build stages for media prep → per-platform mapping → publish → status/retry. Do not assume one payload works for all six networks.
Use cases: Automation teams, Video publishing.
What this means in a real publishing workflow
A multi-platform pipeline should prepare one source asset, then map it into separate platform payloads. Titles, captions, media types, privacy controls, destination IDs, and asynchronous behavior are not interchangeable.
Recommended implementation
- Validate the source media before fan-out.
- Build one branch per platform with its required fields.
- Store a separate Postifys ID and outcome for every branch.
- Retry only failed destinations so successful platforms are never duplicated.
How to verify the fix
For YouTube, keep the final title at 100 characters or fewer. For Pinterest, select a board. For Instagram, use a professional account and a supported media type. For TikTok, preserve the creator-inbox completion step where applicable.
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