Blaze

The Webflow CMS stores, structures, and renders blog content, but it does not write it. Teams publishing SEO articles every week still need a separate tool to draft, edit, and schedule that content. Blaze handles that side of the workflow. Zapier carries the content across, because neither platform ships a native connection to the other.

Publishing a Blaze document to a Zap you picked in that document's Export menu tells Zapier to create a live item in the Webflow CMS. Webflow form submissions can travel the other way and start new article generation inside Blaze. Both directions run through Zapier rather than a direct link between the two products.

This setup fits marketing agencies running client blogs. If you publish weekly SEO posts solo or manage an in-house content calendar, you get the same benefit. Those are the same teams that keep their marketing site and blog on Webflow.

How to integrate Blaze with Webflow

What is Blaze? Blaze is an AI marketing platform, published by Almanac, Inc., that drafts content in a brand's voice and then schedules and posts it to connected channels. It writes blog posts, social posts, email newsletters, landing page copy, and paid ad copy. A Brand Kit, which Blaze assembles from your website, your past content, and answers to a short set of questions, keeps tone, vocabulary, and visual style consistent across everything it produces.

You pair the two platforms so Blaze is the writing layer and Webflow runs the published site. On the Webflow side, the Webflow MCP server is now the shortest route from a finished draft to a reviewed, published CMS item, because an agent can create the item, run a content audit against it, and leave the change in your site activity log. Getting the draft out of Blaze in the first place still happens through manual export, Zapier, or custom code against the Webflow Data API. Blaze publishes directly to WordPress, Wix, and GoHighLevel, not to Webflow, and it has no app in the Webflow Marketplace.

Four methods cover the ground between the two products:

• Manual export: moves a finished Blaze document into the Webflow CMS by hand, with no extra accounts and no code.
• Zapier: sends a Blaze document to Webflow CMS actions when you publish it to a Zap, without writing code.
• Webflow Data API: gives you full control over field mapping, staging, and batch publishing, and needs server-side development.
• Webflow MCP server: hands the CMS write, the review pass, and the publish step to an agent working inside your existing Webflow roles.

Most teams combine two of these: one route to get content out of Blaze, and one route to review it before it reaches the live site.

Export Blaze content into the Webflow CMS

You can export any Blaze document without touching an API. The Blaze Document Editor includes a Copy Text to Clipboard option, and blog documents download as HTML, PDF, or Markdown. This route fits a one-off post or a back catalog you want a person to read before it goes live.

• File download: the Download button on a blog document produces the same content as an HTML, PDF, or Markdown file.
• Clipboard copy: Copy Text to Clipboard lifts the body text so you can paste it straight into a Webflow rich text field.
• Media handling: Download Post Media Only pulls the images out as a zip, because the text export does not carry them into Webflow for you.
• Legacy surface: Blaze files these document export articles under Blaze Copilot, which its help center labels as legacy, so check the buttons against your own workspace before you script anything around them.

Which of these you reach for depends on the volume: one post moves fastest by hand, and an archive is worth batching.

Paste or upload individual posts

Single posts move fastest through copy and paste. Blaze's blog post guide covers the export options in the document view.

To move one post:

1. In Blaze, open the document. Use Share > Download to export HTML or Markdown, or use Copy Text to Clipboard.
2. In Webflow, open the CMS panel and create a new item in your blog Collection.
3. Paste the content into the appropriate Collection fields and publish.

Blaze's scheduling guide documents a Copy doc content option that copies a full document to your clipboard, which is the faster path when the document is already finished.

Import posts in bulk with a CSV file

For migrations or article batches, bulk import beats item-by-item entry. The CMS accepts CSV imports up to 4 MB per file.

To import a batch:

1. Assemble your exported Blaze articles into a CSV with one column per Collection field.
2. Open the CMS panel, choose the Collection, and click Import.
3. Pick an import mode. "Link and update matching items and import remaining as new" refreshes existing entries. "Import all as new items" creates fresh ones.
4. Run the import.

Blaze exports HTML, Markdown, and PDF rather than CSV. Budget a few minutes to reshape the files before importing.

Embed exported HTML with a Code Embed element

Blaze's landing page copy documents export as HTML files. You can paste that markup into a Code Embed element on a static Webflow page. Each Code Embed element holds up to 50,000 characters, a limit that cannot be raised. You need a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan.

To embed exported copy:

1. In Blaze, open the landing page document and click Export to file, then choose HTML.
2. In Webflow, open the Add panel and drag a Code Embed element onto the canvas.
3. Paste the HTML and publish the site.

For longer exports, split or minify the markup, place the hosted HTML in an iframe, or host the JavaScript externally and load it with a script tag through custom code in the head and body tags. Fetching hosted HTML still requires JavaScript that inserts it into the page.

Connect Blaze and Webflow with Zapier

Zapier links Blaze's publish trigger to Webflow CMS actions without any code on your side, and it is the only automated route between the two products. Zapier lists the tool as Blaze.ai. You need a workspace API key from Blaze and a connected Webflow account. One point decides how you design everything downstream: the trigger does not fire on its own when a document publishes. You open the finished document, expand Share, click Export, pick the Zap by name, and click Publish, which is why Zapier asks you to name the Zap when you build it.

To set up the integration:

1. In Blaze, open the Integrations page, open the Zapier integration card, and copy your workspace API key. The key belongs to the workspace rather than to you.
2. In Zapier, create a Zap with the Blaze.ai trigger. Zapier's directory calls it Scheduled Post and Blaze's own guide calls it Publish Doc, and both describe the same trigger, which fires by webhook rather than on a polling interval.
3. Give the Zap a name you will recognize, because that name is what you select from the document's Export menu in Blaze.
4. Add a Webflow action such as Create Live Item, connect your Webflow account, choose the site and Collection, map the Blaze fields, then test the Zap and turn it on.

