Triggers and actions
The full vocabulary of what a journey can listen for, and what it can do in response.
Every journey is made of two kinds of nodes: triggers (what starts the journey) and actions (what it does). Scrollmark's available triggers and actions vary by platform — Instagram has the deepest support, Facebook is close behind, and TikTok + LinkedIn are narrower.
Use this page as a reference while you build.
Triggers by platform
| Trigger | Fires when… |
|---|---|
| User comments on a post | Someone leaves a comment on a post you pick (or all posts) |
| User sends a message | A new DM arrives. Filter by keyword, emoji, phone number, email, birthday, address, wallet, or "any message". |
| User replies or reacts to a story | A story reply or reaction lands in your inbox |
| User mentions in a story | Someone tags your handle in their story |
| User tags me in a post | Your handle is tagged in someone else's post |
| User tags me in a comment | Your handle appears in a comment on a public post |
| User mentions me in caption | Your handle appears in the caption of a new post |
| User clicks on an ad | Someone clicks a click-to-message ad |
| Rewards threshold | A Social Loyalty user crosses a point tier (used by Reward Tiers) |
| Webhook event received | An external system pings Scrollmark to start a journey |
The DM filter is the most powerful one
User sends a message can filter by keyword, emoji, email, phone, first name, last name, full name, birthday, address, or wallet address — not just keywords. It's the backbone of every "DM us the word X for Y" flow.
| Trigger | Fires when… |
|---|---|
| User comments on a post | Comment on any Facebook page post |
| User sends a message | DM to the page |
| User tags you | Tag mention on a post |
| User leaves a page review | A new page review is posted |
| User replies to a review | Someone replies to an existing review |
| User clicks on an ad | Click-to-message ad click |
| Webhook event received | External webhook |
Reaction triggers (reacts to post, reacts to comment, shares post, likes page, follows page, mentions page) are defined but currently disabled in the builder.
TikTok (beta)
| Trigger | Fires when… |
|---|---|
| Comment on a video | A new comment lands on a TikTok |
| Caption mention | Your handle is in the caption of a new video |
| Comment mention | Your handle is in a comment |
| Direct message | A new DM arrives |
LinkedIn (beta)
Triggers are limited and scoped to page engagement. Check the builder for the current set.
Actions by platform
| Action | Does this |
|---|---|
| Send a direct message | Reaches the user's inbox with text, buttons, images, or product carousels. |
| Reply to a comment | Publicly replies to the comment that triggered the journey. |
| Hide comment | Hides the comment on your post. |
| React to a message | Adds an emoji reaction to the engager's most recent message. |
| Action | Does this |
|---|---|
| Send a direct message | Same as Instagram — rich message builder. |
| Reply to a comment | Public comment reply. |
| Like the comment | Likes the comment from your page account. |
| Hide comment | Hides the comment on your post. |
| Reply to a page review | Posts a reply to a page review. |
| Reply to a page review comment | Replies to a comment underneath a review. |
| Block user | Blocks the user from commenting on your page. |
TikTok / LinkedIn (beta)
Both platforms support Send a direct message and Reply to a comment. TikTok also has Like a comment and Hide negative comment in the pipeline.
Flow-control nodes
These aren't triggers or actions — they shape the flow itself. Every platform supports them.
| Node | What it does |
|---|---|
| Time Delay | Pause the journey for minutes, hours, or days before the next step. |
| Condition | Branch the flow based on a check. See list below. |
| Subnode | A quick-reply button attached to a DM. Each button routes the user to a different downstream path. |
Conditions you can branch on
Inside a Condition node, pick one of these checks:
| Condition | Branches on… |
|---|---|
| User follower count | How many followers the engaging user has |
| Journey run | Whether the user has been through a specific journey before |
| Contact info | Whether Scrollmark has the user's email or phone |
| Account type | Business or personal account |
| Actions over time | How many times the user has triggered something recently (spam guard) |
| User has tags | Any tag you've applied to the user |
| Age verification | Verified age gate |
| User follows | Whether the user follows your account |
| Loyalty points | Current Social Loyalty point balance |
| Compare variable | Any variable against any value (escape hatch) |
| Engagement date/time | The date or time the event fired |
| Engagement time | Just the hour |
| Engagement day | Day of week |
| Make your own | Roll your own boolean |
Actions over time is your spam shield
The Actions over time condition lets you cap how many times a journey runs per user per window. "No more than 1 DM per user per 24 hours" is a great safety net on any keyword flow.
DM message types
Inside Send a direct message, each message bubble can be one of:
- Simple text — plain message
- Quick reply — text plus tappable buttons that route the user to a sub-flow
- Button message — text plus outbound link buttons
- Image — image attachment
- Video — video attachment
- Carousel — swipeable card deck
- Catalog (Facebook) — product picker from a connected catalog
You can chain multiple bubbles in a single Send-DM step — text first, then image, then buttons.
Where triggers and actions map to code
If you're talking to the Scrollmark support team, they may reference the internal names — things like INSTAGRAM_DIRECT_MESSAGE or FACEBOOK_SEND_DIRECT_MESSAGE. These are the same triggers and actions, just in backend notation. Use the friendly names above when you're building in the UI.