> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overlap.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> Trigger a workflow when one of your published posts starts trending.

# Trending post

<Warning>
  **Limited availability:** This trigger is rolling out to selected organizations. If you don't see **Trending Post** in the trigger panel, it isn't enabled for your organization yet — reach out to [support@overlap.ai](mailto:support@overlap.ai) to request access.
</Warning>

> Runs your workflow automatically when a post you published starts trending — outperforming your account's own typical views. The workflow receives the trending post's clip, so you can send a proven winner to your other platforms the moment it takes off.

<Info>
  ### Schema

  * **Input**: None (this is a trigger)
  * **Output**: The trending post's clip, ready for editing or export nodes such as **Post to Social**
</Info>

## What counts as trending

Overlap refreshes each social account's platform-specific 90-day baseline daily, then scores every recent post hourly against that history. An account-platform pair needs at least 20 historical posts before Overlap can make a reliable comparison; until then, it does not fall back to a company-wide average and does not send a trending notification.

A post needs two analytics snapshots between 15 minutes and 12 hours apart. It must add at least the greater of 50 views or 5% of the account's median, and it must have at least the greater of 1,000 total views or 50% of that median. Passing those evidence checks is not enough by itself: the post must also either reach the account's historical 90th-percentile view count or reach its median while gaining views at least 5× faster than the account's normal daily pace.

Qualifying posts are ranked by a standout index that compares their p90 overperformance and their recent velocity. Overlap selects at most two new standout posts per company in any rolling 24-hour window. A selection that cools off stops appearing as actively trending, but its slot remains occupied until that 24-hour window expires so customers cannot receive a stream of ordinary-post alerts.

This trigger watches the selected trending posts and fires your workflow with the underlying clip. It does not apply another threshold after trending detection.

## Email alerts

When Overlap selects a trending post, every active member of the organization who has **Email notifications** enabled receives the standout-post email. The email includes the clip thumbnail, aspect ratio, title, description, and current view, like, and share counts. Its link opens the trending post directly on the Analytics post-detail page and preserves the Posts tab and views sort as the return destination.

An organization receives at most two trending-post emails in any rolling 24-hour period, one for each distinct standout post. Overlap sends no more than one email per hourly scan, starting with the highest-ranked standout that has not already used a slot. Each post is permanently marked after successful delivery, so a post that remains trending beyond 24 hours is not emailed again. Delivery retries reuse the same provider idempotency key, so an uncertain retry does not create a duplicate message.

Email delivery starts with posts newly selected after live alerts are enabled; previously selected trending posts are not backfilled.

If a saved member address is rejected by the email provider as invalid, Overlap skips that address permanently for the post. Valid opted-in recipients still receive the alert, and the invalid address does not leave the organization's notification queue stuck retrying.

## Add the node

Open **Workflows** from the left sidebar and click **New** to open the workflow builder.

Choose **Trending Post** from the trigger panel — it appears only for organizations the trigger has been enabled for. Connect it to the rest of your workflow — the most common pattern is straight into **Post to Social** for the platforms you want the winner republished to.

## Settings

* **Which platforms to monitor** — select one or more platforms to react to. Leave everything unselected to watch all platforms.
* **Which accounts to monitor** — select one or more connected accounts to react to. Leave everything unselected to watch all connected accounts.
* **Allow duplicate posting** — off by default, so the trending clip is never re-posted back to the account it already trended on. A second account on the same platform still receives the repost.

## How often it triggers

The trigger fires **at most once per clip, per account it trended on**:

* A post triggers the workflow at most once, and a post that stops trending and later trends again does not re-trigger it.
* Re-posts of the same clip to the same account (for example, scheduled intermittent reposts) count as the same event — the trigger will not fire again for them.
* The same clip trending on a **different account** is its own event and triggers the workflow again.
* Posts this trigger itself created never re-trigger it, no matter how well they perform — including any later scheduled reposts of them. This is what keeps a winning clip from looping through the workflow indefinitely.

## Watching it run

Opening the workflow shows the usual launcher — the URL box, upload target and project
picker — with **Previous Runs** beneath it. When one of your posts trends the trigger supplies
the clip itself, so nothing needs to be pasted for those runs.

You can also drop in a video by hand. A pasted link or uploaded file is run through the
workflow as a single clip spanning the whole video: it is normalized, then handed to **Post to
Social** exactly as a trending clip would be, so it is reposted to every account the workflow
is configured for. Its card in Previous Runs reads `Manual → {platforms it was posted to}`.

Each card in Previous Runs is one repost:

* the badge counts the accounts that repost went out to, rather than clips found
* the line beneath reads `{platform it trended on} → {platforms it was reposted to}` as icons
* clicking a card opens the clip that was reposted

A workflow that pairs this trigger with a manual one shows the same launcher, and its Previous
Runs use the standard project cards instead.

## How it pairs with Post to Social

The clip that reaches your **Post to Social** node is the exact clip that went trending — the same cut, not a re-edit. Enable **Prevent Double Posting** in the Post to Social node's cadence settings so the workflow never re-posts to a platform that clip is already on.

## Notes

* Trending detection runs hourly, and your workflow fires as soon as a post is detected as trending — there is no separate waiting step in between.
* A company can have at most two newly selected trending posts in a rolling 24-hour window.
* Email alerts go only to organization members who have email notifications enabled, with at most two trending emails per organization in a rolling 24-hour period.
* A specific post produces at most one live trending email, even if it continues trending or qualifies again after the rolling window resets.
* If that first attempt doesn't go through, the post is queued and retried automatically over the following hour, so a workflow isn't lost to a temporary hiccup.
* Building the workflow while one of your posts is already trending fires it right away, rather than waiting for the next check.
* Deactivating the workflow removes the trigger's subscription — it stops firing immediately.
* The trigger remembers which posts it has already fired for, across config edits.