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.
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.
Every account has its own permanent proxy
Build a scenario from ready-made actions and run it on every selected account at once.
The scenario moves on only after the check confirms the account’s sign-in is valid.
An avatar from the media library, a name and a bio, shared by all accounts or set for each one.
A warm-up plan built on keywords from your niche, in the time zone you choose. Pause and resume it at any time.
The account gets a tag, so it is easy to pick for the next runs.
The scenario starts at the times you pick, in your time zone.
An account with an invalid sign-in is skipped while the rest carry on.
One video for every account or a different one for each, with a caption and branded or AI-generated content labels.
After posting, the scenario refreshes follower and view counts and shows when they were recorded.
Name, bio and avatar shared across the batch or set for each account, and a username of its own for each.
Before the launch you see which accounts are ready, with a reason for each one that is not.
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.
Each account’s status shows whether TikTok has confirmed the new name, bio and avatar.
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.
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
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
Regional accounts publish one shared video, and each city gets its own caption and posting time.
What they automate
The same job done by hand and with one scenario launch.
By hand: Accounts one by one. With Syndikat: One scenario launch.
The four steps every TikTok account goes through.
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
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
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
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
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
A scenario never repeats an action blindly and never runs a step on an account that lost its sign-in.
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.
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.
The next step starts only once a session check confirms the session. Otherwise the account is skipped, and you can see why.
“Queued”, “Sent” and “Confirmed by TikTok” are shown separately, so you can see what actually changed.
Each team sees only its own accounts and tasks. Someone else’s data cannot be found, even with a direct link.
The owner allows individual actions on each account. Access is checked before every run, so once it is revoked, no new work starts.
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.
Everything your team does with accounts every day, in one workspace, without spreadsheets or switching between phones.
Groups, tags, filters and selection across several pages. An action runs only for accounts that pass the pre-launch check.
Account followers and likes, plus views, comments, shares and saves for every video. Each number shows when it was recorded.
Videos and avatars live in folders and plug into any action or scenario. Archiving never stops tasks that already use a file.
Unknown outcomes, blockers and tasks awaiting input in one place. The journal keeps every workspace event.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Open the batch and check each account. An unknown outcome is checked first, and a repeat run starts from the first unfinished step.
Sign-in opens your workspace, and each TikTok account is connected separately. A connected account stays ready to work while its session is valid.
When TikTok asks for a code from email, the account owner enters it by hand. SMS confirmation is not available yet.
Sign up and import your list of accounts. If your team already invited you, just sign in.