The pairing supports automation in both directions:

• Blaze to Webflow: the Scheduled Post trigger can feed Webflow's Create Item, Create Live Item, Update Item, or Update Live Item actions.
• Webflow to Blaze: Webflow's New Form Submission trigger can feed Blaze's Brainstorm Ideas, Generate an Article, Generate Outline, or Turn Into actions.
• Lookups: Zapier's Find Item and Find Live Item searches locate an existing CMS entry before an update overwrites it.
• Field limits: reference and multi-reference fields do not map, and a video URL written through the API arrives blank until someone opens the item and clicks into the video field and back out.

Both of those last two constraints come from Webflow's own note that Zapier cannot map reference fields, so budget a manual pass on any Collection that uses them. A ready-made Zap template pairs the Blaze trigger with Create Live Item if you would rather not build the Zap from scratch.

Build with the Webflow Data API and Blaze exports

Custom builds run in one direction. You bring Blaze content in through export or Zapier, then write it to your site with server-side code. Blaze publishes no public developer API: its workspace API key authenticates the Zapier integration and nothing else, and it documents no webhooks of its own. This path suits developers who want staged review, custom field mapping, or batch publishing beyond what Zapier handles.

• CMS endpoints: the Webflow CMS API covers Collections and items, with JavaScript and Python SDKs.
• Events: Webflow webhooks fire on events such as collection_item_created and form_submission, with a limit of 75 registrations per trigger type per site.
• Blaze side: the Zapier connection is the only documented programmatic surface Blaze exposes, so anything the Zap cannot carry has to move as a file.
• Credentials: CMS writes require the CMS:write scope and a bearer token, and site tokens expire after 365 consecutive days of inactivity.

Because the Blaze side is closed, treat the Webflow half as the part you control and the export as the contract between them.

Push exported Blaze articles with the CMS API

A publishing script takes exported Blaze HTML or Markdown and creates CMS items directly.

To publish content through the API:

1. List your Collections with GET https://api.webflow.com/v2/sites/{site_id}/collections to find the target Collection ID.
2. Create a draft with POST https://api.webflow.com/v2/collections/{collection_id}/items, or create and publish in one call with POST https://api.webflow.com/v2/collections/{collection_id}/items/live.
3. For batches, send up to 100 items at once with POST https://api.webflow.com/v2/collections/{collection_id}/items/bulk.
4. Push staged drafts live with POST https://api.webflow.com/v2/collections/{collection_id}/items/publish.

Staged items let an editor review Blaze output inside Webflow before anything reaches the live site.

Upload Blaze images with the Assets API

Blaze exports a post's images as a separate zip rather than embedding them in the text export, so images take their own trip through the Assets API. Uploading takes two requests, then one CMS update.

To attach an image:

1. Request an upload with POST https://api.webflow.com/v2/sites/{site_id}/assets; the response returns an uploadUrl and uploadDetails.
2. Send the file to the returned Amazon S3 uploadUrl and pass uploadDetails as headers.
3. Reference the asset ID in the item's image field when you create or update the CMS item.

The image field on the item then points at the uploaded asset. Uploading an asset needs the assets:write scope, which is separate from the CMS scope. If you would rather not write any of this yourself, the CMS API guide walks the same path end to end.

Review and publish Blaze drafts with the Webflow MCP server

The MCP server is the answer to the question an AI writing tool creates rather than solves: who reads the draft before it is live. It connects an agent in Claude, ChatGPT, Cursor, or a similar client to your Webflow project, and the agent works inside the Webflow roles and permissions you already have, so it can do what you can do and nothing more.

Against a Blaze workflow it covers four jobs:

• Write the item: the agent creates Collection items from an exported Blaze document, applies bulk updates, and publishes or unpublishes them.
• Audit the copy: a content audit scans for broken links, missing alt text, and outdated information across pages and CMS items before anything ships.
• Set the rules: per-site Agent Instructions carry your editorial rules, and they can reference the site's own Collections, locales, and components.
• Keep the receipts: every change an agent makes lands in the site activity log, which is what makes an AI-written post reviewable after the fact.

Two limits matter for a content pipeline: the server cannot create new localized CMS items, though it can read and update existing ones, and each authorization reaches a single workspace at a time. Neither blocks an English-language blog pipeline, and both change the plan if you run one site per client brand.

What you can build with the Blaze Webflow integration

Pairing Blaze with Webflow lets you move AI-drafted content onto a live site without retyping any of it, provided a person still decides when each piece goes.

• One-click blog handoff: Export a finished Blaze doc to the Zap and it lands as a live item in your blog Collection, wherever that Collection is bound on the site. The click is the approval step, which is a feature rather than a gap.
• Form-to-draft content engine: A Webflow form submission triggers Blaze's Generate an Article action with the form data as the prompt. A consultant's "request a topic" form can start a draft the moment a lead submits it.
• Content refresh workflow: Blaze's Turn Into action reworks an existing article into a new format, and Zapier's Update Item action overwrites the matching CMS entry, so older posts get fresh copy without manual re-entry.
• Bulk blog migration: Blaze articles reshaped into a CSV load straight into a Collection, up to 4 MB per file. A site consolidating a large archive from another platform can import it in one pass.

See how the same trigger and action pattern scales past one tool in this marketing automation hub build.

One cost is worth naming before you build any of this. Blaze's AI Terms state that the input you give the AI and the output it returns are both your Customer Data and that you are solely responsible for them, and the same document says Almanac does not train its models on that data. Blaze also publishes follower growth, engagement, and ad return multiples on its marketing site with no stated methodology, so treat those as advertising rather than as a forecast for your own site. The reviewable version of this pipeline is the one where a person or a logged agent reads the draft in the CMS before it publishes.