Webflow Connector

Connector status: Live Verified. Tajo runs this connector today.

Illustration · sample data

Sync example

Review one record

Source

Webflow

Connector status: Live

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

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.

Website Builder
WebflowAPI / MCP / docsTajo connectorauth, mapping, syncretries, logs, checksBrevo activationcontacts, events, campaignsbackfill, webhooks, validation
Webflow connector flow from source system to Tajo mapping and Brevo activation.

Implementation Overview

Build target

Implement a Webflow connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

Current status

The connector is marked runtime-ready. Verify production credentials, scopes, and workspace settings before enabling sync.

Primary surface

api.webflow.com

PropertyValue
Integration surfaceAPI + MCP
StatusLive
CategoryWebsite Builder
Setup complexityeasy
Vendor documentationdevelopers.webflow.com/data/docs/getting-started-apps
Allowed hostapi.webflow.com
Base URLhttps://api.webflow.com/v2
OpenAPI schemaintegrations/webflow/spec/openapi.yml
MCP servermcp.webflow.com/sse
Last researched2026-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>. Tajo resolves it per workspace (WEBFLOW_ACCESS_TOKEN).

  • OAuth 2.0 (MCP mode).

  • Restrict outbound API traffic to api.webflow.com unless the vendor documents additional regional hosts.

  • Use https://api.webflow.com/v2 as the default REST base URL and keep regional or account-specific overrides configurable.

  • Use integrations/webflow/spec/openapi.yml to 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

ResourceDirectionConflict handling
form_submissionsinboundn/a
ordersinboundn/a

Mapping To Tajo/Brevo

form_submissions → Brevo contact

Requires: workspace api key.

Source fieldBrevo destinationViaNote
fields.emailemail—pickField tries email, Email, e-mail, E-mail; a submission with neither email nor phone is skipped.
fields.firstNameFIRSTNAMEunified.firstName
fields.lastNameLASTNAMEunified.lastName
idWEBFLOW_CONTACT_IDunified.externalId

orders → Brevo event

Requires: workspace api key.

Source fieldBrevo destinationViaNote
idevent.properties.orderId—
total_priceevent.properties.value—
currencyevent.properties.currency—
customer.emailevent.identifiers.email_id—

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.

Sources

Request early access

Enter your first name and email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: webflow.md

Loading Markdown…