Webflow does not have a built-in way to directly access external services via REST APIs—especially APIs that require authentication like OAuth (e.g., Google, Facebook, Mailchimp). Here's what you need to know:
1. No Native API Integration Support
- Webflow does not include built-in features for calling external REST APIs (e.g., no server-side scripting or fetch-like capabilities).
- There is no built-in OAuth or token management system in the Webflow Designer or CMS.
- To connect Webflow with services like Google Sheets, Mailchimp, or Facebook, you need to use third-party tools such as:
- Zapier
- Make (formerly Integromat)
- n8n
- These tools can listen for Webflow form submissions or CMS events and then trigger API calls using proper authentication (OAuth 2.0, access tokens).
3. Custom JavaScript for Public APIs
- You can embed custom JavaScript in Webflow pages (via custom code blocks) to call public APIs (not requiring OAuth).
- For APIs needing authentication, you would need to host sensitive tokens on a secure server—never store secrets in client-side code.
4. Use Webhooks + Middleware
- For secure and custom integrations:
- Trigger a Webhook from Webflow (e.g., form submission).
- Send the data to a serverless function (such as AWS Lambda, Google Cloud Functions, or a service like Pipedream or Xano).
- Authenticate and call the external API from that backend.
- Optionally, send a response back or update CMS content via the Webflow CMS API.
5. Limitations of Webflow Logic (Beta)
- As of now, Webflow Logic (automations currently in beta/limited release) does not support authenticated REST API calls directly.
- You can trigger Logic flows on form submissions, but for external API actions, you must still connect via third-party tools.
Summary
Webflow cannot natively call external REST APIs or handle authentication like OAuth. Use third-party tools (Zapier, Make) or middleware (serverless functions) to securely bridge Webflow with services like Google, Facebook, and Mailchimp.