Triggers — when an automation runs

The trigger is the starting line

Every automation begins with exactly one trigger. Click the trigger node in the builder to open its config panel and choose a trigger kind.

On event

The most common kind. The automation fires whenever a matching event flows through your project — for example a feature request being created, a status incident opening, or a release being published.

Pick the exact event type from the list. Events are grouped by area, and you can type in the search box to filter the list quickly. Each event carries data (a title, an entity ID, and metadata) that your steps can reference — see Using dynamic values.

On a schedule

Runs the automation on a recurring clock instead of in response to an event. You provide a cron expression (5 fields, minute granularity) — for example 0 9 * * 1 runs every Monday at 09:00. Scheduled runs see a synthetic event so your steps still have a consistent shape to work with.

Manual

The automation never fires on its own and no events match it. Instead it runs only when you start it by hand. Use this for one-off jobs and for flows you want full control over.

Webhook

The automation runs when an external system calls a dedicated inbound URL. AppGram gives each webhook-triggered automation its own URL and token; the payload that is POSTed becomes the event data the steps can read.

The optional condition

Below the trigger you can set a condition — a single expression that must evaluate to true for the run to continue. For example:

event.metadata.priority == "high"

Leave the condition blank to match every event. The condition is checked right after the trigger, before any step runs. To make decisions part-way through a flow, use a branching step instead (see Branching & flow control).

Next

Continue with Steps — what an automation does.