Webflow APIs for AI Agents
Developer ToolsSource ControlMixed ProvenanceBearer tokenOAuth 2.0Agent Ready
For Agents
APIs3 in catalogue
Endpoints224 indexed
AuthBearer token / OAuth 2.0
ProvenanceMixed provenance
An agent can list and inspect Webflow sites, read and update CMS collections, manage assets and custom domains, publish sites, and register webhooks across the Webflow API and Webflow Data API, and separately run Lucidtech document-processing operations over datasets and documents.
Webflow pairs a visual site builder with a structured CMS, so its APIs expose both site infrastructure (domains, publishing, webhooks) and content collections through one bearer token, letting an agent read and change a live site without touching the design editor.
Use for: Managing Webflow sites, CMS collections, assets, domains, publishing, and webhooks, plus Lucidtech document processing
Not supported: payment processing, email or messaging, crm records, visual design editing, real-time streaming
Credentials: The two Webflow APIs both use a Bearer token, while the Lucidtech API uses its own OAuth2 client-credentials flow, so no single credential covers all three.
Across 3 Webflow APIs: 2 vendor-official, 1 third-party, all indexed by Jentic and kept validated and agent-ready.
Webflow is a visual website builder and content management platform. Its APIs let agents manage sites, collections, assets, custom domains, form submissions, and webhooks, and publish live changes to Webflow-hosted sites programmatically. This vendor group also includes a third-party Lucidtech document-processing API covering datasets, documents, and models.
Webflow API Catalog
3 APIs across 1 product group.
Which Webflow API should I use?
| I want to... | Use |
|---|---|
| Read and update CMS collections, assets, and form submissions with the current v2 surface | Webflow API |
| Publish sites, list domains, and register webhooks on the stable v1 surface | Webflow Data API |
| Process documents, datasets, and models for extraction | Lucidtech API |
Install Jentic One Beta
Connect the Webflow APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webflow APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwebflow.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwebflow.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “update webflow cms content and publish the site”.
What AI Agents Can Do with Webflow
Each workflow spans multiple Webflow APIs. Jentic routes each operation to the right API automatically.
Publish content after a CMS update
Update collection items through the Webflow API, then publish the affected site through the Webflow Data API so the changes go live.
Example prompt:
Update the collection item via the Webflow API, then call POST /sites/{site_id}/publish on the Webflow Data API
APIs used
Webflow API + Webflow Data API
Inspect a site and register a webhook
List and inspect a site through the Webflow API, then create a webhook on it through the Webflow Data API to receive future change events.
Example prompt:
Read the site with GET /sites/{site_id}, then create a webhook via POST /sites/{site_id}/webhooks on the Webflow Data API
APIs used
Webflow API + Webflow Data API
Audit domains and assets before a launch
Retrieve custom domains and asset folders through the Webflow API and confirm domain status through the Webflow Data API before publishing.
Example prompt:
List custom domains and assets via the Webflow API, confirm domains with GET /sites/{site_id}/domains on the Webflow Data API, then publish
APIs used
Webflow API + Webflow Data API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means learning a Webflow Bearer token, a separate Lucidtech OAuth2 client-credentials flow, and several base hosts, then handling responses yourself. With Jentic you install once, add each API from the Jentic directory, store each credential once, and your agent calls them.
Permission scoping
Webflow puts the site id in the URL path such as /sites/{site_id}, so a rule can pin an agent to one site, and Lucidtech uses OAuth2 scopes you can hold to read-only. Your own Jentic One rules decide which operations and credentials the agent may use, so publishing, deletes, and write scopes are excluded unless you add them.
Credential isolation
Each credential, the Webflow token and the Lucidtech client credentials, is stored once and encrypted by your own Jentic One instance and injected at execution time. Secrets never enter the agent's prompt, logs, or context.
Intent-based discovery
An agent searches Jentic by intent such as 'list sites', 'publish a site', or 'process a document', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Webflow APIs through Jentic.
Do all of these APIs use the same credential?
No. The Webflow API and the Webflow Data API both authenticate with a Webflow Bearer token, but the Lucidtech API uses a separate OAuth2 client-credentials flow. You store each credential separately in your Jentic One instance.
What is the difference between the Webflow API and the Webflow Data API?
The Webflow API is the broader v2 surface with 108 endpoints covering collections, asset folders, assets, and form submissions. The Webflow Data API is a focused 35-endpoint set centered on sites, publishing, domains, and webhooks. They overlap on site operations, so pick the surface that matches the resource you need.
Why is Lucidtech grouped under Webflow?
Lucidtech is a third-party document-processing API that appears in this vendor group but is not a Webflow product. Treat it as a separate service for datasets, documents, and models, and do not expect it to share Webflow credentials or resources.
Can an agent publish a live Webflow site?
Yes. The Webflow Data API exposes POST /sites/{site_id}/publish, so an agent can publish a site after making content or configuration changes. Publishing is a state-changing operation, so scope your Jentic One rules to allow it only when intended.
Can an agent read and edit CMS content?
Yes. The Webflow API covers collections and their items, so an agent can read, create, and update structured content. Combine it with the Webflow Data API when you also need to publish the result.
Are these APIs read-only?
No. Alongside read operations, they include state-changing calls such as updating or deleting a site, publishing, and creating webhooks. You choose which operations your agent may call in your own Jentic One rules, so write and destructive actions are excluded unless you add them.
If you need a different Developer Tools vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.