Seconds after each call is analysed, a native post-call workflow adds a Google Sheet row with the time, number, outcome, summary, recording link and your extracted fields, such as budget or callback time. It costs nothing beyond the call minutes. Each call adds a new row; it doesn't merge rows for the same number.
Works with: Google Sheets Native (post-call workflow step Google Sheets Append) · Edesy Tables via API (the same workflow's Webhook step calling the Tables API) · any other destination via webhooks in Zapier, n8n or Make (call.analyzed)
How it works#
Call ends ──> post-call extraction ──> trigger "Data Extracted" (agent filter)
│
┌─────────────────┴──────────────────┐
▼ ▼
Google Sheets Append Webhook step (POST)
columns from {{disposition}}, {{callSummary}}, https://tables.edesy.in/api/v1/
{{budget_range}} ... tables/<id>/records
Before you start#
- A voice agent with a post-call extraction template (Agent → Behavior → Post-Call Extraction), so there are fields to write.
- A Google account with edit access to the sheet, or an Edesy Tables table and an API key (
tbl_..., created in Tables Settings). - Owner or admin rights in the voice agent workspace.
Set it up: Google Sheets#
- Create the sheet and type the headers in row 1, for example:
Time | Name | Phone | Outcome | Summary | Budget | Callback time | Recording | Call ID. - In the voice agent, open Settings → Integrations → Google Sheets and click Connect Google Sheets. Approve access. To use another Google login, click Add another Google account.
- Open your agent, go to the Integrations tab, then Post-Call Workflows, and click Add Workflow (or start from Workflows in the sidebar).
- Choose the trigger Data Extracted and select this agent. Use Call Ended instead if you don't use extraction; it fires sooner but has no summary or extracted fields.
- Add a step from Integrations: Google Sheets Append. Pick the Google Account, the Spreadsheet and the Sheet Tab.
- Under Column Mappings, map each column to a variable:
| Column | Value |
|---|---|
| Time | {{_timestamp}} (DD/MM/YYYY HH:mm IST) |
| Name | {{recipientName}} |
| Phone | {{recipientPhone}} |
| Outcome | {{disposition}} |
| Summary | {{callSummary}} |
| Budget | {{budget_range}} (your extraction field) |
| Callback time | {{callback_time}} (your extraction field) |
| Recording | {{callRecordingUrl}} |
| Call ID | {{conversationId}} |
- Save as Draft, run a test call, then set the workflow to Active.
To write only some calls, add a Condition step before the append, for example disposition == QUALIFIED, or filter the Call Ended trigger by outcome.
Set it up: Edesy Tables#
- In Edesy Tables, create a table with fields such as Name, Phone, Outcome, Summary, Budget. Open the base's Share dialog, then the API & webhooks tab, to copy the base and table IDs. Create an API key in Tables Settings.
- In the voice agent post-call workflow, add a Webhook step instead of (or after) the sheet step:
Method: POST
URL: https://tables.edesy.in/api/v1/tables/<tableId>/records
Headers: Authorization: Bearer tbl_xxxxxxxx
Content-Type: application/json
Body:
{
"typecast": true,
"records": [{ "fields": {
"Name": "{{recipientName}}",
"Phone": "{{recipientPhone}}",
"Outcome": "{{disposition}}",
"Summary": "{{callSummary}}",
"Budget": "{{budget_range}}"
}}]
}
Field names or field IDs both work; IDs keep working if someone renames a field. typecast: true lets Tables convert text into number, date or select values.
Data map#
| Variable | Available on | Meaning |
|---|---|---|
recipientPhone, recipientName |
Call Ended, Data Extracted | Number called and name, if known |
disposition, callStatus, endReason |
both | Outcome such as QUALIFIED, NO_ANSWER, DO_NOT_CALL |
callDuration, _timestamp |
both | Seconds; time in IST |
callTranscript, callRecordingUrl |
both | Full transcript; signed recording link |
agentName, callSource, campaignName |
both | Which agent; campaign, api, inbound or test |
conversationId |
both | The call ID; the same value is conversation_id in call.analyzed |
callSummary |
Data Extracted | The AI summary |
| Your extraction fields | Data Extracted | Flattened, for example {{budget_range}} |
The same data is in the call.analyzed webhook as recipient_phone, disposition, call_summary, extracted_data, recording_url and variables, for Zapier, n8n or Make.
Sample extraction template#
The prompt doesn't change for this recipe; the extraction template decides what lands in the sheet. In Post-Call Extraction → New Template, for a real estate lead line:
| Field Key | Data Type | AI Description |
|---|---|---|
budget_range |
Single Choice (Enum): under_50L, 50L_1Cr, above_1Cr, unknown |
Budget the caller said, in rupees |
bhk |
Single Choice (Enum): 1, 2, 3, 4_plus |
Flat size wanted |
site_visit_date |
Text | Agreed site visit date as YYYY-MM-DD, empty if none |
callback_time |
Text | When they asked to be called back, in IST |
language_used |
Text | Language the caller mostly spoke (Hindi, English, Marathi...) |
Test it#
- Place a test call to yourself from the agent page, and talk through the questions.
- Wait for extraction to finish (usually under a minute), then check the sheet for a new row.
- If nothing appears, open the workflow's execution history: each run shows the trigger data and the step's status. Fix the cause and click retry.
- To fill the sheet with past calls, use Backfill on the workflow.
Consent and data protection#
- Recording links and transcripts contain personal data. Share the sheet only with people who need it, and don't make it public.
- Keep the
DO_NOT_CALLoutcome in the sheet so nobody re-dials those numbers, and add them to Settings → Blocked Numbers. - Calls themselves follow your agent's calling window and consent rules; see the recipe that starts the call.
What it can't do yet#
- Google Sheets Append always adds a row. To update an existing row for the same lead, use Google Sheets Lookup then Google Sheets Update with a row number field.
- There is no native Edesy Tables step; the Webhook step calls the Tables API.
- Google Sheets has its own write limits; for thousands of calls an hour, use Tables or a database.
FAQ#
Which trigger should I use? Data Extracted if you want the summary and extracted fields; Call Ended if you only need the outcome and want it a little sooner.
Can each agent write to a different sheet? Yes. Create one workflow per agent, or one workflow listening to several agents with a different sheet per workflow.
Does it log calls nobody answered?
Yes. Unanswered calls end with NO_ANSWER, BUSY or FAILED and still trigger Call Ended.
Does it cost extra? No. Workflow steps don't add charges; you pay for the call minutes.
Can I send the same row to my CRM? Yes. Add a CRM Update step to the same workflow. See Qualified lead to Zoho or Kylas.
Related#
- Blog: Google Sheets + AI voice agent: auto-call and log results
- Workflow triggers and steps
- Qualified lead to Zoho or Kylas
- Form submission to AI call
- Edesy Tables · AI voice agent · Zapier · n8n
Start free · Book a demo · Don't see your app? Request it