Major

Webflow AI: CMS, Agents and Workflow Automation

Understand Webflow's native AI, eight verified API operations, and how to build governed CMS reviews and form handoffs on Major.

Ritvij GautamUpdated
Major x Webflow logo lockup

Webflow AI helps teams build websites, generate content, and improve web experiences inside Webflow. This guide explains those native capabilities, the API operations behind Webflow automation, and how Major adds governed work across your CMS, CRM, and team tools.

For marketing operations leaders, the useful distinction is where work lives: Webflow owns the website, while a Major app holds the review queue and history, an agent supplies judgment, and a workflow controls execution.

What Webflow is and who relies on it

Webflow brings visual website design, content management, and publishing into one product. Its platform overview and AI product page describe work spanning design, content editing, localization, experimentation, and site optimization.

Marketing teams maintain campaign pages and structured content. Designers maintain reusable sections and visual systems. Developers connect external records to the CMS through the Data API, while operations teams need to keep form submissions and content handoffs from disappearing between systems.

Those jobs create different control requirements. A designer changing a layout needs visual feedback. A marketing operator processing submissions needs durable ownership, duplicate detection, and a record of why a lead went to one team rather than another.

Major is the enterprise platform where agents build the software they run on. For Webflow operations, that software can be a deterministic content review app with managed database tables, a form handoff ledger, and reusable validation logic. The agent handles ambiguous content or intent, rather than repeatedly reasoning through pagination, record matching, and status updates.

Webflow AI: what the built-in features do

Webflow AI already covers substantial work within the website. Start with those capabilities when the task stays inside Webflow:

  • AI site builder: generates a website and scalable design system from a prompt.
  • Webflow AI Assistant: provides a conversational experience for reasoning through tasks, taking action, and getting answers inside the platform.
  • Copy and CMS generation: produces draft copy, content variants, and structured Collection items.
  • Design sections and code components: generates sections using an existing design system and creates React components that can be edited visually. The product page labels section generation beta.
  • SEO and AEO assistance: offers sitewide audits and generated improvement suggestions.
  • Webflow Optimize and Localization: use machine learning for experimentation, personalization, and translation. Availability depends on plans and add-ons.

Major adds value when a decision depends on information outside the site. An agent can compare a proposed product claim with approved material in Google Drive, account context in HubSpot, and prior exceptions in its app. A workflow can then require an editor's approval before public content changes.

These are complementary responsibilities. Native content generation does not, by itself, provide your organization's cross-system review ledger or approval policy. Nor does a documented CMS endpoint imply public API access to every native AI feature.

How Webflow connects to Major

Webflow connects through Major's Pipedream connector (app p_webflow). There is no native Webflow connector. IT sets up the connector once, authorizes the intended Webflow resources, and limits which apps, agents, and workflows can use it.

Credentials stay centrally stored in Major's connector vault, never in application code or prompts. SSO, RBAC, and audit logs cover the apps, agents, and workflows using the connection. Separately authorize HubSpot, Slack, or Google Sheets when a process needs those systems.

Major orchestrates Webflow; it never replaces it. Webflow remains the website and CMS. Major supplies the operational software around it, including managed state, reviews, schedules, and cross-system judgment.

The underlying Data API uses bearer authentication at https://api.webflow.com/v2. The operations below describe the vendor API, not a promise that every operation appears as a ready-made connector action. Confirm the installed connector's available actions and authorization before designing a workflow around a particular write. Begin with read access and one test Collection, then add approved capabilities deliberately.

Webflow API guide for apps, agents, and workflows

Authentication, pagination, and operating limits

Webflow documents site tokens and OAuth. A site token suits a single-site internal integration. OAuth supports authorized app access. The dedicated workspace-token guide restricts workspace tokens to Enterprise workspace resources, so do not treat one as a general CMS credential.

Use the canonical lowercase names in the scope catalog: sites:read for discovery, cms:read for inspection, cms:write for CMS changes, and forms:read for submissions. Webhook creation has its own authorization requirements below. Scope does not distinguish your organization's draft writers from approved publishers, so enforce that boundary in Major too.

