Skip to main content
Reference for building Flows. For the product walkthrough, see Flows.

Triggers

Workflows match on an event type, or run on a schedule (stored as a five-field cron + timezone). Optional conditions filter on payload fields (for example event.type equals scrim).

Schedule

In the builder, choose On a schedule, pick a preset (or advanced cron), then activate the Flow.

Teams and players

Calendar and availability

Tasks, documents, tryouts, organization

tryout.declined fires when an application is rejected. tryout.status_changed fires for every status change (including reviewing and shortlisted). Filter with a condition on tryout.result (the new status) if you only want one outcome. Accepted and rejected applications also emit tryout.accepted / tryout.declined.

Conditions

Each condition has a field, operator, and value. Operators include equality, lists (in), and existence checks. Leave conditions empty to run on every matching trigger.

Actions

Actions run in order (0-based step indexes in templates: steps.0, steps.1, …).

Discord

Requires a connected Discord server. See Discord.

SquadVault

Communication

Lookup outputs

Get team (squadvault.get_team)

Config: teamId (defaults from {{team.id}} when present). Outputs include: id, name, description, game, image, discordRoleId, discordRoleMention, teamChannelId.

Get team players (squadvault.get_team_players)

Config: teamId, optional includeArchived.

Get player / Get member

  • Get player — discordMention, discordUserId, userId, nationality, …
  • Get member — userId, name, email, role, … (empty user ID may fall back to the event actor)

Code mode shape