Describe a route, not just a pair of networks
'Works with YouTube' could mean uploading a video, reading a channel's posts, importing analytics, or sharing a link. Those are different operations. Write your requirement as an action with an origin, destination, content type, and account. For example: 'Take an original clip from my existing workflow and publish a video to my own channel.' Ask about the reverse direction separately; support is not automatically symmetrical.
Keep new composition separate from syncing an existing native post. A product may let you compose to a network without reading that network as a source. It may also support a content type in one flow but not another. Ferryman has create, schedule, and sync workflows; its integration documentation is a starting point for checking the route you need rather than assuming identical capabilities everywhere.
Build a requirements-to-evidence table
Use one row per actual publishing requirement. In the evidence column, record a current documentation link or the outcome of a controlled test. An empty cell means unknown. A screenshot of a platform logo is not evidence that an API supports native stickers, music selection, collaborator invitations, or every account category. List essential native finishing features explicitly before choosing an automated route.
The table below is a blank decision framework, not a Ferryman feature matrix or a comparison ranking. Fill it with your own accounts and required formats. It is more useful to discover one unsupported essential operation before a launch than to discover dozens of supported features you will never use. Save the date because permissions and platform APIs can change independently of your subscription.
| Dimension | Question to resolve | Evidence to save |
|---|---|---|
| Direction | Read from this source, or only publish to it? | Documented origin and destination |
| Identity | Which account type and operator can connect? | Supported role and account ID |
| Payload | Text, image set, video, or link? | A representative accepted post |
| Completion | Automatic publication or native review? | Final action and public result |
| Operations | What happens to failures, edits, and deletions? | Separate documented behavior |
Look for boundaries hidden behind familiar words
TikTok documents separate Direct Post and Upload workflows. Its Upload guide says users must open an inbox notification and continue editing before posting. Therefore, 'upload supported' and 'automatically public' cannot be treated as synonyms. The difference may be desirable when you need native finishing, but it changes staffing, deadlines, and the meaning of a successful scheduled task.
YouTube provides another concrete boundary: invited channel-permission users cannot access YouTube APIs, despite being able to perform supported native actions. That means the visible Studio role and the ability to authorize a third-party publisher must be checked separately. Similar caution applies to platform documentation generally: an available API field does not establish that a particular product exposes a control for it.
Turn the matrix into a useful shortlist
Mark each requirement essential, optional, or handled manually. Remove tools that cannot meet an essential need unless the manual alternative is acceptable and explicitly owned. For optional features, record the tradeoff instead of assuming more is always better. Review plan limits using your real number of connected accounts and operators, not just the number of distinct networks you use.
Then test the narrowest representative route before moving a queue. Save the final post URLs, account identity, format, and any manual intervention. Revisit the matrix after a connection change or a new content type. This keeps product selection tied to completed work. It also gives support a precise question: 'Can this role publish this format through this flow?' rather than an ambiguous report that a platform does not work.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.