Quickstart: save a webhook to Google Sheets

Build a Workflow that receives a JSON webhook and adds one row to a Google spreadsheet. Capture test data, map it into an Action, then activate the Workflow and check a real run.

Text
Webhook Trigger → Google Sheets: Append Values

Before you begin

You need a FastHook account, a Google account with permission to edit a spreadsheet, and a terminal. Request examples are provided for a POSIX shell and Windows PowerShell.

Create a test spreadsheet with a worksheet named Orders. Put these headers in its first row:

ABCD
Event IDCustomerAmountCurrency

1. Create a Draft

  1. Open Workflows and select Create workflow.
  2. If Build with AI opens, close that panel to follow this manual walkthrough.
  3. Select New Workflow, or open the three-dot More Workflow actions menu and choose New Workflow.
  4. Name it Webhook orders to Google Sheets and select Create Workflow.

The new Workflow is a Draft. Close Build with AI if it opens after creation, then add the Trigger on the canvas. You do not need to create a separate Connection or Destination.

2. Capture a webhook sample

  1. Select Add Trigger on the canvas and choose Webhook.
  2. Follow Setup → Configure. Give the webhook a recognizable name and keep authentication off for this fictional test.
  3. Save the configuration with Continue and copy the Source URL from Configure.
  4. Open Test and select Test step to listen for a request.
  5. Replace PASTE_SOURCE_URL_HERE with the complete copied URL and run:
Shell
curl --request POST 'PASTE_SOURCE_URL_HERE' \
  --header 'Content-Type: application/json' \
  --data '{"id":"evt_quickstart_preview","customer":{"name":"Ada"},"amount":149,"currency":"USD"}'

In Windows PowerShell, send the same request with:

POWERSHELL
Invoke-RestMethod -Method Post -Uri 'PASTE_SOURCE_URL_HERE' -ContentType 'application/json' -Body '{"id":"evt_quickstart_preview","customer":{"name":"Ada"},"amount":149,"currency":"USD"}'

Select the received record in the Trigger test panel and choose Continue. Confirm that its JSON body contains the event ID, customer name, amount, and currency. Use this captured record when configuring the next Step.

The Workflow is still a Draft. Receiving this sample does not start normal Workflow execution. Before using the endpoint for real data, configure the sender's authentication in the webhook verification guide.

3. Add the Google Sheets Action

Select Add step after the Trigger and choose Google Sheets.

In Setup, choose Append Values as the Action event. Connect or select your Google account, then choose Continue.

In Configure, select your test Spreadsheet and the Orders Worksheet. Set Range (A1 notation) to A:D and Value input option to RAW.

Use the Rows JSON editor to create one row with four columns. For each cell, choose From flow and pick the corresponding value from the captured Trigger body:

ColumnSelect from the Trigger samplePreview value
Aidevt_quickstart_preview
Bcustomer.nameAda
Camount149
DcurrencyUSD

Use Add column if the editor shows fewer than four cells. The picker inserts references to the event fields; typing the preview value as fixed text would write that same value for every future event. Select fields from the actual preview rather than guessing their full paths.

4. Test the Action

Choose Continue to open Test, then select Test step. This calls Google Sheets and writes a real row even while the Workflow is a Draft.

Open the spreadsheet and confirm the row contains:

Text
evt_quickstart_preview | Ada | 149 | USD

If the test fails, check the selected Google account, spreadsheet permissions, worksheet, range, and required mappings. Retest step calls Google Sheets again and can append another row.

5. Activate and send a new event

When the test result and saved settings are correct, choose Publish if it is offered at the end of the Step editor. You can also close the panel and select Activate in the Workflow toolbar. Confirm that the Workflow status is Active.

Send the same request once more, changing its ID to evt_quickstart_live. Activation does not replay the earlier sample: this new request is the event that starts the live run.

6. Verify the run

Open More Workflow actions → Run history, or select Last run above the canvas. Open the run for the new webhook and check:

You have now checked both the Action test and a complete Trigger-started Workflow run. Select Pause when you are finished with this test automation.

Continue building

Read Core concepts for the product model, Workflows for the editor and lifecycle, and Data mapping for using earlier Step outputs. To start from a ready-made pattern, see Templates and duplication.