TokPortal Webhook Events: Complete Reference Guide

You scheduled a video, it posted, and your downstream system has no idea it happened. Your CRM still shows the campaign as pending. Your n8n workflow is waiting for a trigger that never fires. Your team is manually checking dashboards to confirm what actually went live.

This is the exact problem webhooks solve — and why TokPortal's event system exists. Instead of polling an API every few minutes to ask did something happen?, your infrastructure gets told the moment it does. This guide covers every event TokPortal emits, what the payloads look like, and how to connect them to your stack so your automation runs without babysitting.

TokPortal's webhook system is part of the TokPortal REST API. When something meaningful happens on the platform — a video posts successfully, an account finishes warming, a bundle is created — TokPortal sends an HTTP POST request to a URL you define. Your server receives it, processes it, and reacts in whatever way your workflow demands.

This is fundamentally different from polling. Polling burns API rate limits, introduces lag, and requires infrastructure to run continuously. Webhooks are push-based: zero lag, no wasted requests, and your system only does work when there's actually something to act on.

Every webhook payload from TokPortal follows a consistent structure: an event field identifying what happened, a timestamp, and a data object with the full context of that event. The full schema reference lives at developers.tokportal.com.

TokPortal organizes its events into four categories: account lifecycle, video lifecycle, warming, and analytics. Here's what each one means and when you'd act on it.

TokPortal webhooks are raw HTTP events — which means they connect to anything that can receive an HTTP request. Here's how that maps to the most common automation tools in the ecosystem.

n8n: Use the Webhook node as your trigger, then chain it to HTTP Request, Airtable, Slack, or any of n8n's 400+ integrations. A typical flow: video.posted → update campaign row in Airtable → post confirmation to Slack → trigger analytics logging. The TokPortal n8n integration guide walks through the exact node configuration.

Make.com: Drop a Webhooks module as your scenario trigger. Make's visual canvas makes it straightforward to branch logic — route video.failed events to an alert path and video.posted events to a reporting path in the same scenario. See the TokPortal Make.com integration for setup details.

Zapier: Use Zapier's Catch Hook trigger. TokPortal fires the webhook, Zapier parses the payload, and you map fields to downstream actions across 5,000+ connected apps — HubSpot deal updates, Google Sheets logging, email notifications. Full setup at the TokPortal Zapier integration page.

Custom backend / AI agents: If you're building a custom pipeline or running AI agents, TokPortal's MCP server gives your agents native access to TokPortal events and actions without building webhook plumbing from scratch. An agent can listen for bundle.ready, decide what video to post based on campaign logic, call the upload endpoint, and await video.posted — all autonomously.

Pipeline 1 — Full campaign automation for agencies: bundle.created → trigger profile setup API calls → await bundle.profile_updated → start niche warming → await warming.completed → schedule first content batch → await video.posted → notify client via email → begin analytics tracking via analytics.snapshot. This pipeline runs zero human touchpoints from account creation to live content.

Pipeline 2 — UGC launch for e-commerce: Upload 20 videos across 10 accounts on launch day. Listen for video.posted per account. When all 10 fire, trigger a Slack message to the team: all accounts live, campaign is running. If any video.failed events arrive, auto-retry with the backup video variant. Full UGC scaling patterns are covered in the UGC at scale use case guide.

Pipeline 3 — Milestone-triggered budget reallocation: Listen for analytics.milestone_reached at the 50K view threshold. When it fires, automatically queue three additional videos to the same account to ride the algorithmic momentum. This is the kind of reactive distribution that manual management simply can't execute fast enough.