Integration reference

Webflow Trigger and Action reference

Start Workflows from Webflow site, CMS, form, ecommerce, and comment events, then manage content and commerce through the Data API.

Authentication

Connect each customer's Webflow account through OAuth. During authorization, the customer can grant access to a workspace or selected sites; FastHook stores the access token encrypted.

• Trigger account type: oauth2; reconnect by oauth.
• Action connection type: oauth2; available modes: Connected Webflow account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: authorized_user:read, sites:read, sites:write, cms:read, cms:write, forms:read, forms:write, pages:read, ecommerce:read, ecommerce:write, comments:read.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Webflow as a Trigger

The current provider manifest contains 16 available Trigger definitions. Representative definitions include:

• New Form Submission
• Site Published
• Collection Item Updated
• New Order

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Webflow Actions

The current Action manifest contains 24 operations. Representative Actions include:

• Publish Site
• Create Collection Item
• List Form Submissions
• Fulfill Order

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

1. Create a Source using a Webflow Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required Webflow Action and select the connected account.
4. Map Trigger or earlier-Step data into the Action fields with the field picker.
5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Webflow.

Troubleshooting Webflow

The account is missing or cannot be selected

Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.

A resource picker is empty

Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.

The editor asks for additional scopes

Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.

An active Workflow returns 401, 403, or a permission error

Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.

The provider returns 429 or a temporary 5xx

Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

• Choose one to five sites per Source. FastHook creates one Webflow webhook for each selected site and event and removes unused webhooks automatically.
• FastHook verifies x-webflow-signature against the exact request body and rejects webhook timestamps outside a five-minute window before storing an event.
• CMS item bodies use Webflow's fieldData JSON. Collection fields differ by site, so use List Collections and List Collection Items to inspect IDs and values before writing content.
• Webflow permissions and plan features determine whether publishing, ecommerce, forms, localization, and comments are available on a selected site.
• Custom API Request is restricted to https://api.webflow.com/v2 and cannot override the host or authorization header.
• Action and Trigger output schemas are extracted from the pinned official Webflow OpenAPI specification. Event payloads stay open where Webflow varies fields by event and site configuration.

Next

• Explore Webflow integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations