Zentrik + Airtable
Turn structured requirements, feedback, roadmaps, and trackers into mapped Discovery evidence or ideas.
Admins save one workspace credential in Settings → Integrations.
Connect a workspace Airtable personal access token, choose a base and table, then map rows into signals or ideas. Linked records can be matched to Zentrik accounts so imported demand keeps its customer context.
The import is review-first and read-only toward Airtable. Zentrik imports only the rows you choose and does not write changes back to the base.
Connect Airtable
- In Airtable, create a personal access token with data.records:read and schema.bases:read for only the bases Zentrik should access.
- In Zentrik, open Settings → Integrations → Airtable.
- Paste the token and save the connection. Zentrik stores it server-side and does not show it again.
Import a table
- Open Discovery, choose New → Bring in data → Airtable.
- Select a base and table.
- Choose whether each row represents a signal or an idea.
- Map the title, body, source fields, and any linked account records.
- Preview the result, resolve account matches, and import only the ready rows.
Use signals for evidence such as customer requirements or feedback. Use ideas for solution or backlog records that already describe something the team may build.
Data and access
- The token controls which bases and tables Zentrik can read.
- Zentrik reads table schema, selected records, and linked records needed for mapping.
- Existing Airtable records are not edited.
- Rotate the token in Airtable and replace it in Zentrik if access should change or the token may have been exposed.
Troubleshooting
Check credentials and permissions on both sides first. If you have verified everything and it still fails, contact us with your workspace name and what you tried.
A base or table is missing
Edit the Airtable token and grant it access to that base, then reconnect in Zentrik.
Linked customers do not match accounts
Review the linked-record field and match the unresolved values to Zentrik accounts before importing.
The token is rejected
Confirm it is a current Airtable personal access token with schema and record read scopes, then paste it again without extra spaces.
