testing a flow.md

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Testing a Flow

There are a couple of ways to test your workflow.

Manual Run

You can manually trigger your workflow by using the Run button at the bottom left hand side of the Workflow Builder.

The Run history tab will display previous test and live runs of the workflow.

Live Execution

The Live button on the Run history will display all live executions of the workflow.

The recommended method for testing is to use a live execution. If your workflow is triggered off a certain event in ION, open up ION in a separate tab and initiate the event. For example, if you have a flow that is triggered when a purchase order is created, then every time you create a purchase order you will see an execution of the flow in the Workflow Builder.

You can click through each step to display the output and logs.

Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the ask query parameter, and the optional goal query parameter:

GET https://manual.firstresonance.io/workflow-builder/testing-a-flow.md?ask=<question>&goal=<endgoal>

ask is the immediate question: it should be specific, self-contained, and written in natural language. goal is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.