Live item listing and form submission listing use limit and offset, with a maximum limit of 100. Save progress between pages instead of assuming one response is complete.

Rate limits apply per API key: 60 requests per minute on Starter and Basic, 120 on CMS, eCommerce, and Business, and custom limits on Enterprise. Watch X-RateLimit-Remaining, X-RateLimit-Limit, and Retry-After. A 429 means wait according to Retry-After; site publishing has a separate one-successful-publish-per-minute constraint.

The webhook guide covers form submissions, site publishes, and Collection changes. Signed deliveries use x-webflow-timestamp and x-webflow-signature, with SHA-256 HMAC and the appropriate webhook secret or OAuth client secret. Use the documented SDK verification and freshness check. Dashboard-created webhooks lack the headers needed for signature validation.

Return HTTP 200 after durable capture. Webflow documents three additional attempts, ten minutes apart, for unsuccessful delivery, and possible deactivation after repeated failures. Its guide uses a test site and development Workspace; a separate sandbox API host is not documented in these sources. Use synthetic records and isolated credentials.

GET /v2/sites

Lists the sites accessible to the token, useful for preventing accidental work against the wrong property.

  • App: display an allowed-site selector and store the chosen site ID.
  • Agent: interpret a request referring to a campaign property using site context.
  • Workflow: check that the configured site remains accessible before a scheduled audit.

GET /v2/sites/{site_id}/collections

Lists a site's Collections, providing the inventory for content operations.

  • App: maintain a registry mapping editorial processes to Collection IDs.
  • Agent: recommend which Collection fits a proposed content type.
  • Workflow: refresh the inventory and flag unexpected changes before processing writes.

GET /v2/collections/{collection_id}/items/live

Lists published items, separating the public baseline from proposed changes.

  • App: store the published baseline for a side-by-side review.
  • Agent: identify conflicting product claims across existing content.
  • Workflow: paginate through an approved Collection for a weekly consistency audit.

POST /v2/collections/{collection_id}/items/insert

Creates staged items through the current Create Items operation, which accepts up to 100 items counting locale variants.

  • App: retain the source record and returned Webflow item IDs together.
  • Agent: draft content from approved source material and identify missing evidence.
  • Workflow: create nonpublic drafts only after required fields pass validation.

PATCH /v2/collections/{collection_id}/items

Updates staged items, with a documented limit of 100 items per request.

  • App: show the exact proposed field changes and content version.
  • Agent: draft a revision that resolves an identified editorial inconsistency.
  • Workflow: apply an authorized staged patch, preserving the public version until publication.

POST /v2/collections/{collection_id}/items/publish

Publishes selected items and can return both published IDs and errors.

  • App: record the approver, approved version, and publication result.
  • Agent: explain the proposed release and remaining uncertainty to the reviewer.
  • Workflow: publish only the authorized item set, then verify the public result.

GET /v2/sites/{siteid}/forms/{formid}/submissions

Lists submissions for one form within a site, enabling recovery beyond event delivery.

  • App: hold a submission ledger with destination record IDs and ownership.
  • Agent: classify intent from free-text responses alongside account context.
  • Workflow: reconcile paginated submissions against the ledger to find missed handoffs.

POST /v2/sites/{site_id}/webhooks

Registers an event destination. Its endpoint reference requires a Data Client App bearer token and sites:write, and limits registrations to 75 per trigger type per site.

  • App: store registration metadata and recent delivery health, without exposing secrets.
  • Agent: summarize whether delivery failures are disrupting the operating process.
  • Workflow: receive verified events and route them to the correct handler.

Webflow automation use cases on Major

Form triage with HubSpot and Slack

