Reconcile a tracker. Use the permitted Airtable records and show me the supporting evidence.
Once the records are shared with me, I’ll compare selected rows with the source-system data supplied for review.
Selected rows from a table in one base, with their supported named cell values.
Reconcile a tracker
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
1What’s connected.
Reconcile operational trackers and prepare a clear account of missing work. Select the records to share in Seal, then reference them with @ in documents, comments and Neil.
Connection setup and permissions
Seal’s Airtable connector reads one base with a personal access token scoped to schema.bases:read and data.records:read. It does not write to Airtable.
Search covers primary-field text or a number and examines at most 500 rows. Selected rows are captured with their supported named cell values.
Attachments, linked-record contents, and formula, lookup and rollup fields are not included.
Set up Airtable
- In Airtable’s developer hub, create a personal access token with schema.bases:read and data.records:read, restricted to the intended base.
- Open Settings → Integrations → Airtable. Enter the base URL and token, then choose Test and connect.
- Choose a table, search primary-field text, select rows and Seal groups, and enable sharing.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3What Neil can do with Airtable once connected
Once the connection is set up and the records are shared:
- Reconcile a tracker
- Compare selected rows with the source-system data supplied for review.
- Prepare an operations brief
- Summarise the recorded status, owners and overdue work in the selected rows.
- Plan a process migration
- Inspect the fields of selected rows to propose a structured workflow in Seal.
4Connection questions
Does it copy the whole base?
No. Only the rows you select from a table are shared. Linked records are not fetched.
5Before it goes live.
Access
The organisation library reads only; it makes no changes in Airtable. Define which records are shared and which Seal groups can read them.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.