Connect your Google account
Authorise access to the specific spreadsheet, not your whole Drive.
Integration · Google Sheets
The database your team already maintains.
Most teams in the region run on a sheet: prices, branches, stock, leads. The agent can read from it to answer, and append to it so nobody has to copy conversations by hand.
- Connect once
- Used in any flow
- Read and write
Google Sheets · leads-2026
External Request
NewAge
What connecting looks like.
Point at the sheet and range
Choose the tab and the columns the agent may read or append to.
Name the columns clearly
Clear headers make the agent’s answers accurate. ‘price_egp’ beats ‘Column D’.
Decide reads and writes
Reading for answers, appending for leads and orders. Keep them in separate tabs.
What the agent can do once it is connected.
Answers from a lookup
Price by product, availability by branch, fee by city — read live from the row that matters.
Appends leads
Name, phone, city, what they asked and which channel — written the moment the conversation qualifies.
Daily operations
A shift log, an order sheet, or a callback list your team already opens every morning.
No new tool to learn
Your team keeps working in the sheet they know; the agent just stops them from typing it in.
Limits and details worth checking first.
What it isWhat it means for your setup
Not a real databaseSheets are perfect up to a few thousand rows. Past that, response times and reliability suffer — move to a proper system.
Formatting mattersMerged cells, mixed data types and blank header rows are the most common cause of a wrong answer.
AccessAnyone who can edit the sheet can change what the agent says. Restrict editing like you would a price list.
Scopes, rate limits and field names are controlled by the provider and change with API versions. Confirm the current documentation before building a flow that depends on a specific field.
Asked during setup.
Can it update an existing row?
Appending is the safe default. Updating is possible, and should be limited to specific columns so history is not overwritten.
Is it fast enough for chat?
For a small lookup, yes. For large sheets, keep the range narrow and cache what rarely changes.
Can I use Excel instead?
If it is on a service with an API, through the External Request node. A local file cannot be read by a hosted agent.
Point the agent at the sheet you already trust.
It is usually the fastest integration in the whole setup, and the one your team feels on the first day.