> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Sheets

> Log every DialNexa call outcome to Google Sheets - a living record of what happened, what was said, and what comes next, always up to date.

Google Sheets is where most teams start when they need to track something. Call logs, lead lists, campaign results, appointment confirmations - if your team manages any of these in a spreadsheet, DialNexa can write call outcomes directly to the right rows and columns after every call, keeping your Sheets data current without anyone touching the keyboard.

<Note>
  Google Sheets is the right starting point for teams that aren't ready for a full CRM integration but need a reliable record of call outcomes. It's also the best place to audit DialNexa output before connecting to higher-stakes systems like Salesforce or HubSpot.
</Note>

## What this integration does

DialNexa connects to Google Sheets through the Google Sheets API. After a call, DialNexa can:

* **Append a new row** to a Sheet with call data - date, caller name, phone, outcome, notes, duration, and any captured variables
* **Update an existing row** - find the row that matches the caller's phone or email and update the outcome, status, or notes columns
* **Read from a Sheet** - pull a list of leads or contacts from Google Sheets as the data source for a DialNexa calling campaign
* **Look up a record** - check whether a caller already has a row in the Sheet before writing anything new

## When to use DialNexa with Google Sheets

**Campaign call logs** - every call in a campaign gets a row appended to a Sheet: date, phone, name, company, call outcome, summary, and follow-up flag. Your team has a clean, sortable log of every call without anyone creating it manually.

**Call list management** - your team builds a call list in Google Sheets. DialNexa reads the sheet, calls each row, and writes the outcome back - updating the status column for each row after the call.

**Audit and QA** - before connecting DialNexa to your CRM, use Google Sheets as the output. Review the first 100 calls' output in the Sheet, verify accuracy, and then expand to the full workflow once you're confident.

**Reporting and analysis** - Google Sheets integrates with Looker Studio, Google Analytics, and Data Studio. Logging DialNexa call data to Sheets gives you instant access to charts and dashboards without any data engineering.

**Ops and field teams** - for teams without a CRM, Sheets acts as the lightweight customer database. DialNexa reads from and writes to the same Sheet the team already uses.

## What DialNexa writes to Google Sheets

<CardGroup cols={2}>
  <Card title="New rows" icon="plus-square">
    Appends a new row after each call - with date, caller, phone, outcome, duration, summary, and any captured data - building a complete call log automatically.
  </Card>

  <Card title="Row updates" icon="edit">
    Finds the row matching the caller's phone or email and updates the outcome, status, notes, and follow-up date columns - keeping your call list current.
  </Card>

  <Card title="Call list reads" icon="list">
    Reads rows from a Google Sheet to build a DialNexa call list - pulling name, phone, and any other columns your agent needs for context.
  </Card>

  <Card title="Structured data fields" icon="table">
    Writes specific data fields to dedicated columns - not just a notes dump - so the Sheet stays filterable and analyzable.
  </Card>
</CardGroup>

## Setting up the integration

In your DialNexa agent workflow, configure Google Sheets as a data source (for call lists) and/or a data destination (for call outcomes).

1. **Google Sheets connection** - Google OAuth (set up once in DialNexa integrations; authorize access to specific Sheets)
2. **Spreadsheet and sheet tab selection** - which Google Spreadsheet and which tab to read from or write to
3. **Column mappings** - which DialNexa variables write to which column letters or headers
4. **Match logic** - for row updates, which column to match against (typically phone number or email)
5. **Action** - append row, update row, or read rows
6. **Header row** - specify whether your Sheet has a header row so DialNexa maps columns correctly

## Workflow ideas

<AccordionGroup>
  <Accordion title="Call log: a real-time record of every call">
    Every DialNexa call appends a row to a shared Google Sheet: Date | Time | Name | Phone | Company | Outcome | Duration | Summary | Follow-up. By end of day, the Sheet has a complete log of every call made. The ops team can filter, sort, and analyze without waiting for a report.
  </Accordion>

  <Accordion title="List dialing: call a Sheet, write results back to the same Sheet">
    Your team builds a list in Google Sheets: columns for Name, Phone, Company, and Status (set to "To Call"). DialNexa reads every row where Status = "To Call," makes the calls, and writes the outcome back to the Status column. By the end of the campaign, the Sheet shows exactly what happened with every contact.
  </Accordion>

  <Accordion title="QA before going live: validate DialNexa output in a Sheet">
    You're about to connect DialNexa to your Salesforce or HubSpot. Before doing so, run the first 200 calls with Google Sheets as the only output. Review each row - is the outcome accurate? Are the notes useful? Are the contact details right? When the Sheet looks clean, connect to the CRM.
  </Accordion>

  <Accordion title="Campaign reporting: data in Sheets, charts in Looker Studio">
    DialNexa writes call outcomes to a Google Sheet. Connect that Sheet to Looker Studio and build a live dashboard: calls per day, connection rate, outcome distribution, lead quality by source. Management gets a real-time view of campaign performance without opening DialNexa.
  </Accordion>
</AccordionGroup>

## Pairing Google Sheets with other integrations

* **Google Sheets + HubSpot** - use Sheets for the initial audit, then enable HubSpot once you're confident in output quality
* **Google Sheets + Slack** - when a specific call outcome is written to Sheets (e.g., hot lead), trigger a Slack notification to the team
* **Google Sheets + Gmail** - after logging call results to Sheets, use Gmail to send follow-up emails for specific outcome rows
* **Google Sheets + Google Looker Studio** - connect your call log Sheet directly to Looker Studio for automated campaign performance dashboards

## Common questions

<AccordionGroup>
  <Accordion title="Can DialNexa update an existing row in Google Sheets?">
    Yes. DialNexa searches the Sheet for a row where a specific column (e.g., phone number) matches the caller, then updates the designated columns in that row. If no match is found, it can append a new row or leave the Sheet unchanged.
  </Accordion>

  <Accordion title="How does DialNexa handle Google Sheets with multiple tabs?">
    You specify the tab (sheet) name when configuring the action. Each DialNexa workflow action points to one specific tab. If you need to write to multiple tabs, you add multiple Sheets actions to the workflow.
  </Accordion>

  <Accordion title="Can DialNexa use a Google Sheet as a call list?">
    Yes. Configure a DialNexa campaign to pull call list data from a Google Sheet - reading the phone number, name, and any context columns. After each call, the outcome can be written back to the same row.
  </Accordion>

  <Accordion title="Will DialNexa overwrite data in a row it updates?">
    Only the columns you configure for update. DialNexa writes to the specific columns you map in the action configuration - other columns in the row are untouched.
  </Accordion>

  <Accordion title="Is there a row limit for Google Sheets?">
    Google Sheets supports up to 10 million cells per spreadsheet. For most calling campaigns, this is more than sufficient. For very large-scale operations, consider splitting into multiple Sheets by date or campaign.
  </Accordion>
</AccordionGroup>