Triggers

Triggers are server-side rules that watch one or more accounts and run an action when a condition is met. Use them to stop bots when they hit a level target, swap accounts between groups when wealth crosses a threshold, alert you on bans, schedule batch launches, or kick off OAuth re-capture when sessions expire.

How they work

• Triggers are evaluated server-side, not on the agent. You can leave your machine and they still fire.
• Metadata triggers (level, skill, wealth, runtime, etc.) are checked on a polling loop — Pitchfork batches up to 100 accounts at a time every few minutes against accounts whose metadata recently changed.
• Event triggers (account banned, connection failed, status changed) fire as soon as the underlying event is recorded.
• Schedule triggers (scheduled, one_time) fire from a separate polling service that respects timezones and cron expressions.
• Every trigger has one or more actions. Multiple actions on a single trigger run in order; if one fails, the others still execute.

Trigger catalog

Account state

Membership

Group composition

Schedule

Advanced conditions

Any trigger can use multiple_conditions to combine multiple field checks with AND/OR logic instead of a single threshold. Each condition has a field (e.g. total_wealth, combat_level, quest_points), an operator (>, <, >=, <=, ==, !=), and a value.

Action catalog

Worked example: stop and rotate when an account hits 99 Slayer

Create a skill_level_reached trigger with conditions skill: "Slayer", level: 99 and these actions, in order:

1. notify — message: "{{account.name}} hit 99 Slayer 🎉", level: "info"
2. stop_bot
3. move_to_group — group_id: <maxed_accounts_group_id>

Pitchfork picks up the metadata change within a few minutes of your script reporting it, fires all three actions, and your account ends up parked in the maxed-accounts group with a notification in your tray.

Worked example: keep a group running 24/7

Use a group_continuous_launch trigger on the group. Set:

• cooldown_minutes: 30 — don't relaunch the same account inside 30 min of stopping
• exclude_banned: true
• require_member: true
• max_runtime_today: 360 — don't relaunch an account that's already botted 6 hours today

Action: start_script with the script and agent you want.

REST API

Triggers can be created and managed via the Public API under the /api/triggers resource. The shape mirrors the UI form: name, trigger_type, conditions, actions[], optional account_ids[] or account_groups[] to scope.

Caveats

• Polling latency. Metadata triggers can take up to a few minutes to fire after the underlying value changes. If you need real-time, use an event trigger or a webhook from your script.
• No cross-account conditions. A trigger evaluates one account at a time (group triggers being the exception). You can't write "fire when accounts A and B are both running" — use webhooks + your own logic for that.
• Action ordering matters when one mutates state another reads. Put stop_bot before move_to_group if your downstream logic cares about which group an account was in when it stopped.