SuperBrief - Triggers & Actions
Last updated: April 30, 2026
SuperBriefs structure your creator collaborations into a clear lifecycle: applications, approvals, tasks, deliverables, and rewards. Automations can fire at any point in that lifecycle so you can onboard, nudge, and reward creators without manual follow-up.
This article covers all SuperBrief triggers and the dedicated "Brief" actions.
The SuperBrief lifecycle at a glance
A creator's journey through a SuperBrief typically follows these stages:
Applies → the creator submits an application
Approved / Declined → you review the application (if open brief)
Added to the brief → approved creators become brief participants
Works through tasks → Campaign Terms, Info Collection, Upload Content
Receives gifting rewards (if applicable)
Submits deliverables → which get reviewed, approved, or sent back for feedback
Each of these transitions has a matching trigger.
Trigger: Application Status Changed
Fires when a creator's application to a SuperBrief moves between states. This is tied to the open application functionality, which you can create a public brief link and send to creators to apply. (See 📄 How to Receive and Manage Creator Applications in a SuperBrief)
Statuses: Pending, Approved, Declined.
Configuration:
Application status (required) — which status change you want to listen for.
Common use cases:
Welcome approved applicants with the brief details and a magic link
Send a polite decline message to rejected applicants
Notify your team when a new application is received (pair with reenterable off to fire only once per application)
Tip. Use the brief_magic_link variable to give approved creators one-click access to the brief.
Trigger: Creator Added
Fires when a creator is added to a SuperBrief. This can happen in two ways:
You add them manually in the SuperBrief editor
An automation runs the "Add a Creator to a SuperBrief" action (see below)
Use this trigger to onboard new brief participants — send them the brief, explain next steps, or start a deliverable reminder sequence.
Not the same as Application Status Changed. Application Status fires on the approve/decline decision. Creator Added fires when the creator is actually enrolled in the brief. If your application flow is a manual review, the two events happen in quick succession. If you skip applications and add creators directly, only Creator Added fires.
Trigger: Task Status Changed
Fires when one of a creator's tasks inside a SuperBrief changes state.
Configuration (two steps):
Task type (required). Pick which type of task you care about:
Campaign Terms
Info Collection
Upload Content
Partnership Ads (only shown when the Meta Ads integration is configured)
Status (required). The available statuses depend on the task type you picked.
For Campaign Terms and Info Collection
Three statuses: Pending , In Progress and Completed
For Upload Content — the full lifecycle
Upload Content has a richer 7-state lifecycle, so when you pick Upload Content as the task type the status list expands:
Status | Meaning |
| Deliverables are approved |
| Task exists, nothing uploaded yet |
| Creator uploaded, awaiting your review |
| You gave feedback — creator needs to revise |
| Upload deadline has passed |
| Approved but not posted to social by the posting deadline |
| Content is live on social |
Common use cases:
Congratulate creators when they complete Campaign Terms
Remind creators stuck in
Waiting adjustmentThank creators once their content is
PostedEscalate internally when a task is
Late for submission
Reenterable consideration. Upload Content cycles — Pending approval → Waiting adjustment → Pending approval → Approved is common. If you want your automation to fire on each cycle, turn the Reenterable toggle on. See 📄 Automations Walkthroughfor details.
Trigger: Deliverable Status Changed
Fires when an individual deliverable (a single piece of content the creator submitted) changes state. This is one level more granular than Task Status Changed — a single Upload Content task can contain multiple deliverables, each with its own lifecycle.
Statuses:
Status | Meaning |
| Creator uploaded the deliverable, awaiting your review |
| You gave feedback — creator needs to revise |
| Deliverable is approved |
| Approved but not yet posted to social by the posting deadline |
| Deliverable is live on social |
Configuration:
Deliverable status (required) — the target status you want to react to.
Use this when you want to react to a specific deliverable review decision rather than the overall task state.
Trigger: Gifting Reward Status Changed
Fires when a gifting reward attached to a SuperBrief changes state. The status picker reuses the full gifting lifecycle, so you can target any of these states:
Status | Meaning |
| Creator is in the campaign but hasn't claimed their gift yet |
| Creator has claimed the gift; order is confirmed on Shopify |
| Order is being processed |
| Shopify order has been placed |
| Ready for fulfillment |
| Gift has shipped |
| Gift has been delivered |
| Creator posted their content after receiving the gift |
| Can't ship — creator's shipping address isn't on file |
| An error happened; the reward can be retried |
| Creator's recurring gifting cycle is paused |
| Creator's recurring gifting cycle was skipped for this cycle |
| Creator was not eligible for the reward |
| The reward expired |
Configuration:
Gifting reward status (required) — the status you want to listen for.
Use this to confirm reward delivery, follow up with creators who haven't claimed yet, or notify your ops team when high-value rewards ship.
Action: Add a Creator to a SuperBrief
This action enrolls a creator into a SuperBrief as part of an automation. It's the programmatic version of the manual "Add creator" button.
What you configure:
SuperBrief: which brief to enroll the creator into.
Skip if creator is already in this brief: when on, skips the action for creators already enrolled in the brief. On by default.
Send invitation email to creator: when on, the creator receives the standard brief invite email. On by default.
What happens when it runs:
The creator is validated (email, social handles present).
If they were previously removed from the brief, they're reactivated rather than duplicated.
If "Send invitation notification" is on, they receive the standard brief invite.
Post-enrollment workflows (like any "Creator Added" automations you have) will fire automatically.
Best paired with: the Discovery AI List Creator Status Changed trigger, for an end-to-end "find → qualify → enroll" flow.
Variables reference
These variables are available to Email and DM steps downstream of any SuperBrief trigger. Insert them from the variables picker in any message or email action. They're exposed in addition to the default creator variables (first name, email, Instagram handle, etc.) documented in the 📄 Automations Walkthrough.
Variable | Description |
| The SuperBrief's name |
| Public application page for the brief — |
| Creator's personalized, pre-authenticated link to the brief (7-day expiry). Use this to give approved creators one-click access |
| How the creator joined the brief: self sign-up or added manually |
| How the creator was approved: manually reviewed or auto-approved |
Heads up: {{ program_signup_url }} is not a SuperBrief variable — it points to the creator portal's program sign-up, not the brief's application page. For brief sign-ups, use {{ brief_signup_url }}.
Choosing the right trigger
I want to react to... | Use this trigger |
A creator applying or being reviewed | Application Status Changed |
A creator being added to the brief | Creator Added |
Task progress (across all task types) | Task Status Changed |
A specific deliverable decision | Deliverable Status Changed |
Gifting reward state changes | Gifting Reward Status Changed |