Airtable
Paste an API keyAppend records to any base — the first connector we proved live, record by record.
What you can do
- Add an Airtable record — JSON fields (templates work), typecast on, read-back verified
No false success: every send/create in Airtable is verified — ASHDOCS reads the item back from Airtable's API before the step turns green. If it can't be found, the run fails honestly instead of pretending.
Get your Airtable credentials
- 1Go to airtable.com/create/tokens and click Create new token.
- 2Add scopes data.records:read and data.records:write.
- 3Under Access, add the base(s) your flows will write to.
- 4Create the token and copy it (starts with pat).
Add the connection in ASHDOCS
- 1Open the Connections page in the flows console.
- 2Click “Connect with a key” and pick Airtable.
- 3Paste: Personal access token. ASHDOCS validates the credentials against Airtable before saving — a bad key is rejected with a plain-English reason, never stored.
Use it in a flow
In the flow builder, add the Airtable step, pick your connection, and fill the fields — values from earlier steps drop in as {{s1.field}} placeholders. Then hit Test this step in the step's panel to run it on its own before switching the flow on.
Troubleshooting
403 “refused the record”
The token can't see that base — edit the token's Access list, or check the base ID (starts with app, from the base URL).
“Record fields must be valid JSON”
Use a JSON object, e.g. {"Name": "{{trigger.body.name}}", "Status": "New"}.
FAQ
Is the record verified?
Yes — ASHDOCS GETs the new record back by ID and only goes green when Airtable confirms it exists. This was proven live against a real base.
Do field types have to match exactly?
Typecast is on — Airtable converts sensible values (e.g. "3" into a number) automatically.