Community

Community tutorials for Status 200 Uploads

Tutorials that people outside Status 200 Uploads wrote and published on their own sites: a workflow, a lesson or a walkthrough built on one of our integrations. Each card names the author, says what the tutorial builds and which integration it uses, and shows the day we last read it. A tutorial is its author's own work: we read it, we did not run its steps.

  • Checked on

Every community tutorial

Written and published by people outside Status 200 Uploads, on their own sites. The title of each card opens the tutorial on its author's own site.

How a tutorial is listed

  • A tutorial here is someone else's work. It is written and published on the author's own site, under the author's name. We do not host it, edit it or change its steps.

  • We read a tutorial before it is listed, and its card shows the day of the last read. The card gives the author's name as the tutorial's own page does, and one sentence on what the tutorial says it builds.

  • A card shows only while the tutorial's last read is at most 30 days older than the day this page was last checked, the "Checked on" date at the top. A card with an older read is left off this page, and by the same rule off its integration's page, until the tutorial is read again.

  • A tutorial is not a test of ours. What we tested ourselves, and on which day, is on each integration's own page.

  • When a link was given in return for something, for example for the tutorial itself, it is marked as sponsored for search engines.

Write your own tutorial

Anyone can write a tutorial about Status 200 Uploads. These four steps make one that readers can follow.

  1. Pick one job

    Build one thing from start to finish, for example one workflow that sends one video to one network. Name the integration it uses and the networks it posts to: each network has its own settings and file limits.

  2. Say what the reader needs

    Say which plan your tutorial needs. The REST API, the Python package and the n8n node work with an API key, and API keys are on every plan, Free included. The AI connector, Telegram and Discord are on the paid plans, and so is importing from a Google Drive share link.

  3. Let readers try it without posting

    A post sent with dryRun set to true runs every check a real post runs and sends nothing, so a reader can follow your steps before anything goes out. Then show the real run and what comes back.

  4. Publish it, then tell us

    Publish the tutorial on your own site, under your own name, and send its address through the Support page. We read a tutorial before we list it, and we decide which ones are listed. A listed tutorial shows your name and a link to your page.

Send us your tutorial's address →

What a tutorial can be about

A tutorial can be about any of these. Each one has a page of its own with the setup, the limits and how it was checked.

Questions

Build the workflow from a tutorial

The REST API, the Python package and the n8n node work with an API key, and API keys are on every plan, Free included.