Azwedo

Starting a Webflow site from a blank canvas means wireframing page structures by hand. You source icons file by file and write every headline yourself. Each of those tasks widens the gap between kickoff and publish.

Azwedo narrows that gap with four apps on the Webflow Marketplace: icon libraries, AI copywriting, prebuilt components, and in-place SVG editing. All four carry the Approved by Webflow review label and install in a few clicks.

Two other parts of the Azwedo lineup have changed recently. Modulify has become a standalone site builder that no longer exports into Webflow, and the Cllouda file hosting API is no longer reachable. Both are covered below, along with what to use in their place.

How to integrate Azwedo with Webflow

What is Azwedo? Azwedo is a Kosovo-based design and software company that sells branding and web design services alongside a set of Webflow apps. Its four Webflow apps are Ikonik, Text Wizard AI, Modulo, and SVGFlow, and they are the part of Azwedo that still plugs directly into Webflow today. Which one you reach for depends on where you are in the build.

Two things a reader may have seen written about Azwedo are no longer true, and we checked both against the vendor rather than repeating them. Modulify, once an AI tool whose exports you pasted into Webflow, is now an AI website builder with its own hosting and CMS: its own documentation states that it does not export into Webflow, and its Webflow-facing offer is a migration program that rebuilds sites away from Webflow. We keep a separate Modulify integration page for readers looking specifically at that product. Cllouda, Azwedo's file hosting API, has been dropped from Azwedo's own products page, its API host no longer resolves in DNS, and its published SDK package is no longer on npm. Its documentation is still online with no shutdown notice, which is exactly what makes it easy to follow into a dead end.

That leaves three ways to work, moving from an AI agent driving Webflow to a developer path through the API.

• The Webflow MCP server lets an AI agent write copy, build pages, and manage assets in your site directly, which covers much of what Azwedo's AI tooling was reached for.
• The Azwedo apps on the Webflow Marketplace handle icons, AI text, components, and SVG editing without writing code.
• Custom code and the API place markup generated anywhere into a page and handle asset hosting outside Webflow.

Most builds combine the first two, with the third reserved for the cases where a designer genuinely needs to drop in code or point CMS items at files held elsewhere.

Generate site content with the Webflow MCP server

The job Azwedo's AI apps do in one panel is now something an agent can do across your whole site. The Webflow MCP server connects tools such as Claude Code and Cursor to your Webflow projects, so you can describe the page or the copy you want in plain language and let the agent build it. Every agent works inside your existing Webflow permissions and roles, and the changes it makes land in your site's activity log.

We built this into Webflow because the alternative, writing API calls and managing tokens for every small content change, is not work a marketing team should be doing. The free Starter plan includes it, so you can try it before paying for anything.

• Writing and rewriting copy: Ask the agent to draft headlines, feature descriptions, or CMS entries in a given tone, then revise them in place without leaving your editor.
• Building pages and components: Create responsive layouts, elements, styles, and components with props and variants, rather than assembling them by hand.
• Managing assets: List, organize, update, and delete assets and folders, and run compression jobs against images already in your site.
• Governing what agents may do: Per-site Agent Instructions shape how an agent works on a given site, and permissions carry over from the roles you already assigned.

Some things stay manual: the server cannot build Webflow Interactions, and it cannot create new localized CMS items. The getting started guide walks through authorizing a workspace and connecting your first client.

Install the Azwedo apps from the Marketplace

The Webflow Marketplace lists Azwedo's four apps separately, each with its own install flow. All four now appear under the Modulify.ai developer name, which is the same company operating a renamed developer account, and all four carry the Approved by Webflow label. Ikonik covers icons, Text Wizard AI handles AI text generation, Modulo supplies prebuilt components, and SVGFlow edits SVG icons in place.

To install one:

1. Open the app's Marketplace listing, for example Ikonik.
2. Click Install and authorize it for the site you want it on.
3. Open the app inside Webflow to browse icons, generate text, or edit an SVG.

Once installed, the four apps cover four distinct jobs:

• Ikonik: Its listing describes 50,000 or more open-source icons across 45 packages, in filled and outline formats, uploaded straight into your site's assets.
• Text Wizard AI: Generates and rephrases text in formal, creative, concise, lengthy, or academic styles, which you place into text elements or CMS fields.
• Modulo: Supplies a library of prebuilt Webflow components, with free components available and others sold individually or by subscription.
• SVGFlow: Changes the color, size, and stroke width of SVG icons directly inside Webflow, without a round trip through a vector editor.

One caveat worth knowing before you commit a client project to any of these: the app landing pages that the Marketplace listings link back to on the vendor's own site currently return 404, and only two of the four products still appear on Azwedo's products page. The apps work, but treat the surrounding documentation as thin.

Place generated code with custom code and the API

If you are holding an HTML and CSS export from Modulify or any other generator, Webflow gives you three places to put it, and the choice comes down to scope. A Code Embed element drops a self-contained block, such as a hero or a pricing table, exactly where you want it on the canvas. Page settings and site settings hold head and body tags for styles and scripts that need broader reach.

To place an export with a Code Embed element:

1. Open the Add panel and drag a Code Embed element to the target location on the canvas.
2. Paste the exported markup and click Save & Close.
3. Publish the site, since custom code appears in preview but only goes live after publishing.

Each Code Embed element holds up to 50,000 characters. It takes HTML directly, CSS inside style tags, and JavaScript inside script tags. Server-side languages such as PHP, Python, Perl, and Ruby are not supported anywhere in Webflow.

The other half of this path is asset hosting, and this is where Cllouda used to sit. With its API host gone, route files through a hosting service that is still maintained and store the returned URLs in Webflow CMS fields. Both Cloudinary and Uploadcare have documented Webflow paths, and the Webflow API writes the resulting URLs back into your collection items.

What you can build with Azwedo and Webflow

The Azwedo apps are content and design accelerators rather than data connectors, so what you build with them shows up in how fast a page gets populated and how consistent it looks.

• Consistent icon systems: Pull icons from Ikonik's packages into your site's assets, then recolor and resize them with SVGFlow so a feature grid reads as one set.
• Faster first-draft copy: Use Text Wizard AI to draft hero headlines and feature descriptions in a chosen style, then refine the survivors by hand.
• Component-led page assembly: Start sections from Modulo's prebuilt components instead of building every layout block from an empty div.
• Agent-driven site edits: Point an MCP client at your site and have it rewrite copy and update CMS items across many pages in one pass.

If your export needs to land on specific pages at scale rather than through the canvas, learn how to apply custom code programmatically across a site.

The shortest route to the AI half of this is not an app install at all: connect the MCP server to the editor you already use and give it a page to build.