TokPortal + Google Sheets: Run Spreadsheet-Driven TikTok Campaigns

You're already planning your TikTok campaigns in a spreadsheet. The video URLs are there. The captions are there. The target accounts, the post times, the sounds — all in rows and columns, color-coded, shared with your team. Then someone has to manually log into each account and actually post it. That bottleneck is the entire problem. The plan is automated. The execution is not.

This is exactly the use case TokPortal's API was built for. When your spreadsheet can trigger real posts — through real TikTok apps, on real devices, in real countries — the gap between planning and publishing collapses to zero. Here's how to build it.

Every serious content operation, from a two-person DTC brand to a 20-client agency, runs some version of the same Google Sheet: rows for each piece of content, columns for account, caption, date, format, sound, status. It's collaborative, flexible, and universally understood. No new tool adoption. No onboarding your client to yet another SaaS.

The problem has never been the spreadsheet. It's that the spreadsheet has always been a planning artifact, not an execution layer. You finish the planning column, then start the manual posting grind. Every row is a task someone has to do by hand. At five accounts that's manageable. At fifty, it's a nightmare. At two hundred, it's impossible.

Connecting Google Sheets to TokPortal via the API — or through no-code tools like n8n, Make.com, or Zapier — turns your existing planning sheet into a live posting pipeline.

Before building the workflow, it helps to understand exactly what columns map to what API parameters. TokPortal's REST API — documented at developers.tokportal.com — gives you programmatic control over essentially every posting variable. That means every column in your sheet can correspond to a real posting action.

There's no single right architecture — the best connection depends on your team's technical comfort and the complexity of your campaign. Here are the three main approaches, from simplest to most powerful.

n8n is the most flexible no-code option for this use case because it handles looping through spreadsheet rows natively, supports conditional logic, and can write status updates back to your sheet after each post. Here's the core workflow structure:

Make.com (formerly Integromat) is an excellent alternative if your team already uses it. The scenario logic mirrors n8n: a Google Sheets module watches for rows with a trigger status, an HTTP module sends the video details to the TokPortal API, and a final Google Sheets module writes the result back. Make's visual canvas makes it easy to hand off to a non-technical team member for maintenance.

One Make-specific tip: use the 'Watch Rows' trigger rather than polling all rows on a schedule. This fires the scenario only when a new or updated row appears, keeping your operation usage low and your latency near-zero.

If you want to keep everything inside Google Workspace, Apps Script is a powerful option. A time-driven trigger runs a function every 10 minutes, iterates through rows where Status is 'Ready' and the scheduled time has passed, calls the TokPortal REST API via UrlFetchApp.fetch(), and writes results back to the sheet. No external subscriptions, no third-party tools. The full API reference at developers.tokportal.com documents every endpoint you'll need. This approach is ideal for technical marketers who want a self-contained solution that lives entirely inside their Google account.

The way you structure your Google Sheet determines how clean your automation logic is. Here's a proven column setup for a multi-account campaign sheet:

The spreadsheet model truly shines when you're managing campaigns across multiple accounts — say, 15 TikTok accounts across the US, UK, Germany, and Brazil for a single product launch. Without automation, that's 15 manual logins per posting day. With a spreadsheet-driven pipeline, it's 15 rows that all fire at their respective scheduled times with zero additional effort from your team.

The workflow doesn't change. You just have more rows. Each row has a different Bundle ID pointing to a different country's TokPortal account. The automation treats each row identically. You can localize captions per row (column), use country-specific sounds (column), and stagger post times by timezone (column). The spreadsheet makes the complexity manageable because every variable is visible and editable in one place.

A one-way pipeline — sheet to TokPortal — is useful. A two-way pipeline is a campaign management system. TokPortal fires webhooks for real-time events: post published, post failed, account warming complete, and more. Here's how to use them:

In your n8n or Make workflow, add a webhook receiver node. When TokPortal fires a video.published event, the webhook payload includes the Row ID you passed at post time. Your workflow looks up that row in the sheet and writes 'Posted' to the Status column along with the actual timestamp. When a video.failed event fires, it writes 'Failed' and the error reason. Your sheet becomes a real-time campaign dashboard that updates itself — no manual checking, no status meetings just to find out if things posted.

Full webhook event documentation is available at developers.tokportal.com.

Spreadsheet-driven automation is a major step forward. But there's a level beyond it: AI agents that generate content, populate the sheet, and trigger posting autonomously — no human input required between strategy and publish. TokPortal's MCP server enables exactly this. An agent like Claude or a custom GPT can call TokPortal's API directly: create accounts, schedule videos, check analytics, and respond to performance data. The spreadsheet becomes optional — the agent manages state in whatever structure makes sense for the workflow. For teams already experimenting with AI-assisted content creation, this is the natural next step after nailing the spreadsheet pipeline.