Send Volai call results to Google Sheets
Import the n8n template and write a sample call to Google Sheets. Connect your Volai account to log future completed calls automatically.
1Import the workflow into n8n
Save the JSON file linked above. Open the workflow menu in n8n and select Import from File. The template uses built-in nodes and was tested with n8n 2.48.5.
2Prepare the spreadsheet
Create a blank Google Sheets tab called Call results. Copy the header below and paste it into A1. Each value goes in a separate column on the first row.
Call ID Event time (UTC) Direction Status Duration (s) Mode3Write a sample row
In Write call result to Google Sheets, select your Google Sheets OAuth2 credential. Set Document to By ID and paste the part of your spreadsheet URL between /d/ and /edit. Keep Sheet set to Call results. To try it without a Volai account, disable Confirm successful write. Execute the workflow from Test with a sample call. Look for DEMO-call-result-001 with sample in the Mode column. A repeat run updates that row.
4Connect your Volai account
Create your Volai account and generate a key in API settings. In n8n, create a Header Auth credential. Enter Authorization in Name and Bearer <API key> in Value, replacing <API key> with your key. Give the credential any display name. Select it in Read Volai call event and, if you want to report successful writes, in Confirm successful write. To report your sample write, enable that node and run the sample again.
5Subscribe to completed calls
In Volai call completed, copy the public HTTPS Production URL. If that webhook path is already in use, change it before copying. Replace the example address in the command below with your URL and run it in Bash or Zsh. Enter your API key at the prompt, keep the response private, and copy its deliveryToken.
(
printf 'Volai API key> '
IFS= read -rs VOLAI_API_KEY
printf '\n'
printf 'Authorization: Bearer %s\n' "$VOLAI_API_KEY" |
curl --fail-with-body --silent --show-error \
--header @- \
--header 'Content-Type: application/json' \
--data '{"url":"https://your-n8n.example/webhook/volai-call-result-to-sheets","events":["call.completed"]}' \
https://volai.cz/v1/webhook-subscriptions
)6Publish the workflow
Create a second Header Auth credential. Enter X-Volai-Webhook-Token in Name and paste the deliveryToken from the API response into Value. Select it in Volai call completed and publish the workflow. After your next completed call, look for a live row. Before writing, the workflow checks the token and reads the event from Volai.
What you can do with it
Daily call reporting
Count completed calls by day using the UTC event time.
Team workload
Use a pivot table to compare the volume and duration of incoming and outgoing calls.
Check the automation
Match rows in the sheet with your Volai call history by call ID.
Frequently asked questions
- What goes into the sheet?
- Each row contains the call ID, event time in UTC, direction, status, duration in seconds, and
sampleorlivemode. Phone numbers, transcripts, and recordings are left out. - What does the workflow measure?
- After a successful write, Confirm successful write can send Volai a confirmation. For accounts created from this guide with measurement consent, Volai counts the first confirmed sample run and first confirmed live run separately within seven days of registration. The confirmation excludes spreadsheet cells. For live runs, Volai uses the subscription and event IDs to check ownership and status. Disable the node in n8n to turn this off.
- Can the same call appear twice?
- Sequential repeats update the row with the same
Call ID. Use one workflow per sheet. Google Sheets cannot guarantee that simultaneous writes of the same ID produce a single row. - What should I check if the row is missing?
- Look for sample run errors in the n8n editor. For a live failure, temporarily turn on Save failed production executions in workflow settings, reproduce the issue, and find the failed step in execution history. Turn saving off afterward. For a failed write, check Google access, document ID, sheet name, and exact headers. For webhook errors, check that the workflow is published and uses the right public URL and delivery token.