Databases & Spreadsheets — Airtable, Google Sheets & SQL
Giving an Agent Structured Data
To keep application data, customer leads, and operation logs structured without hosting a separate database, Langoedge agents can read and write Airtable and Google Sheets, or query a real relational database directly.
There are two routes, and they work quite differently:
| Route | Use for | How it's set up |
|---|---|---|
| MCP Connector | Airtable, Google Sheets, Notion, Coda, and other hosted data apps. | Connect the account, add a connector node. |
| SQL toolkit | Your own Postgres or SQL Server database. | Enabled per deployment — see below. |
1. Airtable & Google Sheets (via MCP Connector)
Airtable and Google Sheets are reached through an MCP Connector, not through built-in tools.
Connect the account
Add an MCP Connector
Scope and attach
What these apps let an agent do
The exact tool names come from the provider, but the shape of the capability is stable:
Airtable — list bases and tables, read and search records (including formula-based filters), create rows, update rows, upsert on a key, and delete records.
Google Sheets — list spreadsheets and worksheets, read a range or whole worksheet, append rows, update existing rows, and find rows matching a query.
2. Relational Databases (SQL Toolkit)
For a real Postgres or SQL Server database, Langoedge has a SQL toolkit that lets an agent inspect the schema and run queries.
When enabled, the toolkit registers a set of standard LangChain SQL tools for listing tables, inspecting schemas, checking a query, and executing it. Connection credentials are URL-encoded and handled server-side; the LLM never sees them.
Best Practices
Withhold destructive tools
Use the connector's tool scoping to turn off delete and bulk-update operations unless the agent genuinely needs them. Prompt instructions are a weaker guarantee than simply not exposing the tool.
Give the agent IDs, not guesses
Most write operations need a base, table, or spreadsheet ID. Let the agent list them first rather than hardcoding IDs into a prompt that will break when someone renames something.
Keep writes off the voice loop
MCP connectors are Text Graph only. A voice agent should call the Text Graph asynchronously so a slow spreadsheet write doesn't leave the caller in silence.
Summarize before returning
A raw record dump burns context. Put a summarization step after a large read so only the relevant fields re-enter the conversation state.