Running your Workflow

There are multiple ways to run your Workflow:

Call the API for this Workflow

This is the most common way to run your Workflow. See Execute API for more details.

This is how your Workflow will be run from within your fintech products & services, so it's important to test it out thoroughly to make sure you're passing in the right data.

Run Workflow from the Test Modal

From inside the Workflow Editor page, click the Test button in the top right corner. Select Individual Test.

You can edit the fields in the left hand JSON block, to control the Input you'll be running through the Workflow.

If you'd like your Workflow to call live data sources (rather than using cached data) and actually save a record to the execution History, you'll need to click on Advanced Options, and turn off Dry Run mode.

When you click Test, you'll see a table of Rules appear in the Results section. You can over any Rule Execution record to see more details.

All Custom Variables will appear in the Variables tab. You can click into them to see exactly what Rules affected their value.

Finally, all Data pulled in from your Data Connectors will appear in the Data tab.

Use the Batch Runner

The Runner is a great way to test many different potential inputs, rather than testing them one at a time. You can open the Runner page from the Sidebar. You'll see a table of Runner jobs, and the Create Job button in the top right.

Click the button, select your Workflow and Version, and Upload a CSV with the inputs you'd like to use. Your CSV's column names should match the expected input fields for your Workflow

Once the Batch Runner kicks off a job, you'll see it listing as Pending or Running in the table. When the Status changes to Done, you'll see a download link to download your results spreadsheet.

Note: the Batch Runner is designed to run in the background, so jobs won't affect the performance of your live workflows. This means they won't run as quickly as the production versions of your workflows, and shouldn't be used for high speed situations or testing.

Did this page help you?