Set Up Real-Time Data Feed Max on Webflow

Expose your Webflow CMS collections or Ecommerce products as a JSON feed

Pro Plan

What Your Feed Should Look Like

Real-Time Data Feed Max accepts any public URL returning JSON or plain text. The AI reads whatever you give it — products, services, bookable slots, property listings, menus, opening hours, anything — and uses it to answer visitor questions. There is no required shape or field name.

The one exception is Dynamic Product Cards. If you want matching items to render as visual cards in the chat, use these specific field names: name, price, description, image_url, button_link, in_stock.

Example — products (triggers Dynamic Product Cards)

{
  "products": [
    {
      "name": "Wireless Headphones Pro",
      "price": "$149.99",
      "description": "Premium over-ear wireless headphones with ANC.",
      "image_url": "https://example.com/images/headphones.jpg",
      "button_link": "https://example.com/products/headphones",
      "in_stock": true
    }
  ]
}

Example — services (any shape works)

{
  "services": [
    {
      "service": "Deep tissue massage",
      "duration_minutes": 60,
      "price_from": "$95",
      "therapists_available": ["Anna", "Mark"],
      "booking_link": "https://example.com/book/deep-tissue"
    },
    {
      "service": "Haircut & style",
      "duration_minutes": 45,
      "price_from": "$55",
      "booking_link": "https://example.com/book/haircut"
    }
  ]
}

Example — plain text (works too)

Opening hours: Mon-Fri 9-6, Sat 10-4, closed Sunday.
Delivery: Free over $30, minimum order $15, within 5 miles.
Lunch specials (weekdays only):
- Margherita pizza $12
- Caesar salad $9
- Soup of the day $7

Rule of thumb: Use descriptive field names the AI can interpret (service, duration, price, location, etc.). If Dynamic Product Cards make sense for your business, follow the exact field names above. If they don't, use whatever shape fits your data — the AI still searches it and answers questions correctly.

How Webflow Differs

Webflow's CMS Collections and Ecommerce products are served as rendered HTML to visitors — there is no public JSON endpoint out of the box. Webflow's official CMS API requires a bearer token, so you'll need a small proxy that holds the token and returns a public JSON feed.

Setup via a Proxy

Generate a Webflow API token Webflow admin → Site settings → Apps & integrations → Generate API token. Give it read scope for CMS (and Ecommerce if applicable).

Note your Site ID and Collection ID(s) Both are visible in Webflow admin → Designer → CMS Collections → collection settings. You can also list them via the API: GET /v2/sites and /v2/collections.

Deploy a small proxy Cloudflare Worker (free tier is fine), Vercel function, or Netlify function. It calls the Webflow API with the token, reshapes the response, and returns public JSON.

Paste the proxy URL into Real-Time Data Feed Max The Webflow token stays secret inside the proxy.

CMS Collection items

GET https://api.webflow.com/v2/collections/{collection_id}/items?limit=100
Authorization: Bearer YOUR_WEBFLOW_TOKEN

Webflow Ecommerce products

GET https://api.webflow.com/v2/sites/{site_id}/products?limit=100
Authorization: Bearer YOUR_WEBFLOW_TOKEN

Example Cloudflare Worker proxy

export default {
  async fetch() {
    const r = await fetch(
      'https://api.webflow.com/v2/collections/YOUR_COLLECTION_ID/items?limit=100',
      { headers: { 'Authorization': 'Bearer ' + YOUR_TOKEN } }
    );
    const data = await r.json();
    const products = data.items.map(item => ({
      name:        item.fieldData.name,
      description: item.fieldData['short-description'] || '',
      image_url:   item.fieldData['main-image']?.url,
      button_link: `https://your-site.com/items/${item.fieldData.slug}`,
    }));
    return new Response(JSON.stringify({ products }), {
      headers: { 'Content-Type': 'application/json' },
    });
  }
};

Tip: Webflow uses slug-style field IDs — "short-description", "main-image", "product-name" — so your transform code needs to reference the exact field IDs from your collection. Check them under CMS → collection → field settings.

Rate limits: Webflow API has a 60 requests/minute limit per site. If your collection has more than 100 items, your proxy will need to paginate and cache results — don't re-fetch on every chatbot request.

Troubleshooting

I see a password page instead of JSON

Your site is in maintenance, staging, or password-protected mode. Real-Time Data Feed Max needs a fully public URL.

Real-Time Data Feed Max says the feed failed

Open the URL in a private browser window. If you don't see JSON, the URL is wrong or the endpoint is down. If you see JSON but we still fail, the response may be missing a Content-Type: application/json header or exceeding the 10,000,000 character limit.

Product cards don't render

Dynamic Product Cards require specific field names (name, price, image_url, button_link, in_stock). If your platform uses different names, reshape the response in a small custom script before exposing it.

Data looks wrong or outdated

The feed auto-refreshes every 24 hours. For immediate updates, click Refresh Now in Real-Time Data Feed Max. For live fields (price, stock), the AI pulls fresh data on every message — so the 24h cycle only affects which items are known, not their current state.

Feed size exceeded

Real-Time Data Feed Max accepts up to 10,000,000 characters (~25,000 items). If you exceed that, trim fields (skip long HTML descriptions), split your catalog, or use the standard Real-Time Data Feed alongside for secondary data.

Still stuck? Start with the simplest option for your platform and verify the URL works in a browser before pasting it into Real-Time Data Feed Max. You can always upgrade to a more advanced option later — only the URL field changes on our side.

Documentation