Pabbly

You can submit data for analysis in Conduit using Pabbly.

In this example, we will create a workflow that sends new rows created in a Google Sheet to a virtual table in Conduit. (Instead of Google Sheets, you can use any application integrated with Pabbly.)

Spreadsheet

1. First, create a spreadsheet with two columns: Name and Cost.
   

2. Next, connect the Pabbly Addon to the spreadsheet (for detailed instructions, refer to the Pabbly documentation).

Conduit

Let's add a new WebHook to Conduit and name it "Test Pabbly."

In this integration, we will create two columns: Name and Cost. Copy the URL from Conduit.

Pabbly

3. Create a new workflow with a trigger in Pabbly called “Google Sheets” and connect it to the spreadsheet.
   
4. In Pabbly, create a new action called “API (Pabbly)” and specify the event as “Execute API request.”

4.1. For the action event method, choose POST.
4.2. Set the API endpoint URL (which you can copy from Conduit).
4.3. Select the payload type as JSON
4.4 Set the necessary parameters.

5. Click “Save and Send Test Request” to ensure everything is set up correctly.

Open the event log for the Webhook in Conduit by clicking the "View Logs" button.

If you encounter an error message stating "Error: No valid columns found," it indicates an issue with the column configuration. Ensure that all necessary columns, such as Name and Cost in this example, are created in the action.

Update vs Append

By default, Conduit's Webhook operates in Append mode, meaning any edit to a row triggers the Workflow and sends the updated row to Conduit, resulting in multiple versions of the same row.

If you want Conduit to maintain a copy of the data from the spreadsheet (same number of rows), switch to Update mode. In this mode, modified rows will overwrite older versions of rows in Conduit.

Add the "?mode=update" parameter to the URL and select the column that identify a unique row.