Fostr’s Airtable integration enables structured data to flow seamlessly across customer records, setup fields, onboarding assets, and more. This FAQ page answers common questions about permissions, credentials, and access control, ensuring your team understands how data from Airtable is securely authorized and who can see what.
Credentials and Access
To activate the Airtable integration, the following are required:
- API Key or OAuth Token for authentication
- Base ID and Table IDs to identify specific data sources
Additional details on access and security:
- Credentials are tenant-level and apply across the entire workspace or base, not individual users.
- Stored securely in encrypted fields within the Customer Record or Integration Recordset.
- Access is restricted to authorized Fostr roles, with read protections in place.
- Table-level read/write access must be granted within Airtable during setup. Full access to designated bases is strongly recommended for consistency.
- User emails are not needed, as the integration relies on field IDs rather than personal identifiers.
- Once configured, the sync is automated. Administrator involvement is only required if schema changes occur in Airtable, such as renamed or deleted fields.
Permissions and Visibility
Data retrieved from Airtable is used internally by Fostr and is structured into several categories:
- Permissions mapping
- Setup fields for configuration
- Customer onboarding state
- Metadata to support custom workflows
Visibility and access considerations:
- Synced data is visible only to internal Fostr team members such as Designers, Implementers, Operators, and Admins.
- End users do not see Airtable data directly, only through curated workflows built on top of it.
- There are no direct visibility configurations in the integration itself. Visibility depends on how data is mapped into Recordsets or Actions.
- After setup, access needs are minimal. The sync continues automatically, though schema updates in Airtable may require adjustments or relinking.