Skip to main content

Using Actions Library

Using Actions library for Reverse ETL​

The Actions Library is a feature designed to facilitate Reverse ETL (Extract, Transform, Load in reverse), allowing users to push data directly from a data workbook to external connectors such as Salesforce or HubSpot. This capability lets users operationalize their data by taking action on insights derived within the platform.

What is the Actions Library?​

The Actions Library is the central repository and management interface for defining and configuring actions that push data out of the system.

The primary purpose of the Actions Library is to enable Reverse ETL. That is, to move cleaned, transformed, or derived data from the workbook (the data warehouse/source) back into operational systems (the connectors, like CRM or marketing tools) using an Action.

  • An Action defines a configuration for connecting to an external service (a connector) and specifying how the data should be mapped and transmitted.

  • Actions are managed under Workbooks $\to$Settings $\to$ Actions Library.

After running an action, the system tracks the action name, the rows that were pushed, and the overall status (successful or not).

How to create an Action?​

An action needs to be created once to define the connection parameters for a specific connector.

  1. Navigate to the Actions Library. In a Workbook, select Settings $\to$ Actions Library. The Actions Library dialog box is displayed.

  2. Click Create New Action.

  3. Provide the following basic information:

    • Action Name: Provide a descriptive name for the action. This name will be used to identify the action in the system.
    • Action Type: Select the action type.
    • HTTP Method: Specify the HTTP method (e.g., POST, PUT, etc.) required by the connector's API.
    • Endpoint: Define the specific URL/endpoint of the external connector where the payload should be sent.

  4. Define the Connector Configuration:

    • Select Connector: Choose a connector where you want to perform the reverse ETL. Click New Credential to enter any additional configuration required for the chosen connector.

  5. Define Column Mapping:

    • Provide a JSON structure that maps the column names from your workbook to the required column/field names of the connector.

    • Note: The structure of this mapping is specific to the external connector. Sample instructions are provided to help with this definition.

  6. Click Create Action

Once created, the action will appear in the list within the Actions Library and be available for use in your workbook. You can edit or delete existing actions from this library.

How to run an Action to execute reverse ETL?​

Running an action executes the Reverse ETL process, which pushes the selected data to the external connector.

Step 1: Select data rows​

  1. Navigate to the relevant workbook containing the data you want to push.

  2. Select the rows in the workbook that you want to send to the connector.

Step 2: Initiate the Action​

  1. In the workbook, click Actions tab and select the specific action you wish to run (e.g., "Push to Salesforce Leads"). The Actions tab is highlighted if there are new actions created.

Step 3: Confirm and Run​

  1. A pop-up will appear, displaying the rows you have selected.

  2. Click Run this action to initiate the push.

Step 4: Check the Tracker​

  • The action is run asynchronously.

  • You can check the action tracker to monitor the status of the run (successful, failed, etc.).

    [Note]

    The same action configuration can be run multiple times by selecting different sets of rows.

⚠️ Known Limitations​

The following limitations are currently associated with the Actions Library functionality:

  • User Permissions: Users must have the appropriate permission level (e.g., Editor or Creator) to run or create an action. Viewers cannot perform these tasks.

  • Connector Access:

    • When a workspace is shared with a company member who lacks access to the configured connector, they may be unable to run the action.

    • The same issue may occur when sharing the workspace with a member outside the company.

  • No Test API: A Test API feature to check the connection between the system and the connector is currently not included.

  • Path Parameters: Path parameters are currently not supported when defining the API endpoint configuration for an action.

Was this helpful?