Workflows

#Overview

A workflow connects something that happens in your server to the things greed should do about it. You build it on a canvas: a trigger on the left, steps to the right, wires between them.

Crucially, a workflow does not replace your existing setup. It runs the features you have already configured — your welcome message, your autoroles, your logs — so there is one place to edit each of them and no chance of two systems fighting over the same job.

#The four kinds of step

#A worked example

The problem: you want a welcome message, but not for brand new accounts that are probably throwaways.

Without workflows you would have to turn Welcome off entirely. With one:

Your Welcome configuration stays exactly as it is. The workflow only decides when it applies.

#Variables

Steps that render a message reuse the feature they belong to, so they carry that feature's own variables — a welcome step renders your Welcome message with the same {user.mention}, {guild.name} and friends you already use there. There is no second vocabulary to learn.

On top of those, a message rendered by a workflow gets a small {workflow.*} set describing the run itself:

{workflow.trigger} {workflow.invite.code} {workflow.invite.url} {workflow.inviter.mention} {workflow.inviter.id} {workflow.account_age_days}

Anything that does not apply to the current run renders as an empty string rather than leaving the raw name in your message.

#Times and timezones

Any step that involves a clock — time of day and on a schedule — carries its own timezone picker, defaulting to UTC.

greed stores the moment in UTC and converts for display and evaluation, so daylight saving is handled for you: a workflow set to run at 09:00 in Europe/London runs at 09:00 local in both winter and summer, without you touching it twice a year.

#Limits

#Saving

Workflows are built on the website only — a graph is not something a chat command can express, so there is no ,workflow equivalent.

The name sits at the top of the builder; click it to rename. Changes to the canvas, the name and the enabled toggle are all held until you press Save changes, which turns to Saved once there is nothing outstanding. Leaving without saving discards the edits, and a new workflow always starts disabled so a half-built one cannot fire.

#When a step breaks

Servers change. A channel gets deleted, a role gets moved above greed, permissions get revoked — and a workflow that keeps trying would fill your audit log with failures.

Instead, greed checks every reference before it runs a step. If the thing a step points at is gone or unusable, that workflow is switched off and the reason is recorded, rather than retrying forever. Fix the reference and switch it back on.