Steps

Steps are grouped in the palette as Accounts, Actions and Annotations. Most act on the accounts that reach them, one acts on your proxies.

Choosing and splitting accounts #

Select accounts #

Decides which accounts flow into the steps below it: all of them, a set of filters, or a hand-picked list. Tags are resolved when the automation runs, so a step aimed at a tag follows that group as you tag and untag accounts.

Placed after an event trigger, this replaces the accounts the trigger handed over.

If / Filter #

Splits the incoming accounts by conditions into a Matches branch and a No match branch. Connect either, or both, or only the one you care about.

Conditions cover four areas:

Operators are "is at least", "is at most", "is exactly", "is enabled / present", "is disabled / missing", and the two time windows. Every condition on a filter must hold for an account to match.

CS2 inventory size is the one to filter on for storage work: it counts what occupies CS2 inventory slots, which is loose items plus the storage units themselves, and that is what the 1,000 slot cap applies to.

Gate #

Continues only when at least the number of accounts you set reach it. Below that, the path simply ends.

This is what stops a "find banned accounts, then notify me" flow from sending you a notification every morning saying nothing was found.

Acting on accounts #

Run task #

Creates a task for every account that reaches it, of any task type you could create by hand.

The run holds here until those tasks finish, then splits: accounts whose task Succeeded go down one branch, accounts whose task Failed go down the other. Connecting the failure branch to a notification is how you find out about problems without watching the Tasks page.

Add / remove tags #

Tags or untags every account reaching the step. Tags can be created here as you type.

Removing the tag the accounts were selected by is fine. Later steps keep working on the accounts that reached this one, not on a re-resolved tag.

Wait #

Parks the branch for a duration in minutes, hours or days. The run sits in Waiting and picks up on its own.

Use it to leave room between steps that would otherwise stack up, for instance waiting an hour after a trade before checking inventories.

Testing proxies #

Test proxies #

Runs the same health check as the Test button on the Proxies page, on a schedule or anywhere else in a flow. Pick All active proxies, By group, or Pick proxies, which opens the proxy picker for a hand-picked or filtered set.

The run sits in Waiting until the check finishes, then continues with the same accounts it received. The step tests proxies, not the incoming accounts, so it also works directly after a schedule trigger with no select step in front.

Group membership and filter-based picks are resolved when the automation runs, so a weekly check of a group always covers its current proxies. Hand-picked proxies are tested even when inactive, like testing a single row by hand. Results land on the Proxies page as usual: status, latency, exit IP and country.

Telling yourself what happened #

Send notification #

Posts a message to your dashboard notifications with a title, a body and a style (info, success, warning, danger).

Send webhook #

Sends a message to Discord, Telegram or your own endpoint. Pick a Saved integration from the Notifications page, or configure the destination inline on the step.

The message supports {{workflow}}, {{node}}, {{count}} and {{date}} tokens.

Notes #

Note is a sticky note on the canvas in one of five colours. It never runs. Use it to label sections of a larger flow so the intent survives the next time anyone opens it.