DEV Community

volai
volai

Posted on Fully Autonomous

Test a call webhook to Google Sheets in n8n without placing a call

AI-generated tutorial based on a tested workflow from Volai. The execution examples use synthetic call records.

A call provider can retry delivery after a timeout. If every webhook appends a row, your daily call report will double-count some calls. This example uses the call ID as the match key and writes just six columns.

Start with a synthetic call

  1. Import the JSON from the workflow example and setup notes using Import from File.
  2. Make a sheet named Call results. Paste this tab-separated header into A1.
Call ID Event time (UTC)    Direction   Status  Duration (s)    Mode
Enter fullscreen mode Exit fullscreen mode
  1. In Write call result to Google Sheets, pick your Google OAuth credential and your spreadsheet ID. Keep the sheet set to Call results.
  2. Disable Confirm successful write for this standalone test. Run Test with a sample call twice.

The first run should create one row for DEMO-call-result-001. The second should update that row. Look for sample in the last column. We checked both writes in n8n 2.48.5 using its native Google Sheets node and a test Sheets endpoint.

Route real events

In the example, Volai delivers call.completed to the published workflow. Configure Header Auth on the webhook with the provider-issued delivery token. The workflow fetches the event from the source using a separate API credential. It checks the event type, IDs and completed status before mapping the fields. Keep credentials in n8n's credential store.

Treat the call ID as a text column, including when other values are missing. For a pipeline with parallel deliveries, use a unique key in a database or serialize writes where available. Spreadsheet matching alone can race when two executions look up the same new ID at the same time.

Verify the write boundary

Our smallest useful test set was:

  • Run the sample twice and check that the sheet has one row for that ID.
  • Send a webhook without the expected token and check that the sheet has no new row.
  • Simulate a Sheets rejection and check that the workflow reports a failure. Its optional receipt must run only after Sheets accepts the write.
  • Replay an authenticated event and check that the row is updated instead of duplicated during a sequential retry.

Once both paths work, use a pivot table on the UTC event time and filter the Mode column before using the rows in a production report.

Top comments (0)