Ellipse Gradient for Header

Webflow Integration Guide

Integrate Webflow sites, CMS content, forms, assets, and selected events with enterprise systems through REST APIs, OAuth 2.0, API tokens, and webhooks.

Webflow integration options at a glance

Webflow’s primary integration model is the Data API v2 REST API, authenticated with OAuth 2.0 or bearer API tokens. The API supports sites, CMS Collections and Collection items, pages, assets, forms, submissions, webhooks, and other documented resources. Webflow also provides webhook notifications for selected event types, bulk operations for some CMS workflows, and asset endpoints for supported file operations. Martini can consume these APIs, receive Webflow webhook events through an exposed API, schedule paginated synchronization workflows, map JSON payloads, apply validation and business rules, and route results to enterprise applications. Event coverage should be supplemented with scheduled REST reads where Webflow does not provide the required notification.

Integration pointSupported by Webflow?Common use casesHow Martini supports it
REST APIsYesThe Webflow Data API v2 provides access to sites, Collections, Collection items, pages, assets, forms, webhooks, and other documented resources. It can support CMS reads, writes, publishing, and archival operations where the endpoint and permissions allow.Martini can consume Webflow REST endpoints from workflows, handle JSON responses and pagination, map fields, apply business rules, and call downstream APIs.
WebhooksLimitedWebflow sends notifications for selected event types, including supported CMS- and form-related events. Coverage is event- and resource-specific rather than universal.Martini can expose a REST API or webhook receiver, validate and normalize the payload, route by event type, retrieve authoritative resource data, and enforce idempotency.
Bulk / batch APIsLimitedBulk operations are available for selected CMS workflows and can reduce one-request-per-item processing. Limits and supported operations are resource-specific.Martini can partition Collection item workloads, invoke supported batch operations, track partial failures, and fall back to controlled individual requests when required.
File and asset APIsYesWebflow asset endpoints support documented asset and file operations, including retrieving asset metadata and supported management actions.Martini can transfer or reference asset metadata, associate assets with CMS items, and handle large-file or upload failures separately from ordinary JSON errors.
AuthenticationYesWebflow supports OAuth 2.0 for multi-user or multi-workspace applications and bearer API tokens for controlled internal integrations. Permissions are scope- and resource-dependent.Martini can keep tokens and OAuth configuration in secrets or environment configuration, send bearer credentials, and protect inbound APIs receiving Webflow events.
Scheduled synchronizationYesScheduled REST reads can supplement webhook coverage for resources or event types without the required notifications. Synchronization must be designed per resource.Martini can schedule workflows, process paginated responses, maintain cursors or timestamps where suitable, checkpoint progress, and retry transient failures.

How Webflow exposes data and business events

Webflow REST APIs

The Webflow Data API v2 is the principal programmatic interface for sites, CMS Collections and Collection items, pages, assets, forms, webhooks, and other documented resources. It supports read and write operations where the relevant endpoint and authorization permit them.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with an OAuth access token or bearer API token, calls the required endpoint, processes paginated JSON, maps the response to a canonical model, applies business rules, and writes to the target system. Resource-specific bulk operations can be used for supported CMS workloads.

Implementation sequence

Retrieve credentials from Martini secrets
Call the required Webflow REST endpoint
Process pages or cursors until synchronization is complete
Validate and map Webflow JSON fields
Apply business and publication rules
Write the result to the target system and store a checkpoint

Webflow Webhooks

Webflow supports webhook notifications for selected event types, including supported CMS- and form-related changes. Notifications do not cover every possible Webflow operation, so event coverage must be checked for each workflow.

Martini implementation pattern

Martini implementation pattern: expose an authenticated REST endpoint for Webflow delivery, validate the request, identify the event and resource, check for duplicate processing, and retrieve the current resource when the notification is incomplete before invoking downstream actions.

Implementation sequence

Receive the Webflow webhook notification
Validate the request and event payload
Create and check an event deduplication key
Retrieve the current Webflow resource when required
Route the event to the appropriate workflow
Write downstream changes and record processing status

