Answer: Install
n8n-nodes-postifys, add your API key credential, select a platform and connected account, map media/caption fields, and branch on failures.What this means in a real publishing workflow
The Postifys n8n node keeps platform OAuth credentials inside Postifys while n8n uses a Postifys API key. This separation makes workflows easier to rotate, audit, and share without exposing social tokens.
Recommended implementation
- Create a Postifys API key and add it as an n8n credential.
- Choose the platform, account, and operation in the Postifys node.
- Map platform-specific title, caption, media URL, board, channel, or page fields.
- Enable asynchronous posting and record the returned history ID.
How to verify the fix
Use a status column in the source table and claim one pending row before downloading media. Mark it submitted only after Postifys accepts the request, and route failures to a visible needs-attention state.
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