Skip to main content
New in version 0.3.0

TikTok automationthrough Android mobile API requests.

Warm up new accounts, publish videos, update profiles and run scheduled scenarios across your whole account network. For every account you can see what is done and what needs your attention.

  • Batch launches One action or scenario for many accounts in a single launch
  • AI agents Claude and Codex work in the workspace with your role
  • Planned warm-up New accounts get ready for their first posts
  • No open tab needed Schedules run on the server
Mobile API requestsAndroid

Every account has its own permanent proxy

Demo: an operator selects TikTok accounts and runs a three-step scenario (session check, profile update and video publishing). Each account gets its own outcome, and the run continues after the tab is closed.

Where to start automating TikTok

Build a scenario from ready-made actions and run it on every selected account at once.

  1. Session check

    The scenario moves on only after the check confirms the account’s sign-in is valid.

  2. Profile

    An avatar from the media library, a name and a bio, shared by all accounts or set for each one.

  3. Warm-up

    A warm-up plan built on keywords from your niche, in the time zone you choose. Pause and resume it at any time.

  4. Groups and tags

    The account gets a tag, so it is easy to pick for the next runs.

  1. Schedule

    The scenario starts at the times you pick, in your time zone.

  2. Session check

    An account with an invalid sign-in is skipped while the rest carry on.

  3. Video publishing

    One video for every account or a different one for each, with a caption and branded or AI-generated content labels.

  4. Statistics

    After posting, the scenario refreshes follower and view counts and shows when they were recorded.

  1. Values

    Name, bio and avatar shared across the batch or set for each account, and a username of its own for each.

  2. Pre-launch check

    Before the launch you see which accounts are ready, with a reason for each one that is not.

  3. Launch

    The batch starts with one action. Accounts run in parallel up to your workspace’s threads, and the rest wait in the queue and start on their own as a thread frees up.

  4. Confirmation

    Each account’s status shows whether TikTok has confirmed the new name, bio and avatar.

For teams that run TikTok account networks

Your own network, a client’s or a regional one: every account sits in one workspace, and groups and tags split the catalog by stage, client or city.

Your whole account network in one launch

New accounts go through warm-up, each runs through its own permanent proxy, and scheduled scenarios publish videos across the whole network at once.

What they automate

  • Warm-up for new accounts in batches
  • A permanent proxy for every account
  • Scheduled posting across the whole network

Client accounts in one workspace

Each client has a group, operators run actions only where they are allowed to, and every account’s outcome is visible without spreadsheets.

What they automate

  • Warm-up for new client accounts
  • Posting on an agreed schedule
  • Separate permissions for every operator

One campaign across every city

Regional accounts publish one shared video, and each city gets its own caption and posting time.

What they automate

  • One video with a caption for each city
  • Schedules in the right time zone
  • Consistent profiles across the network

One video across your whole network

The same job done by hand and with one scenario launch.

By hand: Accounts one by one. With Syndikat: One scenario launch.

  • How it runsBy hand: A phone or browser for each accountWith Syndikat: Android mobile API requests
  • Signing inBy hand: Signing in to each account by handWith Syndikat: Sessions are kept on the server
  • PublishingBy hand: One account at a timeWith Syndikat: The whole batch in one launch
  • TimingBy hand: Whenever someone is freeWith Syndikat: On schedule, in your time zone
  • OutcomeBy hand: A spreadsheet kept by handWith Syndikat: A status and journal for every account
  • FailuresBy hand: Unclear whether the post went outWith Syndikat: Checked before any retry

From a list of accounts to a verified outcome

The four steps every TikTok account goes through.

  1. Import the list

    Paste usernames or upload a TXT or CSV file. Each row shows a result: added, duplicate in list or invalid name.

    Demo of the step in the workspace

  2. Confirm sign-in

    Sign-in starts separately for each account. The code from TikTok’s email goes into that account’s own form, and the account is then ready for scenarios.

    Demo of the step in the workspace

  3. Run a scenario

    Steps run in order. The pre-launch check shows which accounts are ready and gives a reason for each one that is not.

    Demo of the step in the workspace

  4. Review the outcome

    Every account moves on its own. Outcome groups and the run journal show what is done and what still needs checking.

    Demo of the step in the workspace

Demo of the step in the workspace

Work continues after you close the tab

Schedules run scenarios at the right time in your time zone. The queue, steps and journal run on the server, and you only need the browser to see the outcome.