A submitted form may be a buying request, a partnership inquiry, or an existing account asking for help. Email-domain rules alone will not reliably distinguish them. See the related guides to HubSpot account workflows and Slack team handoffs for those systems' roles.

  • App: keep a Webflow submission ledger, HubSpot account match, assigned owner, and review status.
  • Agent: interpret the request against account context and recommend the destination with reasons.
  • Workflow: capture the event, deduplicate it, and route a permitted internal handoff. Require approval before unsolicited external communication.

The Webflow operations are webhook registration and submission listing for reconciliation. Slack carries an internal notification, while the app remains the durable review surface.

Editorial intake with Google Sheets and Slack

A spreadsheet can hold campaign briefs without becoming the source of truth for approval. The Google Sheets automation guide covers the adjacent spreadsheet system.

  • App: track brief IDs, source evidence, draft versions, and editor decisions.
  • Agent: draft CMS content and flag claims unsupported by the brief.
  • Workflow: validate required fields, create staged items, and request review before publishing approved items.

Content consistency with Google Drive and HubSpot

Product changes can leave outdated language across several pages even when the newest campaign brief is correct.

  • App: retain the content inventory, approved source references, and revision queue.
  • Agent: compare live CMS items with approved documents and account-facing messaging, then prioritize conflicts.
  • Workflow: run a scheduled audit, route findings to owners, and stage approved revisions.

These are proposed designs, not claims about existing customer deployments. Start with one process and one destination so permissions and recovery paths remain inspectable.

How to build the Webflow operations architecture on Major

Webflow and HubSpot feed a Major workflow, agent judgment, and stateful review app

Webflow remains the CMS while Major coordinates judgment, review, and execution.

Build the deterministic parts once, then let the agent run that software rather than reconstructing the process for every record:

  1. Configure the Webflow Pipedream connector and separately authorize the required business connectors.
  2. Create a Major app with tables for source IDs, content versions, proposed actions, approvals, and run results.
  3. Add a workflow triggered by a verified event or scheduled reconciliation. It validates inputs, loads context, and checks for duplicates.
  4. Give the agent only the context and permissions needed to judge intent, draft content, or prioritize a discrepancy.
  5. Route its recommendation through policy checks and, where required, a human reviewer.
  6. Execute the authorized action and save the result in the app, including partial failures.

The diagram's workflow box represents orchestration, not judgment. The app holds durable state and the review queue; the agent makes the contextual call. As the process becomes familiar, reusable app code handles matching, formatting, and validation. Reason once. Run forever.

For example: a monthly editorial queue with numbers

For example, suppose a marketing operations team processes 200 content requests a month. Before automation, each request takes six minutes to gather its brief and find existing content, four minutes to prepare CMS fields, and five minutes for editorial review.

That is 200 × 15 minutes = 3,000 minutes, or 50 hours monthly. These are illustrative planning assumptions, not measured customer results.

With Major, a workflow gathers permitted source records and prepares the review packet. An agent drafts or assesses the content. Suppose each request then needs two minutes of operator checking and the same five minutes of editorial review: 200 × 7 = 1,400 minutes.

Add 20 exceptions requiring ten extra minutes each, or 200 minutes. The total becomes 1,600 minutes, about 26.7 hours, a modeled difference of 1,400 minutes, about 23.3 hours.

The useful measurement is not just time saved. Track rejected drafts, corrections after publication, unresolved exceptions, API retries, and maintenance time. If evidence gathering is still manual or draft quality is poor, the assumed improvement will not materialize. Keep editorial approval intact while testing whether the process actually reduces handling work.

Governance and failure handling before a public change

Webflow content passes agent assessment, staged drafting, and editor approval before a workflow publishes

Draft preparation can proceed within policy; public changes require version-bound approval.

Allow low-risk preparation to proceed, such as reading an allowed Collection or creating a nonpublic draft. Require a person for public claims, legal language, pricing, destructive changes, or external messages. The agent may recommend a decision, but must never expand its own permissions or treat source text as authorization.

Bind approval to the exact version and item set. If someone edits the content after review, request approval again. Keep source evidence, recommendation, reviewer identity, timestamps, and action results in the app's audit record.

