Triggering Workflows

Define how your Looply Workflows are initiated with event triggers

Every workflow within Looply is required to have a defined event trigger as the first step to determine how the process will be initiated. Here are some triggers we currently support:

• HTTP Request - triggers your workflow when an HTTP request is received from your system or client

• Scheduled - triggers your workflow on a preset schedule defined by you

Request

Request event triggers can be used when you want to be able to trigger an execution of your workflow by sending an HTTP Request to the Looply API. These event triggers also support attaching a body payload to your request which will be passed into your workflow at runtime.

Configure Payload

Workflows set up to use an HTTP Request as the trigger also supports the configuration of a mock payload during workflow development.

Mock payloads work by allowing the developer to send a POST request to a unique Looply API with data in the body that will resemble real-world data your workflow is expected to receive during runtime. This mock data is then stored against your workflow and can be accessed by steps within your workflow or will be attached during test executions.

Send Request

You can find the unique Looply API endpoint for receiving data for your workflow by clicking on your event trigger step and opening it in the side panel.

You will find your unique endpoint under the Request URL field and can copy this to clipboard with the Copy button.

Now all you need to do is use a REST client of your choice to send a POST request to this endpoint and setup your mock data in the body.

Detecting Payload

Once you have sent at least 1 test request to your unique endpoint, you can sync the data to your workflow by clicking on the Detect Payload button.

Your mock payload will be displayed within this side panel for you to confirm.

Scheduled

Scheduled workflows can be used when you want setup your workflow to repeat on a specific defined interval. As these workflows would be run automatically on a schedule, it is not possible to support a dynamic payload at runtime.

Looply supports configuring workflow schedules with the following options:

• Minutes

• Hourly

• Daily

• Weekly

Scheduled workflows will automatically begin when you successfully activate your workflow.

Pause/Resume Schedules

Once activated, scheduled workflows can be paused at any given time by visiting the Workflow Builder, selecting the Event Trigger step, and then clicking the Pause button.

Paused workflows can be resumed at any time by repeating the same process as above and clicking the Resume button.

Note: You can only have one version of your scheduled workflow active at any given time. If you create a new version of your scheduled workflow and activate it - the previous version schedule will be canceled.