Integrations
Connecting to Airtable
Read and update records across your bases, so a tracker stays current without anyone retyping it.
Connect Airtable and Gini can read and update records across your bases, so the trackers your team runs on stop going stale.
What it can do
- List your bases. What the connection can reach.
- Read a base's schema. Tables and fields, which is what lets you say "the roadmap base" instead of an id.
- List and read records. Filtered, or one at a time.
- Create records.
- Update records, including several at once.
How to connect
Open Integrations
app.ginicomputer.com → Integrations → Airtable.
Authorise in Airtable
Airtable's own consent screen shows what is granted.
Come back
Gini can now work in the bases you granted.
The connection asks for three scopes: read records, write records, and read base schema. It needs the schema one to know what your fields mean.
What changes anything
| Operation | What it does | Changes anything? |
|---|---|---|
| List bases | See what is reachable | No |
| Get base schema | Read tables and fields | No |
| List records | Read a table, filtered | No |
| Get record | Read one record | No |
| Create records | Add new rows | Yes |
| Update records | Change existing rows, in bulk | Yes |
Note what is missing: there is no delete. Gini cannot remove a record or a table through this connection.
What it's great for
- The tracker nobody maintains. Roadmaps, vendor lists, content calendars, hiring pipelines. These go stale in a predictable way, and it is always because updating them is somebody's fourth priority.
- Filling from another source. "Add a row to the leads base for everyone who emailed us about pricing this week."
- Finding the gaps. "Which rows are missing an owner or a due date?"
- Answering without opening it. "What is in the Q3 roadmap base, and what has not moved in a month?"
Example routine
Keeping a pipeline base current without anyone typing:
- Each morning, read yesterday's inbound from email.
- Add a row per new lead, with source and first message.
- Update rows where something changed rather than duplicating them.
- Post the count and anything ambiguous in the channel.
Good to know
- It works within your Airtable access. Bases your account cannot reach stay unreachable.
- Bulk updates are exactly as fast as they sound. "Update multiple records" is one call, which is good for throughput and worth respecting. On anything wide, ask for the list first.
- Say which base and table. Gini can read your schema, but two tables called "Pipeline" in different bases is a coin flip.
- Airtable has no version history to fall back on. Unlike Notion or Google Sheets, an overwrite here is not one click from being undone. That is the reason to review before a wide update rather than after.
Make it a routine once it works twice
Updating the same base from the same source is the textbook case for a routine. Run it by hand until the shape is right, then let Gini take it over.
Troubleshooting
Gini can't see a base
Check the grant covers it. Airtable authorises per base, and one created after you connected will not be included until you update the grant.
It wrote to the wrong table
Name the base and the table in the ask. This is the most common cause by some distance.
A write failed
Usually a field type mismatch, a required field left empty, or a single-select value that does not exist yet. Gini reports which field.