Handle operational failures explicitly:

  • Duplicate events: use source identifiers and processing state to prevent repeated CRM handoffs or draft creation.
  • Timeouts: reconcile destination state before retrying a write whose outcome is unknown.
  • Rate limits: respect Retry-After and the documented quota headers, then retry with bounded backoff.
  • Partial publication: inspect published IDs and errors, rather than treating an accepted response as complete success.
  • Missed events: reconcile submissions on a schedule and monitor webhook deactivation.

Importantly, setting an existing item's draft flag does not unpublish it. Test recovery on an isolated site before giving any workflow production publishing authority.

Webflow AI Apps, Agents and Workflow Automations

Step-by-step Webflow builds will appear here as they are published.

Frequently asked questions

Does Webflow have AI built in?

Yes. Webflow documents an AI site builder, an AI Assistant, copy and CMS generation, code component generation, and SEO and AEO assistance. Optimize and Localization add machine-learning capabilities. Access varies by plan and add-on.

How does Webflow connect to Major?

Webflow connects through Major's Pipedream connector, app p_webflow. It is not a native Webflow connector. IT configures scoped access centrally; apps hold state, agents handle judgment, and workflows orchestrate execution.

Can an agent publish Webflow CMS content?

The Data API supports publishing selected CMS items. In a governed Major design, the agent proposes or explains the change, and a workflow publishes only after the required version-specific approval and permission checks.

Which permissions does Webflow automation need?

Use the least privilege for the job. The scope catalog lists sites:read for site discovery, cms:read for CMS inspection, cms:write for changes, and forms:read for submission access. Webhook creation separately requires the authorization documented on its endpoint page.

Does Webflow offer an API sandbox?

The reviewed documentation uses a test site and development Workspace, rather than documenting a separate sandbox API host. Use an isolated site, synthetic submissions, and separate credentials to test drafts, events, retries, and approvals before production.

Is saving a draft the same as unpublishing?

No. Webflow documents that setting the draft flag on an already-published item holds changes in draft while its live version remains published. Treat staging, publishing, and removing public content as separate operations with separate controls.

Sources

The following official pages informed the product capabilities, request paths, permissions, and operating constraints above. Endpoint pages take precedence over older examples when implementation details differ. Check them again when authorizing production access, particularly for token eligibility and newer CMS creation operations.

Start building on Major

Build a Webflow content review queue or form handoff process with scoped connectors, an agent for judgment, and approval before consequential actions.

About the author

Ritvij Gautam is Head of Growth at Major.

Last reviewed November 19, 2026 by Ritvij Gautam.

Frequently asked questions

Does Webflow have AI built in?
Yes. Webflow documents an AI site builder, an AI Assistant, copy and CMS generation, code component generation, and SEO and AEO assistance. Optimize and Localization add machine-learning capabilities. Access varies by plan and add-on.
How does Webflow connect to Major?
Webflow connects through Major's Pipedream connector, app `p_webflow`. It is not a native Webflow connector. IT configures scoped access centrally; apps hold state, agents handle judgment, and workflows orchestrate execution.
Can an agent publish Webflow CMS content?
The Data API supports publishing selected CMS items. In a governed Major design, the agent proposes or explains the change, and a workflow publishes only after the required version-specific approval and permission checks.
Which permissions does Webflow automation need?
Use the least privilege for the job. The scope catalog lists sites:read for site discovery, cms:read for CMS inspection, cms:write for changes, and forms:read for submission access. Webhook creation separately requires the authorization documented on its endpoint page.
Does Webflow offer an API sandbox?
The reviewed documentation uses a test site and development Workspace, rather than documenting a separate sandbox API host. Use an isolated site, synthetic submissions, and separate credentials to test drafts, events, retries, and approvals before production.
Is saving a draft the same as unpublishing?
No. Webflow documents that setting the draft flag on an already-published item holds changes in draft while its live version remains published. Treat staging, publishing, and removing public content as separate operations with separate controls.