Skip to main content
VeluraHQ’s CMS integrations let you publish content without leaving your workflow. Once connected, a publish block in any workflow or Sheet column can push an approved draft directly to WordPress or Webflow — with your fields mapped, media uploaded, and draft-or-live status set by your review gates. No copy-pasting, no CMS tab switching, no manual reformatting.

​
WordPress integration

1

Open the integration settings

Go to Settings > Integrations > WordPress in your workspace.
2

Enter your site URL

Type your WordPress site URL (e.g., https://yoursite.com). VeluraHQ uses the WordPress REST API, so your site must be running WordPress 5.6 or later.
3

Generate an Application Password

In your WordPress admin, navigate to Users > Profile > Application Passwords. Enter a name for the application (e.g., “VeluraHQ”) and click Add New Application Password. Copy the generated password.
4

Paste your credentials

Enter your WordPress username and the application password into VeluraHQ.
5

Connect

Click Connect. VeluraHQ will verify access by making a test request to your site.
6

Map your fields

In your workflow’s publish block, map the VeluraHQ output fields to your WordPress content structure: title, body, slug, categories, tags, featured image, and any custom fields you use.

​
Webflow integration

1

Open the integration settings

Go to Settings > Integrations > Webflow in your workspace.
2

Connect with Webflow

Click Connect with Webflow and complete the OAuth authorization flow. You’ll be redirected back to VeluraHQ automatically.
3

Select your site and collection

Choose the Webflow site you want to publish to, then select the CMS collection that will receive the content (e.g., your Blog Posts or Articles collection).
4

Map your fields

In your workflow’s publish block, map VeluraHQ output fields to the corresponding Webflow CMS collection fields — name, rich text body, slug, and any custom fields in your collection schema.

​
Draft-first publishing

All CMS publishes from VeluraHQ default to draft status. Nothing goes live until a human reviewer approves the draft and explicitly triggers publishing. Drafts appear in your WordPress or Webflow CMS where your editorial team can review them using the native CMS interface before promoting to production. This keeps staging and production clearly separated, regardless of how many rows are running in parallel.
You can override the draft default in the publish block configuration and set it to publish live directly. This is useful for high-volume programmatic content — like location pages or product descriptions — after your team has validated the workflow quality and output standards. Use this setting with care for editorial content.

​
Field mapping

In the publish block configuration, map your workflow output variables to the right CMS fields for your platform: Field mapping is saved per workflow, so once configured you don’t need to re-map fields on subsequent runs.

​
Publishing at scale via Sheets

When running bulk operations in Sheets, add a CMS Output column to your Sheet and select WordPress or Webflow as the destination. Approved rows publish in batch. Rows in a pending review state stay in draft until a reviewer approves them — the Sheet reflects each row’s publish status in real time so you always know what’s live and what’s waiting.
The WordPress REST API and Webflow API have rate limits that vary by plan. For batches over 100 rows, VeluraHQ automatically throttles publish requests to stay within those limits and avoid errors. For very large batches (500+ rows), schedule runs during off-peak hours to ensure smooth throughput and avoid any risk of temporary API blocks from your CMS provider.