Pull from Webflow
Webflow doesn’t yet have a native Parabola pull step. Instead, use Parabola’s Pull from an API step pointed at the Webflow Data API. Authentication and pagination are straightforward once you generate a site token. Webflow’s full API reference lives here.How to authenticate
Webflow uses bearer-token authentication via a site token (sometimes called a site API token).Generate a site token in Webflow
- Open the site you want to connect in Webflow.
- Go to Site settings → Apps & Integrations → API access.
- Click Generate API token, give it a name and the scopes you need (for CMS reads, enable CMS: read), then copy the token. Webflow’s instructions are here.
Pulling CMS collection items
The most common Webflow pull is a list of items in a CMS collection. Use the List Collection Items endpoint::collection_id with the ID of the collection you want. You can find collection IDs in the Webflow Designer at the top of the settings panel for that collection:
offset and limit to 100, and set the number of pages to fetch high enough to cover your collection (each page is 100 items).
To skip the manual setup, copy this snippet and paste it anywhere in any flow to drop in a step that’s mostly pre-configured for collection item pulls: parabola:cb:be322aeb-6ef6-4eed-9153-aec3d82cb336
The Pull from an API step also lets you keep specific columns and rename them inside the step, so you don’t have to clean the response in a separate step.
Available data
Webflow’s Data API exposes most of what’s in your site. The endpoints operators most often pull:- CMS collection items — items in a collection (blog posts, products, team members, case studies) with all field values, slugs, statuses, and timestamps. The most common Webflow pull.
- CMS collections — collection schemas, useful for discovering field names and IDs before pulling items.
- Sites — site metadata including domains, last published date, and workspace.
- Form submissions — submissions captured by Webflow native forms, with field values, submission timestamps, and form IDs.
- Ecommerce orders — orders, products, SKUs, customers, and inventory for sites running Webflow Ecommerce.
- Pages — published page metadata for sitemap or auditing flows.
Common use cases
- Sync CMS content to a spreadsheet for review: Pull blog posts, case studies, or product items from Webflow and drop them into Google Drive or Smartsheet so marketing can audit metadata, tags, and statuses without poking around in the Designer.
- Push form submissions to your CRM: Pull Webflow form submissions and route them into HubSpot or Salesforce, enriching with UTM parameters and routing rules along the way.
- Add new leads to email lists: Send Webflow newsletter signups into Mailchimp or Klaviyo audiences automatically.
- Reconcile Webflow Ecommerce orders: Pull orders, transactions, and inventory from Webflow alongside Stripe payouts and push the result into NetSuite or QuickBooks Online for clean revenue and fee reporting.
- Update Webflow CMS from external data: Pair Pull from an API with Send to an API to refresh CMS items based on data in Airtable, Google Drive, or a database like Postgres or BigQuery.
- Build a marketing dashboard: Combine Webflow form submissions with Google Analytics and ad spend from Facebook Ads to track CAC and conversion by landing page.
Tips for using Parabola with Webflow
- Use the v2 API. All examples here use
api.webflow.com/v2/.... The v1 API is deprecated and being retired; new flows should target v2. - Get the right scopes on your site token. A token without
CMS: readreturns 401s on collection endpoints. If you also want to write back, addCMS: writeand use Send to an API. - Set offset and limit to 100 for CMS pulls. That’s the page size Webflow expects. Set the pages-to-fetch high enough to cover your collection — each page is 100 items.
- Pull collections first, then items. Hitting
/v2/sites/:site_id/collectionsgives you collection IDs and field schemas, which is faster than hunting through the Designer. - Match cadence to use case. Hourly for form-submission routing, daily for content audits, weekly for ecommerce reconciliation. The same step can run on different schedules across forks of a flow.
- Watch for rich text fields. CMS items with rich text return HTML strings that may contain commas and quotes. Use Parabola’s text steps to clean them before joining or exporting.
FAQ
Does Parabola have a native Pull from Webflow step?
Not yet. Use the Pull from an API step with bearer-token auth pointed at the Webflow Data API. Authentication and pagination are straightforward.Can I update Webflow CMS items from Parabola?
Yes. Use a Send to an API step pointed at the relevant Webflow endpoint (for example,PATCH /v2/collections/:collection_id/items/:item_id) with a site token that has CMS: write scope. Each row in your data becomes one API call.
Where do I find a collection ID?
In the Webflow Designer, open the collection’s settings panel — the collection ID sits at the top.Does Parabola support Webflow webhooks?
Yes, via the webhook trigger on a separate flow. Point a Webflow webhook (form submission, CMS item published, ecommerce order placed) at your Parabola webhook URL, and the receiving flow will run on each event.What’s the page size for Webflow collection items?
100 per page. Set bothlimit and offset to 100 in the Pull from an API step, and increase the pages-to-fetch value until you’re getting the full collection back.
With Webflow and Parabola connected, the manual exports and copy-paste workflows your team uses to keep CMS, CRM, and analytics in sync run automatically on a schedule.