Social media schedulers stop at the API. Here’s what to do with the rest.
Most social media schedulers publish through each platform’s official API. That works well for ordinary posts, but an API covers only what a platform has opened to outside apps. You can’t add a link sticker to an Instagram story through it, and you can’t pick a TikTok sound from the library. Many schedulers leave those posts out. Some send a reminder at the scheduled time and leave the rest to you.
Slate keeps all of it on one calendar. An account can post by API, by hand with an assigned person and a reviewer, or from a Cloud Phone with a preset you build yourself. This guide covers what APIs leave out and how to choose between the three.
- What platform APIs leave out, according to their own documentation.
- The three ways an account can post in Slate, and when each one fits.
- What to read before you build a preset, and how presets work.
How a regular scheduler works
When a platform has a publishing API, an outside service can post on your behalf. You sign in once on the platform’s own screen, and from then on the service posts on schedule. For Instagram, TikTok, YouTube, X, Facebook, Threads and Pinterest this is a good path, and Slate uses it too.
An API includes only what the platform decided to open, so it leaves gaps of two kinds.
What happens to the posts an API can’t make
Many schedulers leave them out of the schedule. Some send a reminder at the scheduled time and leave the rest to you: you open the preview, copy the caption, switch to the app, add the sticker or sound, and post.
With one account that takes a couple of minutes a day. With twenty accounts it becomes part of someone’s job, and that job needs a schedule, an owner and a way to check the result.
Three ways to post in Slate
In Slate you choose how each account posts: By API, By hand or From a phone. Posts for all of them sit in one queue and one calendar, in each account’s slots.
| By API | By hand | From a phone | |
|---|---|---|---|
| Who posts | Slate, through the platform’s API | The person you assign | A Cloud Phone, following your preset |
| Signing in | Once, on the platform’s sign-in screen, from any browser | The person uses the account as they normally do | You sign in yourself on the phone’s live screen |
| What a post can include | What the API accepts | What that person can add in the app | What your preset describes, where the app’s rules allow it |
| How you know the result | The platform reports it | A reviewer checks what went out | The phone looks at the screen after the run |
| What you can look at | A link to the post | The task, the link and the review | The run history with a frame of each step, and the live screen |
You choose the way for each account and can change it later.
By API
You connect an account on the platform’s own sign-in screen, so your password stays with the platform. From then on its posts go out through the API in the account’s slots.
- Whoever has the account can connect it. If the account is signed in on someone else’s phone or in another browser, send them a link. It works for a week, needs no Never Manual sign-in and goes straight to the platform’s sign-in screen.
- Problems show up before sending. A YouTube video with no title, a pin with no board or an Instagram caption with more than five hashtags stops in the queue with an explanation.
- The result is checked. Slate asks the platform whether the post went out and saves the link to it. If the connection drops, it tries again on its own.
- Stories go out by API on Instagram and Facebook, within what the API accepts.
By hand
By hand is the simplest way to keep a post the API can’t make on your schedule. You choose the person who posts for the account and, if you want a review, the person who checks the work.
Each slot becomes a task for the person who posts, with the file to download and the text to copy. They post in the app as they normally would and mark the task posted, and they can paste the link to the post. The reviewer sees what went out and accepts it, or returns it with a note. A returned post goes back to the same person and keeps its place on the calendar.
We recommend By hand for the two most common cases, an Instagram story with a link sticker and a TikTok video with a sound you picked. Each has its own guide.
From a phone
From a phone means a Cloud Phone runs a preset you built. A Cloud Phone is a physical Android device that we host, or a virtual one in the cloud, and only your workspace uses it. It has apps from the store. You sign in to your accounts yourself on the phone’s live screen, and the sign-in stays on the phone.
A preset is a task you describe in plain words or show once on the phone. Slate turns it into fields, the parts that change from post to post, and you can run it right away or on a schedule. Slate provides no ready-made presets, so you build each one yourself.
How a preset works
Here is a preset for a community post, a format many apps share: a post goes into a community, with a photo and a title.
You write a preset once, and the accounts on that app that post from a phone can use it. A field’s value comes from the post, or from the account if the post leaves it empty. A post with an empty field waits until someone fills it in.
What happens during a run
- A clean start. The app is closed and opened again, so each run starts from the same place.
- The right file. Slate puts the post’s file into the phone’s gallery ahead of time, and the phone finds it by name in the picker.
- Reading the screen. At each step the phone reads the screen as it is and decides what to do next. It doesn’t replay recorded taps, so small changes in an app often don’t matter.
- Checking the result. After posting, the phone looks at the screen and compares it with the task’s own words.
- A record of each step. The run history keeps a frame of each step with a note on what was done.
- Reopen the app on @lisbon.trams12:30:03
- Start a new post in the community “Old trams”12:30:10
- Pick the post’s photo in the gallery12:30:18
- Write the title: “Rain on the old tram line”12:30:26
- Post12:30:31
- Check the community: is the post there?12:30:44
An illustration of a run, as the run history shows it.
When a run can’t finish or isn’t sure
If a run can’t finish, for instance because it keeps going in circles, it stops and shows you the step.
Sometimes an app takes a long time to upload a video, or shows nothing after the button. If a run can’t tell whether a post went out, it asks you instead of trying again. The post gets the status To check, and a question appears in your inbox: Did @northwind’s post go out? The run’s page shows a frame of each step, and you answer from there. The account’s other posts keep their times while that one waits.
When you add posts, Slate skips an account that already has the file queued or posted.
One queue for all three
Once you’ve set how an account posts, its posts take their place in the shared queue and calendar. If a Cloud Phone is busy with another run at that time, the post waits its turn.
Posts by API at 09:00, 18:00
New colors are in. Which one is yours?Today 18:00
By hand · Mon–Fri · 1 a day · Dana
Story with a link sticker: northwind.example/dropToday, with Dana
From Phone 03 at 12:30
Rainy streets · Rain on the old tram lineto check
From Phone 03 at 16:00
Fall line · #fall #colorsTomorrow 16:00
The line under each account’s name says how it posts. Amber is waiting for a person.
Watch and step in
A Cloud Phone has a live screen. You can watch a run as it happens, or use the phone yourself by tapping, typing and scrolling in your browser. While you’re on the phone, scheduled runs wait and show Waiting for the phone. After two minutes without a touch the phone is free again, and what was waiting picks up on its own.
Presets that don’t post
A preset doesn’t have to publish. It can stop at a draft, or run once or on a schedule of its own, as long as the app’s rules and your permissions allow it.
Drafts
The phone uploads the video with its caption and saves a draft. Someone on your team opens it in the app and publishes it.
Upload this video with this caption and save it as a draftA schedule of its own
A preset run can repeat on its own, with its values set in the schedule, such as the same story every Friday evening.
Post this picture as a story with these opening hoursShow it once
You don’t have to write a preset. Press Show it on the phone, do the task once yourself, and Slate writes the preset from the screen recording. If a run fails, Slate goes through it frame by frame and leaves notes for the next one.
Set up your accounts
- Connect what the API covers.In Accounts, add the account, choose By API and sign in on the platform’s screen, or send the link to whoever has the account.
- Assign what needs a person.Choose By hand on the account, then pick the person who posts and the person who checks the work.
- Build a preset where the rules allow it.In Phones → Presets, write the task or show it once on the phone. You can run it right away. Then choose From a phone on the account.
- Add posts.In Media, select files and press Post files. The posts join the shared queue in each account’s slots.
Questions
Is a Cloud Phone an emulator?
A physical Cloud Phone is a real Android device with apps from the store, and we host it for you. A virtual one runs Android in the cloud, and some apps need a physical phone. Only your workspace uses either.
Does Slate come with presets for popular apps?
No. Slate provides no ready-made presets. You describe a task or show it once on the phone, and Slate turns that into your preset.
Can I run a preset on a particular app?
That depends on the app’s rules and on your permissions for the account, so we can’t answer it for you. Read the app’s terms before you build a preset. If you’re unsure, use By hand.
Can accounts that post in different ways share one queue?
Yes. How an account posts is set on the account, and all the accounts’ posts sit in one queue and one calendar.
Why use a phone if the platform has an API?
Usually you don’t need to. The API is faster and simpler. When a post on Instagram or TikTok needs something the API lacks, we recommend By hand.
What happens when an app updates?
The phone reads the screen at each step, so small changes often don’t matter. If a run can’t finish, it stops and shows you where, with a frame of each step.
Will a post go out exactly on time?
A post by API or from a phone starts at its slot. If the Cloud Phone is still busy with another run, the post waits for it to finish, usually a few minutes. A post by hand goes out when the assigned person posts it.
Whose accounts are on the phone?
Yours. You sign in yourself through the live screen. We don’t supply or share accounts.
Schedule your posts in one calendar and build your own presets.
Connect accounts by API, assign the posts that need a person, and add a Cloud Phone when you want to run a preset you built.
Sources
Checked on November 7, 2026.
- Meta: Instagram publishing API, stickers not supported. developers.facebook.com
- TikTok: Content Posting API, direct post fields. developers.tiktok.com
- YouTube Data API: uploading a video, available fields. developers.google.com
- Reddit: Responsible Builder Policy, API access by approval. support.reddithelp.com
- Snapchat: Public Profile API, by allowlist. developers.snap.com