Wire a trigger to an action.

The event that starts a rule.

SocFlow watches your accounts for it, around the clock.

New follower

Fires the moment someone follows a connected account.

Keyword mention

Fires when a post or comment matches a topic or phrase you define.

DM received

Fires on an incoming direct message to a monitored account.

Optional gates on the rule.

A rule only runs its action when every condition passes.

Account age

Skip brand-new or throwaway accounts.

Follower count

Run only above or below a threshold you set.

Verified status

Branch on whether the account is verified.

What the rule does when it fires.

Chain more than one — they run in order.

Send DM

Deliver a direct message from a template you write in plain language.

Like

Like the post or comment that triggered the rule.

Reply

Post a reply, templated or conditional on the trigger content.

Repost

Reshare to your other connected accounts automatically.

When something breaks, you see it first.

Failures aren't buried in a log. A rule that can't run turns red with the reason attached: auth expired, rate limit hit, account disconnected. You fix the cause instead of hunting for it.

One board for every account you run.

Agencies and operators managing 5, 10, or 20 accounts don't get a separate dashboard per client. Every rule, every execution, and every account's health lives on one board — filter by account or platform when you need to zoom in, otherwise it's one view for everything running.

Every time a rule fires, it's logged with what triggered it, what ran, and the result — a real audit trail, not a best-effort notification you might miss.

Send it somewhere else, too.

Not every action belongs inside SocFlow. A webhook action posts the trigger's payload to any URL you give it — your CRM, a Slack channel, an internal tool — the moment a rule fires, so the rest of your stack finds out without polling for it.

A couple of things people ask.

Can a rule use more than one trigger?

Each rule starts from one trigger, but you can run as many rules as you want per account, and chain more than one action off a single trigger.

What happens if an action fails?

The rule turns red on your board with the reason attached — auth expired, rate limit hit, account disconnected — instead of failing silently.

Do filters run before or after the trigger fires?

After. The trigger fires on the raw event, filters then decide whether the action actually runs — so a filtered-out event still shows up in your log, just marked as skipped.

Does every platform support every trigger and action?

No — each platform's list is built against what its API actually exposes. See per-platform coverage.