Webflow Connector
Connector implementation
Build the Webflow integration
Form submissions, ecommerce products, orders, inventory, custom code injection, CMS collections, and webhooks from Webflow sites via the v2 Data API. Phase 1 of the Webflow ↔ Brevo native app pilot.
Implementation Overview
Implement a Webflow connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
The connector is marked runtime-ready. Verify production credentials, scopes, and workspace settings before enabling sync.
api.webflow.com
| Property | Value |
|---|---|
| Integration surface | API + MCP |
| Implementation status | Runtime-ready (OpenAPI mode) |
| Category | Website Builder |
| Setup complexity | easy |
| Vendor documentation | developers.webflow.com/data/docs/getting-started-apps |
| Allowed host | api.webflow.com |
| Base URL | https://api.webflow.com/v2 |
| OpenAPI schema | connectors/webflow/openapi.yml |
| MCP server | mcp.webflow.com/sse |
| Last researched | 2026-08-07 |
The MCP endpoint was verified by handshake on 2026-08-07: 401 with RFC 9728 metadata; it is its own authorization server and supports dynamic client registration.
Authentication
-
Bearer token (OpenAPI mode). Sent as
Authorization: Bearer <token>. Alto resolves it per workspace (WEBFLOW_ACCESS_TOKEN). -
OAuth 2.0 (MCP mode).
- Authorize: mcp.webflow.com/oauth/authorize
- Token: mcp.webflow.com/oauth/token
- The authorization server publishes no scope list.
-
Restrict outbound API traffic to
api.webflow.comunless the vendor documents additional regional hosts. -
Use
https://api.webflow.com/v2as the default REST base URL and keep regional or account-specific overrides configurable. -
Use
connectors/webflow/openapi.ymlto generate or validate typed API clients and request models. -
Validate the MCP server endpoint at mcp.webflow.com/sse and document required headers, auth grants, and tool availability.
-
Keep developers.webflow.com/data/docs/getting-started-apps linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Commerce, payment, or subscription objects
- Events, webhooks, and behavioral activity
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
| Resource | Direction | Conflict handling |
|---|---|---|
form_submissions | inbound | n/a |
orders | inbound | n/a |
Mapping To Tajo/Brevo
Webflow has a typed contract, and every resource on it is read for context rather than projected into Brevo. That is a recorded decision, not a gap: no field of this connector currently becomes a Brevo contact, list, or event.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.