Askel connects to your customer's Airtable workspace, letting your product read and write records across bases and tables in the structured, relational format that Airtable customers already use to run their operations.
Use the Airtable records endpoint to insert new rows, populating single-line text, number, date, select, checkbox, linked record, and attachment fields.
List records with a filterByFormula expression to retrieve only the rows that match your criteria, reducing data transferred and processing time.
PATCH individual records by record ID to update specific fields without overwriting the entire row, preserving values set by the customer's team.
Remove records by ID, useful for archiving entries that your product has fully processed or replacing soft-delete patterns the customer uses.
Fetch the table and field metadata via the Airtable Meta API to discover field types and options at connect time, powering accurate field-mapping suggestions.
Post file URLs to attachment fields on a record, which Airtable fetches and stores. Useful for linking PDFs, images, or exports generated by your product.
You sell a project delivery tool. Lakeview Consulting tracks all client projects in an Airtable base called Client Delivery. When your product marks a project as complete, the corresponding Airtable record should be updated with the completion date, hours logged, and final status.
Lakeview's Airtable admin goes to airtable.com/create/tokens, creates a token with data.records:read and data.records:write scopes on the Client Delivery base, and pastes it into your product.
Askel calls the Meta API to read the Client Delivery table's fields: project name, client, status, completion date, and hours logged. A mapping draft appears immediately.
Askel uses filterByFormula to find the Airtable record whose Project ID field matches the completed project. This avoids creating duplicates.
Askel PATCHes the found record with the completion date, hours logged, and a status field value of Completed. Only those three fields are touched.
Askel records the Airtable record ID and update timestamp in your product's audit log. If Lakeview's team questions the data, your CS rep can trace the exact operation.
The customer generates a Personal Access Token from airtable.com/create/tokens, scoping it to the specific bases and permission levels needed. Askel stores the token securely. Personal Access Tokens support granular per-base scoping, so customers can grant access only to the bases relevant to your product without exposing their entire workspace.
© 2025 Askel.ai. All rights reserved.