Create and manage triggers

Triggers turn events from connected tools into workflow work. A trigger rule says which event to match, which department should receive it, and which available workflow should run.

Nothing is queued until triggers are switched on. Winglo still lists received events when triggers are off so you can confirm what a connector is reporting before automation begins.

Open Triggers#

Open Connectors, then choose Triggers. The page contains workspace trigger settings, your rules, a form for adding a rule, and recent events.

Only departments and workflows currently offered by the form can be selected. If no workflow is available for a department, a trigger cannot route work there.

Build a rule#

Provide:

• Name: a short description of the business outcome
• Tool: one connected source or any connected tool
• Event: an event name or supported pattern; leave it blank to avoid filtering by event type
• Department: the department that owns the work
• Runs: the available workflow to queue
• Priority: the relative urgency of the queued work
• Most an hour: the maximum number of times this rule may fire in one hour

Start narrowly. Choose one known tool and event, select the workflow that should own the response, and use a conservative hourly limit. A broad pattern can match more events than expected.

Turn triggers on safely#

Create and review the rule first. Then switch Triggers are on when you are ready for matching events to queue work.

The workspace-wide hourly maximum limits all trigger activity together. Each rule also has its own hourly maximum. These controls reduce unexpected volume but do not replace careful event matching.

Winglo can pause triggers automatically when a safety limit is reached. Read the displayed reason, investigate the source and rules, then resume only after correcting the cause.

Read rule activity#

Each rule shows whether it is on, its match scope, destination workflow, priority, hourly limit, and how often it has fired. Turn a rule off to stop future matches without deleting its configuration. Delete it only when you no longer need the rule.

Turning off a rule does not cancel workflow work already queued.

Understand recent events#

Recent events appear whether or not they matched a rule. Common outcomes include:

An event may arrive directly from a provider or be found during a periodic check. Open the event details and dispatch message to understand why it did or did not create work.

Test without creating duplicate work#

Use a low-impact provider event and keep limits small during the first test. Confirm that exactly one event appears, one rule matches, and the intended workflow is queued. If the provider outcome is unclear, inspect both Winglo and the provider before sending another test.

Use Monitor and repair workflow runs after a trigger queues work.