Background

We have a Webflow website that is integrated with an Airtable base for dynamic content synchronization. The Webflow/Airtable integration was originally established with the NoBull Airtable App which has been retired and is replaced by Finsweet’s CMS Bridge. The data connection between Airtable and Webflow stopped functioning due to Airtable’s transition from API keys to Personal Access Tokens (PATs). All required tables and data remain intact in Airtable.

We have both Webflow Dev and Staging Environments available for safe setup and testing. You will be required to advise requirements for (or directly execute) backups of both Webflow website and Airtable account instances to ensure risk minimisation.

Project Goals

• Restore and future-proof automated sync between Airtable and Webflow CMS

• Ensure compliance with Airtable’s new authentication (PATs)

• Achieve robust, secure, and well-documented integration via Finsweet CMS Bridge or best-practice alternative

• Maintain data integrity (no loss or duplication)

• Provide post-launch support for bug fixes and troubleshooting

Current State

• All Airtable tables and data are intact and accessible.

• Webflow API keys and OAuth are set up, with references to previous NoBull integration; current linkage is broken.

• No active/visible Airtable API key in custom code—suggests previous integration was server-side or via third-party tools.

• Site relies on dynamic content from Airtable for key CMS collections.

• Webflow Dev and Staging Environments are ready for non-disruptive deployment/testing.

Scope of Work

Situation Assessment & Audit

• Review current Webflow site settings, custom code, integrations, and Connected Apps to determine where and how Airtable sync was/is configured.

• Identify whether Finsweet CMS Bridge is currently in use, partially configured, or if a new setup is required.

• Map Airtable structures to corresponding Webflow CMS Collections.

Authentication & Security Update

• Replace deprecated Airtable API key(s) with a new Personal Access Token (PAT) as required by Airtable’s updated API policies.

• Ensure secure handling of the PAT, avoiding exposure in client-side code.

Integration Restoration or Rebuild

• Re-link/restore existing integration OR rebuild using Finsweet’s latest CMS Bridge (or another best-practice solution), as needed.

• Ensure stable, automated sync based on current requirements.

• Map all essential fields between Airtable and Webflow Collections and test for completeness and accuracy.

Testing & QA

• Fully test integration in the Webflow Dev and Staging Environments, ensuring data syncs accurately and reliably.

• Confirm no loss of data and that all dynamic content is displaying/operating as intended.

Documentation

• Provide clear, step-by-step technical documentation of the new setup—including how to update PAT in future, and recommended maintenance tasks.

Deployment & Monitoring

• Deploy updated integration to the live environment following successful staging QA.

• Monitor for initial data flashes or sync errors.

Post-Launch Support

• Provide a reasonable period of post-launch support (e.g., 2–4 weeks) for bug fixes, troubleshooting, and minor adjustments to ensure a smooth handover.

Deliverables

• Working, robust Airtable ↔ Webflow CMS integration

• Written documentation (integration overview, credentials updating, troubleshooting guide)

• List of mappings between Airtable tables/fields and Webflow CMS Collections/fields

• Post-launch support agreement (details to be discussed/finalized with chosen partner)

Your Response

Please outline your approach based on the above scope, fixed cost estimate and timeline, relevant experience with Webflow, Airtable, and Finsweet CMS Bridge, and your terms for post-launch support. If you recommend any enhancements or alternatives, please include your rationale.

Thank you—we look forward to working with a partner who can deliver a stable, future-proof solution that minimizes risk and maintains business continuity for our Webflow website.

• Please outline your approach based on the above scope, fixed cost estimate and timeline, relevant experience with Webflow, Airtable, and Finsweet CMS Bridge, and your terms for post-launch support

• All required tables and data remain intact in Airtable
• You will be required to advise requirements for (or directly execute) backups of both Webflow website and Airtable account instances to ensure risk minimisation
• Restore and future-proof automated sync between Airtable and Webflow CMS
• Ensure compliance with Airtable’s new authentication (PATs)
• Achieve robust, secure, and well-documented integration via Finsweet CMS Bridge or best-practice alternative
• Maintain data integrity (no loss or duplication)
• Provide post-launch support for bug fixes and troubleshooting
• All Airtable tables and data are intact and accessible
• Webflow API keys and OAuth are set up, with references to previous NoBull integration; current linkage is broken
• No active/visible Airtable API key in custom code—suggests previous integration was server-side or via third-party tools
• Site relies on dynamic content from Airtable for key CMS collections
• Webflow Dev and Staging Environments are ready for non-disruptive deployment/testing
• Situation Assessment & Audit
• Review current Webflow site settings, custom code, integrations, and Connected Apps to determine where and how Airtable sync was/is configured
• Identify whether Finsweet CMS Bridge is currently in use, partially configured, or if a new setup is required
• Map Airtable structures to corresponding Webflow CMS Collections
• Authentication & Security Update
• Replace deprecated Airtable API key(s) with a new Personal Access Token (PAT) as required by Airtable’s updated API policies
• Ensure secure handling of the PAT, avoiding exposure in client-side code
• Integration Restoration or Rebuild
• Re-link/restore existing integration OR rebuild using Finsweet’s latest CMS Bridge (or another best-practice solution), as needed
• Ensure stable, automated sync based on current requirements
• Map all essential fields between Airtable and Webflow Collections and test for completeness and accuracy
• Fully test integration in the Webflow Dev and Staging Environments, ensuring data syncs accurately and reliably
• Confirm no loss of data and that all dynamic content is displaying/operating as intended
• Provide clear, step-by-step technical documentation of the new setup—including how to update PAT in future, and recommended maintenance tasks
• Deployment & Monitoring
• Deploy updated integration to the live environment following successful staging QA
• Monitor for initial data flashes or sync errors
• Provide a reasonable period of post-launch support (e.g., 2–4 weeks) for bug fixes, troubleshooting, and minor adjustments to ensure a smooth handover
• Deliverables
• Working, robust Airtable ↔ Webflow CMS integration
• Written documentation (integration overview, credentials updating, troubleshooting guide)
• List of mappings between Airtable tables/fields and Webflow CMS Collections/fields
• Post-launch support agreement (details to be discussed/finalized with chosen partner)