Configuring and Testing Actions

Actions define what your workflow does after a trigger occurs. Configuring them properly ensures they perform the correct tasks in connected apps. Testing helps validate that the configuration works as expected before deploying your automation.

Configuring an Action

Once you’ve selected the app and added the action to your workflow, you can begin configuring it. This involves setting up inputs and connecting the required account.

1. Connect an Account

  • Select the app action in your Keragon editor.

  • Go to the "Auth" tab.

  • Click "+ Connect new account" and provide the required authentication details.

  • Alternatively, select from existing accounts displayed under the "Auth" tab.

2. Configuring Inputs

Understanding the Different Field Types

When configuring the inputs of a trigger or an action in Keragon, you will notice different field types that can accept data:

  • Single Input: This is the most common and simplest input type. It appears as a small box and can accept both strings and numbers.
    Screenshot 2024-06-13 at 6.01.20 PM.png

  • Drop Down: This input type displays a dropdown menu with a list of options to choose from. These options are predefined and provided by the third-party app associated with the action or trigger.
    mceclip0.png

  • List of Items (Array): This type of input accepts a list or collection of similar elements, such as names, numbers, or emails.
    Screenshot 2024-06-14 at 10.00.12 AM.png

  • Nested Inputs (Object): This input type is used for grouped information where each piece of data has a name and value. For example, an object could represent a person with properties like name, age, and address.
    Screenshot 2024-06-14 at 9.59.15 AM.png

When configuring an action’s inputs, you can use static data or dynamic data.

Static Data

Static data is unchanging information. You can input static data by typing directly into a text field or by selecting a value from a dropdown menu. Using static data ensures that each time the workflow runs, the action will transmit the same information to the app.

  • Enter constant values directly into input fields.

  • Example: Set the status field to "New" so that every created record has the same status.

staticmapping.gif

Dynamic Data (Data Mapping)

Dynamic data introduces variability into the action's inputs. This data is derived from variables linked to previous steps in the workflow. Each time the workflow runs, the specific data from a prior step may be different based on new input or changes that occurred up to that point.

  • Dynamic data comes from previous steps in the workflow.

  • This is achieved using the Variable Selector.

Using the Variable Selector:
  • Click on the input field you want to configure.

  • The variable selector window will appear, allowing you to select data from previous steps.

  • The selector includes:

    • Values from Previous Steps: Data outputs from earlier workflow steps.

    • Authentications: Data related to authentication tokens and connection details.

  • Select the variable to map dynamic data into the input.

Example: Map the patient’s name from a form submission trigger directly into the "Create Patient" action.

dynamicdata.gif

Understanding the Variable Selector

The Variable Selector makes it easy to pass data between steps in your workflow.

Key Features:

  • Automatically appears when clicking into an action’s input field.

  • Allows selecting data from previous steps without writing any code.

  • Displays available data types: String, Number, Boolean, Array, Object, and Null.

Types of Variables:

When you click on an action's input field in Keragon, the variable selector window appears. Depending on the type of input, the selector contains two or three categories of variables:

Values 

This appears only for dropdown inputs. It includes predefined options that the input expects.
Frame 9.png

Steps

Data from earlier steps in the workflow.
Frame 10.png

  • Each variable here shows:
    • The variable’s key name

    • The variable’s type. Learn more about supported data types here.

    • The variable’s actual value.
      Variable data.png

      Cannot select data?

      In some cases, variables may not be selectable. If you hover over them, you'll see the reason why. Most often, this happens because the data you're trying to select doesn't match the expected input type. For example, you might be trying to assign a number to an input that only accepts text. In such cases, you should first transform the data using a helper action, and then use the transformed data in the input.
      image 22.png

      You can learn more about data transformations in our dedicated section here.

      Cannot see data?

      If you don’t see any available data to select, it’s likely because the previous steps haven’t been tested yet. Please run a test on the prior steps to generate data. Once tested, the data will become available for selection in your workflow.

Authentications

Credentials and tokens from connected accounts.

Testing an Action

After configuring inputs, it's important to test the action to ensure it behaves correctly.

How to Test an Action:

  • Click the "Test Step" button in the Properties Panel.

  • Keragon will execute the action with the provided inputs.

Reviewing Test Results:

  • Status: Indicates if the action was successful or failed.

  • Error Message: Displays specific errors if the action failed.

  • Inputs: Shows the data that was sent to the app.

  • Outputs: Displays the response from the app, which can be used in subsequent workflow steps.

Screenshot 2023-11-10 at 10.13.09 AM.png

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section