Is it possible to do integration work on the staging domain before it goes into production in Webflow?

Yes, it is possible to test and integrate third-party services or custom code on a Webflow staging domain before publishing to a production domain.

1. Use Webflow’s Staging Subdomain

• Every Webflow project comes with a staging subdomain (e.g., yoursite.webflow.io) that you can use to preview and test your site.
• Publish to staging by clicking Publish in the Designer and selecting only the .webflow.io domain.
• This allows you to integrate code snippets, third-party services (like analytics, forms, or APIs), and test CMS features before pushing live.

2. Add and Test Custom Code

• You can insert custom code in Site Settings under the Custom Code tab or directly in page settings in the Before or sections.
• The custom code runs on the Webflow staging domain, so integrations like scripts or SDKs can be fully tested before production.
• Make sure third-party services (e.g., OAuth, Stripe, CRMs) allow calls from the webflow.io subdomain, or temporarily allow it if domain verification is required.

3. Test Forms, Webhooks, and Integrations

• All forms and logic (such as Zapier, Make, or custom webhooks) work normally on the staging environment.
• Be aware that emails sent from Webflow forms will be labeled as TEST submissions when submitted from the staging domain.

4. CMS and Logic Can Be Previewed

• You can create and test CMS collections, conditional visibility, and Webflow Logic flows on your staging site.
• These features will function the same as they would on the production domain.

5. Watch for Domain-Specific Behavior

• If your third-party integration depends on a specific verified domain, such as for domain-locking or redirect URIs, you may need to:
• Add a temporary redirect URI for the .webflow.io domain.
• Use feature flags or safe fallbacks that detect the domain and adjust behavior accordingly.

Summary

Yes, you can fully test integrations on Webflow’s staging domain (.webflow.io). Use it to verify design, logic, scripts, and third-party services before going live. Just ensure your integrations don’t depend on a specific domain that restricts staging access.