Webflow CMS Bulk Operations

Webflow provides bulk operations for selected CMS workflows. These operations can improve throughput for Collection item synchronization but are limited to documented resources and request sizes.

Martini implementation pattern

Martini implementation pattern: partition a source dataset into supported batch sizes, map each item to Webflow fields, submit bulk requests, inspect item-level or request-level outcomes, and retry only eligible failures without duplicating successful writes.

Implementation sequence

Load the source dataset and determine the synchronization scope
Resolve Collection schema and references
Partition items within Webflow batch limits
Map and submit the supported bulk operation
Record successes and isolate failed items
Retry transient failures and route permanent failures to exception handling

Webflow Asset APIs

Webflow exposes asset-related endpoints for supported asset operations. Integrations may transfer files, store asset metadata, or associate assets with CMS content depending on the endpoint and permissions.

Martini implementation pattern

Martini implementation pattern: retrieve or receive the source asset, determine whether the target needs a file or only metadata, call the supported Webflow asset operation, and associate the resulting identifier with the relevant Collection item.

Implementation sequence

Determine whether the workflow transfers a file or asset reference
Retrieve source metadata and validate file constraints
Call the supported Webflow asset endpoint
Store the Webflow asset identifier or URL
Associate the asset with the target CMS item
Retry transfer failures and record inaccessible or expired URLs

Common Webflow integration patterns

Pattern 1: Synchronize CMS content to Webflow

When to use this pattern

Use this pattern when an editorial, product, event, or business system owns content that must be published into Webflow Collections. It supports one-way or selected bidirectional synchronization with validation before publication.

Integration direction
Source application
Martini
Webflow
Example Mapping
Webflow FieldCanonical FieldTarget Field
nametitlename
slugurlSlugslug
publishedDatepublicationDatedate
imageUrlprimaryAssetimage
Martini implementation pattern

A Martini workflow retrieves approved source content, resolves related records and assets, transforms field types and identifiers, validates required Webflow fields, and creates or updates Collection items. It uses stable correlation keys, supported bulk operations where appropriate, and retries rate-limited calls while routing schema or reference failures to an exception path.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Process Webflow form submissions

When to use this pattern

Use this pattern when website inquiries, support requests, or partner forms must create actionable records in a business application such as Salesforce, HubSpot, Zendesk, ServiceNow, or Jira.

Integration direction
Webflow
Martini
Salesforce
Example Mapping
Webflow FieldCanonical FieldTarget Field
emailcontactEmailEmail
namecontactNameName
messagerequestDescriptionDescription
submissionIdsourceSubmissionIdExternal ID
Martini implementation pattern

Martini receives a supported Webflow event or retrieves submissions on a schedule, normalizes form fields, applies routing and consent rules, and upserts the downstream object. It preserves the Webflow submission identifier, protects personal data in logs, and prevents duplicate creation before retrying transient target errors.

Martini capabilities used
  • webhook receiving
  • workflows
  • data mapping
  • business rules
  • error handling

Pattern 3: Drive downstream automation from Webflow events

When to use this pattern

Use this pattern when selected CMS or form events should trigger search indexing, notifications, catalog updates, or approval workflows without waiting for a full scheduled synchronization.

Integration direction
Webflow
Martini
Search or business application
Example Mapping
Webflow FieldCanonical FieldTarget Field
eventTypechangeTypeevent.type
resourceIdwebflowResourceIdsource.id
siteIdwebflowSiteIdsource.site
eventTimestampoccurredAtevent.occurredAt
Martini implementation pattern

A Martini API receives and validates the Webflow webhook, checks an event key for prior processing, retrieves the authoritative resource when needed, and routes the event by type. Downstream calls are isolated behind reusable workflow steps with retry handling and a dead-letter or exception path for invalid events.

Martini capabilities used
  • APIs
  • webhook receiving
  • workflow orchestration
  • idempotency rules
  • error handling

Pattern 4: Run scheduled Webflow synchronization

