Integration Configuration

Configure event-driven integration triggers without confusing trigger setup, Workflow testing and published live execution.

Many external-system integrations can start a Workflow when an event occurs. These integration triggers are the foreground-to-background boundary: an event arrives from another system and Lleverage runs the defined Workflow path without a person manually starting it.

Exact triggers differ by provider. The common lifecycle is the same.

Configure the trigger

1. Add the provider trigger to the Workflow.

2. Select or create the required Connection.

3. Configure the resource or event the trigger should listen for.

4. Build the rest of the Workflow around the data the trigger supplies.

5. Test the Workflow with safe inputs.

6. Publish the production version and activate the trigger when it is ready for live traffic.

Connection setup and trigger setup are separate. A valid Connection gives Lleverage authority to use the external system; the trigger determines which event starts this Workflow.

Testing is still real execution

A Workflow test is a real Workflow execution. Actions reached during the test can call external systems and create real side effects.

Some trigger editors may provide sample or test input to help exercise downstream logic, but that does not turn the rest of the Workflow into a sandbox. Use test accounts, safe records or non-destructive actions where the production system matters.

See Tests for the current testing model.

Publishing makes trigger configuration operational

Draft editing and testing do not automatically replace the live Workflow. Live traffic uses the current Published version together with its active/default state.

Publishing can create or update the trigger infrastructure needed for the live Workflow. Treat a publish that changes an external trigger as an operational change, not merely a documentation step.

See Publishing workflows.

Diagnose trigger problems in layers

If an expected event does not produce a run, check:

• whether the external Connection is still authorised;

• whether the correct resource or event is configured;

• whether the intended Workflow version is Published and active;

• whether any provider-side subscription, permission or webhook prerequisite is still valid;

• Monitoring for evidence that a run started and then failed.

If no run exists in Monitoring, investigate the trigger and external-provider boundary first. If a run exists, diagnose the execution trace instead.