Automations overview

Automations answer the people your content brings in. Someone comments a word on a post; they get a DM. Someone taps your link in bio; a flow starts.

An automation is a trigger plus an ordered list of actions.

Triggers

Trigger	Fires when
Comment keyword	A comment on your post contains a keyword
DM keyword	An inbound DM contains a keyword
Story reply	Someone replies to your story
Story mention	Someone mentions your account in their story
New follower	Someone follows your account
Link-in-bio tap	A visitor taps a link in your bio
Referral link entry	Someone enters through a referral link

Actions

Sending actions: send DM, send link, send comment reply.

Flow actions: wait / delay, condition (if/else), stop if, randomizer (split), go to flow, add tag, remove tag, set custom field, notify a human, call webhook.

Every message is written by a human

There is no action that composes outbound text with a model at send time. That was removed from the product deliberately, and it is not coming back without a new decision.

The reason is narrow and worth stating: a model composing a message in the moment can invent a price, overstate what a service does, or improvise advice to someone describing an emergency, and no send-time guard catches wrong grounding, only absent grounding. Every message an automation sends is text a person wrote and can read before it ships.

So automations are powerful and dumb, on purpose. The intelligence in this product is upstream, in what you write.

Status

An automation is draft, active or paused. Only active ones fire, and you can pause one without losing its configuration or its run history.

Before you arm it

Test it. Testing before you arm it covers dry runs, and staying inside platform rules covers the constraints that decide whether a message is allowed to send at all.

Availability

The automation suite is a paid feature. On TrendSuite Lite it appears in the simplified form described in comment-to-DM.