When to use this pattern

Use this pattern for resources without sufficient webhook coverage, for reconciliation, or for large CMS, asset, page, or submission synchronizations that need checkpointed processing.

Integration direction
Webflow
Martini
Enterprise data store
Example Mapping
Webflow FieldCanonical FieldTarget Field
idsourceObjectIdwebflow_id
updatedOnsourceUpdatedAtlast_updated
collectionIdsourceCollectionIdcollection_id
archivedisArchivedarchived
Martini implementation pattern

A scheduled Martini workflow reads paginated Webflow responses, maintains a cursor or last-processed state where suitable, maps objects into a canonical model, and upserts the data store. It controls concurrency, backs off on rate limits, checkpoints successful pages, and resumes without reprocessing completed work.

Martini capabilities used
  • scheduling
  • workflows
  • API consumption
  • data mapping
  • checkpointing
  • error handling

Applications commonly integrated with Webflow

Webflow commonly serves as a website, CMS, and presentation layer connected to business applications. Martini can orchestrate these flows through Webflow APIs and webhooks, while separately consuming the APIs of each target application.

Application Scenario Direction Martini Pattern
Salesforce Send Webflow form submissions to Salesforce Leads or Contacts and optionally return CRM-owned campaign or status information. Webflow → Martini → Salesforce Receive or retrieve Webflow submissions, validate and normalize fields, upsert the Salesforce object, preserve the Webflow submission identifier, and route failures for retry or review.
HubSpot Route website inquiries and marketing form data into HubSpot contacts, companies, or campaigns. Webflow → Martini → HubSpot Use a Webflow webhook or scheduled submission read, map form fields to HubSpot properties, apply duplicate rules, and record the downstream identifier and processing status.
Shopify Synchronize product or commerce-related content when Webflow provides the presentation layer and Shopify remains the transactional commerce system. Shopify → Martini → Webflow Read approved Shopify product data, transform it into Webflow Collection fields, resolve references and assets, update items in controlled batches, and retry rate-limited calls.
NetSuite Publish selected product, inventory, or business content from NetSuite to a customer-facing Webflow site. NetSuite → Martini → Webflow Retrieve approved NetSuite data, apply publication and field-validation rules, upsert Webflow Collection items, and return synchronization results to the originating workflow.
Zendesk Convert Webflow contact or support-form submissions into Zendesk tickets and preserve the ticket reference for follow-up. Webflow → Martini → Zendesk Normalize the submission, apply routing and priority rules, create or update a Zendesk ticket, and handle duplicate submissions and transient API errors.
ServiceNow Create cases, requests, or incidents from structured Webflow forms used by customers, partners, or employees. Webflow → Martini → ServiceNow Receive the Webflow event, validate personal and business data, map the form to the selected ServiceNow object, write the record, and persist correlation and retry state.
Jira Create Jira issues from website feedback, defect reports, or internal request forms. Webflow → Martini → Jira Route selected Webflow submissions, transform fields into Jira issue attributes, apply project and issue-type rules, and store the created issue key for duplicate prevention.
Workday Publish approved careers or organizational content from Workday-related processes into Webflow CMS structures. Workday → Martini → Webflow Retrieve approved Workday content through its available APIs, map it to Webflow Collection fields, resolve referenced assets, and publish only after validation and approval checks.

How to build a Webflow integration in Martini

Objective

Choose OAuth 2.0 for multi-user or multi-workspace access, or a bearer API token for a controlled internal integration, and keep credentials outside workflow definitions.

Instructions in Martini

  • Create the required Webflow authorization or token configuration
  • Store secrets in Martini secrets or environment configuration
  • Grant only the Webflow scopes required by the workflow
  • Confirm site-, workspace-, and resource-level permissions

Objective

Select a Webflow webhook for supported event types or a Martini scheduler for resources and changes that require polling or reconciliation.

Instructions in Martini

  • Confirm the Webflow event type and coverage
  • Expose an authenticated Martini API for webhook delivery when applicable
  • Use a scheduler for unsupported or periodic synchronization
  • Define the event or schedule correlation key

