Once Airtable is connected to Fostr, it becomes a powerful engine for syncing structured records, tracking onboarding states, and powering configuration workflows. This page explains what data is synced, how often it updates, and what Fostr does with that data once it arrives.

Data Refresh, Frequency and Sync Timing

Fostr syncs with Airtable on a recurring schedule. Syncs generally occur at least once daily, but timing can vary depending on tenant configuration. Some tenants choose shorter intervals to capture updates in near real time, while others prefer standard daily refreshes for efficiency. Syncs can also be triggered by update events so changes in Airtable are quickly reflected in Fostr.

The refresh interval is configurable on a per-tenant basis. This flexibility makes it possible to adapt the integration for bases with sensitive triggers or higher-volume workflows. Once the integration is set up, the process runs automatically and does not require ongoing administrator involvement. Manual triggers are also available through automation flows when immediate updates are necessary.

Known timing considerations include:

• Delays: Minimal, but possible if Airtable’s API rate limits (5 requests per second per base) are reached.
• Schema mismatches: Renamed or deleted fields and tables can cause interruptions.
• Best practice: Keep bases lightweight and naming consistent to avoid issues.

Data Coverage and Historical Access

When an Airtable base is first connected, Fostr performs a full backfill of all existing records. This ensures no historical data is missing and that the integration starts with a complete, accurate snapshot of configured Airtable tables. After this initial ingestion, updates follow an incremental sync pattern, meaning new or changed records are captured during refresh without duplicating older data.

The integration supports row-level access to records, making it possible to pull deeply descriptive datasets from Airtable. However, not all field types are included automatically.

Key points on coverage:

• Historical access: Full initial backfill of relevant tables.
• Exclusions: Field types like images or attachments are excluded unless explicitly mapped.
• Views: Hidden or filtered views are only included if configured.

Data Scope and Granularity

The integration captures a broad set of Airtable information and translates it into structured data within Fostr. This typically includes customer onboarding configurations, workflow field definitions, permission templates, and view information. By syncing at the record level, Fostr ensures workflows and onboarding sequences are fully aligned with Airtable data.

The detail included per record is comprehensive:

• Field names and values
• Field types (e.g., single select, linked record, checkbox)
• Record IDs along with update metadata such as last modified time

There are some limitations:

• API rate limits: Airtable enforces 5 requests per second per base, which affects large or multi-table syncs. Sync flows must be optimized to handle heavier loads.
• Versioning: Airtable remains the system of record. Fostr ingests new data with metadata tags, but upstream changes in Airtable overwrite prior values.