Follows
Watch a YouTube channel or TikTok profile and analyze the new videos that match your rule.
A follow watches one creator: a YouTube channel or a TikTok profile. Every new upload is checked against a rule you write, and checking is free. A video that matches becomes an ordinary transcription job, charged like any other job, and its result is sent wherever you asked.
You create and manage follows in the console, under Follows, or from an assistant through the MCP server. There is no REST endpoint for them.
Plans
| Prop | Type | Description |
|---|---|---|
| Free | not available | Follows need a paid plan. |
| Starter | 3 follows | Up to 5 analyses per follow in any 7 days. |
| Pro | 10 follows | Up to 20 analyses per follow in any 7 days. |
| Scale | 50 follows | Up to 100 analyses per follow in any 7 days. |
The weekly limit counts analyses, not checks. A job that failed or was cancelled does not use one up.
Rules
A rule can be a description in plain words, exact filters, or both.
- Description — what you care about, in your own words, for example "running shoes and marathon training". Each new video's title and description are judged against it.
- Exact filters — hashtags, mentions, keywords, and whether the video discloses an ad or a paid partnership. Keywords match whole words in the title and description.
Within one kind of filter, any match is enough: two hashtags widen the rule. Across kinds, every kind must match: adding a keyword narrows it. The exact filters run first, so a description only judges the videos that got past them. A rule with nothing in it is refused, because it would match every video.
Editing a rule checks the recently seen videos again. Anything that now matches is offered to you, never run by itself.
What happens to a match
A match is analyzed straight away, unless one of these holds. Then it is listed in the console as Matched, not run:
| Prop | Type | Description |
|---|---|---|
| From before you followed | run it any time | The first check also looks at the creator's few most recent videos. Matches among them are offered, never run by themselves. |
| Paused | run it any time | A paused follow keeps checking uploads but runs nothing by itself. |
| Payment failed | run it once paid | The subscription is past due. Update the payment method, then run the match from the console. |
| Weekly limit reached | not run | The follow already ran its plan's analyses for the last 7 days. |
| Too long for the plan | not run | The video is longer than your plan allows for one job. |
| Not enough credits | not run | The workspace could not cover the analysis when the match came in. |
New uploads are picked up on a schedule, not the moment they are posted. The console shows each follow's recent checks, with a one-line reason for every verdict, the videos that did not match included.
Where results go
A follow can send each finished match to up to five channels:
- Email — to people in the workspace only. Invite someone before adding them.
- Slack — an incoming-webhook URL on
hooks.slack.com. It posts the video, why it matched, and a short excerpt. - Webhook — any
https://URL. It receives the signedfollow.match.completedevent.
A channel hears about a match once its job has completed. A job that fails sends nothing.
A follow's webhook is its own channel. It is not the webhook_url of a job, and it sends a different body: a receiver
that also takes job webhooks tells the two apart by event.
The daily digest
Every morning at 08:00 UTC, each member of the workspace gets one email about its follows: the videos analyzed in the last 24 hours, the matches waiting to be run, and a count for the week. It is only sent on a day with something to report.
Each member turns it off for themselves in Settings → Daily digest, or with the unsubscribe link in the email.