Objective

Call Webflow REST endpoints to retrieve the authoritative object, process pagination, and use bulk operations where the relevant CMS endpoint supports them.

Instructions in Martini

  • Call the required Data API v2 endpoint
  • Process every page or cursor
  • Retrieve the current resource after incomplete webhook payloads
  • Preserve Webflow identifiers and timestamps

Objective

Coordinate validation, enrichment, routing, target calls, and state management in a reusable Martini workflow rather than embedding logic in a single point-to-point script.

Instructions in Martini

  • Route by object type or event type
  • Resolve Collection references and dependent assets
  • Separate draft, approval, and publication actions
  • Persist checkpoints and correlation identifiers

Objective

Convert Webflow JSON, form fields, Collection references, and asset metadata into the target application’s canonical and native models.

Instructions in Martini

  • Map stable identifiers rather than display labels where possible
  • Convert dates, booleans, enumerations, and references
  • Validate required Webflow and target fields
  • Preserve source payload context for troubleshooting

Objective

Apply publication, routing, consent, duplicate, approval, and data-quality rules before writing to downstream systems or publishing Webflow content.

Instructions in Martini

  • Reject missing required fields
  • Apply target routing and ownership rules
  • Check event or submission deduplication state
  • Require approval before production publication

Common Webflow data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
SitesRepresent Webflow websites and site-level configuration or metadata used to select synchronization scope.Content platforms, commerce platforms, analytics repositoriesMartini retrieves site data through the REST API, applies site-specific routing rules, and stores identifiers in workflow state or a target system.
CollectionsDefine CMS structures, fields, types, and configuration for content synchronization.Content platforms, product systems, editorial systemsMartini reads Collection schemas before mapping items, validates field types and required fields, and detects schema changes.
Collection itemsStore CMS content such as blog posts, products, events, or locations.Salesforce, Shopify, NetSuite, search indexes, content systemsMartini maps fields and references, uses upsert or stable identifiers where supported, processes pages or batches, and separates validation failures from transient errors.
PagesRetrieve or manage supported Webflow page data and coordinate page-related publishing workflows.Content systems, search platforms, approval systemsMartini calls supported page endpoints, applies publication rules, and records the response and workflow correlation identifier.
AssetsManage or reference media files associated with Webflow sites or workspaces.Digital asset platforms, commerce systems, content systemsMartini maps asset identifiers and metadata, transfers files only when required, and handles URL lifetime, access, and file-size considerations.
Forms and form submissionsCapture website forms and the submitted values used for lead, support, or request processing.Salesforce, HubSpot, Zendesk, ServiceNow, JiraMartini receives supported events or retrieves submissions, preserves submission identifiers and timestamps, protects personal data, and applies duplicate and routing rules.

Authentication and security considerations

Authentication choices

Webflow supports OAuth 2.0 for applications accessing multiple users, sites, or workspaces, and bearer API tokens for controlled internal integrations. Select the approach based on the ownership and distribution model of the integration.

Credential protection

  • Store Webflow tokens and OAuth configuration in Martini secrets or environment configuration.
  • Grant only the scopes required for sites, Collections, pages, assets, forms, ecommerce resources, or webhooks.
  • Confirm whether each endpoint requires site-level, workspace-level, or resource-specific authorization.

Inbound webhook security

Protect Martini endpoints receiving Webflow events with authentication, request validation, event deduplication, and controlled logging. Avoid exposing personal form data unnecessarily in workflow logs.

Operational considerations for Webflow integrations

Rate limits and pagination

Confirm current Webflow limits for the account, endpoint, API version, and authentication method. Process list responses page by page, preserve cursor state, control concurrency, and use exponential backoff for transient 429 responses.

Webhook coverage and synchronization

Webflow webhook support is limited to documented event types. Combine event-driven workflows with scheduled REST reads for unsupported changes, and retrieve the current resource when a notification does not contain complete data.

Idempotency and retries