Today’s schedule, Europe/Kyiv

  • 09:00 Morning post, 24 accounts
  • 13:30 Session check, 64 accounts
  • 19:00 Evening warm-up, 18 accounts

Automation without duplicates or surprises

A scenario never repeats an action blindly and never runs a step on an account that lost its sign-in.

Sessions stay on the server

Each account’s session is kept on the server together with the proxy assigned to it. The account owner types the code from TikTok’s email, and we never store it.

No duplicate posts

If an action’s outcome is unknown, the service checks it first. A retry happens only when the action was never sent, so the same post never goes out twice.

Steps wait for a session check

The next step starts only once a session check confirms the session. Otherwise the account is skipped, and you can see why.

Honest statuses

“Queued”, “Sent” and “Confirmed by TikTok” are shown separately, so you can see what actually changed.

Separate workspaces

Each team sees only its own accounts and tasks. Someone else’s data cannot be found, even with a direct link.

Everyone sees and does only their part

The owner allows individual actions on each account. Access is checked before every run, so once it is revoked, no new work starts.

Choose a role
OwnerAdminOperatorViewer

Invites members, connects accounts and grants permissions.Builds scenarios and runs actions on every account in the workspace.Runs actions on the accounts where they are allowed to.Views outcomes and the journal but changes nothing.

Invites members and grants permissions
YesNo
Builds scenarios and manages media
YesNo
Runs actions and scenarios
YesWith a separate permissionNo
Deletes posts
YesWith a separate permissionNo
Sees outcomes and the journal
Yes

Tools for everyday work

Everything your team does with accounts every day, in one workspace, without spreadsheets or switching between phones.

Catalog and batch actions

Groups, tags, filters and selection across several pages. An action runs only for accounts that pass the pre-launch check.

Profile and statistics

Account followers and likes, plus views, comments, shares and saves for every video. Each number shows when it was recorded.

Publishing and media

Videos and avatars live in folders and plug into any action or scenario. Archiving never stops tasks that already use a file.

Inbox and journal

Unknown outcomes, blockers and tasks awaiting input in one place. The journal keeps every workspace event.

AI agents in your workspace

Create a key in your profile, and Claude, Codex or another MCP client works with your role and permissions: it imports accounts, runs actions and scenarios, adds media and reads the journal.

Questions about TikTok automation

What exactly can I automate on TikTok?

Session checks, profile updates (username, name, bio, avatar), warm-up on a plan, video publishing with captions, statistics refreshes, groups and tags, and deleting your own posts. Run actions on their own or combine them into a multi-step scenario.

Is it safe for my accounts?

Each account runs through its own permanent proxy, and new accounts go through warm-up before their first posts. We never store confirmation codes. The next step starts only after a successful session check, and an unknown outcome is checked before any retry, so a post never goes out twice.

Do I need phones or a device farm?

No. Every action runs through Android mobile API requests from our servers. You only need a browser, and the account owner needs access to their email to enter the confirmation code.

How does warm-up work?

You choose a start date, a time zone and keywords from your niche. Warm-up follows a plan, and the workspace shows how many sessions are already done. You can pause and resume it.

How does mass posting work?

Upload a video to the media library, select accounts and write a caption. Publish right away or add it to a scheduled scenario, where the video and caption can be set for each account.

Can I work through AI agents?

Yes. Create a key in your profile and add the MCP server address to Claude Code, Codex or another MCP client. The agent works with your role and permissions: it imports accounts, runs actions and scenarios, adds media and reads the journal. Only the account owner enters TikTok confirmation codes.

Does it work for a large account network?

Yes. Your workspace runs as many accounts at the same time as it has threads, and the rest wait in the queue and start automatically. Split accounts into groups and tags, then run actions and scenarios in batches or on a schedule for each group.

Does work continue after I close the site?

Yes. The queue, scenarios and schedules run in the background. When you come back, you will see each account’s outcome and the event journal.

What if only part of a batch succeeds?

Open the batch and check each account. An unknown outcome is checked first, and a repeat run starts from the first unfinished step.

How is workspace sign-in different from connecting TikTok?

Sign-in opens your workspace, and each TikTok account is connected separately. A connected account stays ready to work while its session is valid.

Which TikTok confirmation methods are supported?

When TikTok asks for a code from email, the account owner enters it by hand. SMS confirmation is not available yet.

Connect your accounts and run your first scenario

Sign up and import your list of accounts. If your team already invited you, just sign in.