How to test a step in your workflow

Once you have configured your step's inputs, you can test it to ensure it functions as expected. Testing a step prompts Keragon to make an API request to the application, which then uses the response data to populate the variable selector, making it available for subsequent steps.

Testing a trigger

Option 1: Testing a trigger using sample events

In most triggers after you have configure them you have the option to test them with sample event.

Follow the steps below to test a trigger with sample data.

1. Select the trigger in your keragon editor
2. Go to "Inputs" tab
3. Click "Test with sample event" button
4. In the drop down select a past event
5. Click "Test trigger" button
6. View your test result and the data from the trigger under the "Outputs" tab

If you do not see any sample events in the dropdown, it means that there are no recent events (e.g., form submissions) in your triggering app. Try creating an event in your app, and then click the 'Test with sample event' button again.

Option 2: Testing a trigger using live events

Another way to test your trigger is by sending a live event while your workflow is published. Follow the steps below to test a trigger with a live event.

Note that some triggers, like the HTTP Webhook and certain app triggers, do not offer the functionality to test with sample events. In these cases, testing with a live event is the only option.

1. Ensure that your workflow is published and contains only the trigger without any subsequent actions.
2. Navigate to the vendor application where you've configured your trigger. This application is where you will initiate the data flow.
3. Within the interface of your vendor application, perform the specific task that triggers your workflow. This task could be submitting a form, creating a CRM record, adding a new row, and more.
4. Return to your Keragon editor and in the top right corner your should see a checkmark if the test was successful. 

Testing an action

After configuring the inputs of the action, it's important to test the step to ensure it operates as expected.

1. Click the "Test step" button
2. You will then see the results of this test, which include:
   1. Status: Indicates whether it was completed successfully or failed.
   2. Error message: If an error occurred, this will show the specific error.
   3. Inputs: The data that was used by this action to perform its task.
   4. Outputs: The data returned from the 3rd party app, which can also be used in next steps.