Webhook deliveries may be retried or duplicated. Store a stable event identifier where available, or combine event type, resource identifier, and timestamp. Use upsert behavior and checkpointing to prevent repeated downstream effects.

Schema and publishing controls

Validate Collection field identifiers, types, references, and required fields before writing. Keep draft, approval, and publishing actions explicit, and test mappings after Webflow API or Collection schema changes.

Assets and personal data

Decide whether an integration transfers an asset file, URL, or metadata. Handle file constraints separately from JSON errors, verify URL access requirements, and limit exposure of form submission data in logs.

Why use Martini instead of scripts or point-to-point integrations?

Reusable orchestration

Martini separates Webflow API calls, webhook intake, mappings, business rules, target writes, and error handling into maintainable workflows and reusable integration assets.

Event and batch flexibility

Webflow events can trigger real-time processing, while scheduled Martini workflows can handle pagination, reconciliation, and resources without sufficient webhook coverage. Supported CMS bulk operations can be combined with controlled retries and checkpointing.

Reliable enterprise processing

Instead of maintaining isolated scripts, teams can centralize secrets, validation, transformation, idempotency, retry behavior, monitoring, and downstream API orchestration in Martini.

API-led integration

Martini can consume Webflow REST APIs and expose controlled APIs for other applications, allowing Webflow to participate in broader enterprise workflows without requiring a dedicated vendor connector.

Frequently asked questions

How can Webflow be integrated with enterprise systems?

Webflow can be integrated through its Data API v2 REST endpoints, OAuth 2.0, bearer API tokens, selected webhook event notifications, CMS bulk operations, and asset APIs. Enterprise workflows can synchronize Collections, Collection items, forms, submissions, assets, pages, and site data with external applications.

Can Martini integrate with Webflow?

Yes. Martini can consume Webflow REST APIs, receive supported Webflow webhook events through an exposed API, schedule synchronization workflows, map Webflow JSON, and orchestrate calls to downstream applications. No native Martini Webflow connector is documented in the supplied sources.

Do I need a connector to integrate Webflow with Martini?

No. A dedicated Webflow connector is not required. Martini can integrate using Webflow’s confirmed REST APIs, OAuth 2.0 or bearer token authentication, supported webhooks, bulk CMS operations, and asset endpoints.

Is there any extra Lonti cost to integrate Webflow with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Webflow. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Webflow, cloud infrastructure, or other third-party systems depending on subscription, API usage, and deployment model.

Which Webflow integration methods should be used?

Use the Webflow Data API v2 REST API for resource reads and writes, OAuth 2.0 for applications serving multiple users or workspaces, and API tokens for controlled internal integrations. Use webhooks for documented event types, bulk CMS operations for supported batch workloads, and scheduled REST synchronization where webhook coverage is insufficient.

Does Webflow provide webhooks, GraphQL, or SOAP APIs?

Webflow supports webhook notifications for selected event types, not every resource or operation. No current official general-purpose Webflow GraphQL or SOAP API was confirmed in this research, so new integrations should use the REST API and documented webhooks.

How does Martini synchronize Webflow data?

Martini can receive supported webhook events for near-real-time processing or run scheduled workflows that retrieve paginated Webflow data. Workflows can maintain cursors or timestamps where suitable, use bulk CMS operations, checkpoint successful work, and reconcile resources that do not have adequate webhook coverage.

How are Webflow mapping, errors, and duplicates handled?

Martini maps Webflow fields, references, assets, and form values into canonical and target models, while validation and business rules protect required fields and publication state. Workflows can deduplicate events using an event identifier or a composite key, retry transient and rate-limit failures, and route schema, permission, or reference errors for review.

Related Martini documentation

Webflow APIs

Events

Workflows

Security

Operations

Connect Webflow to your enterprise systems

Use Martini to orchestrate Webflow APIs, selected webhook events, CMS synchronization, asset processing, and downstream business workflows with secure configuration, reusable mappings, and operational controls.

EXPLORE MARTINI
BOOK A DEMO