Skip to content
Tutorials Center
My learning

Topics

Lesson 27 of 37 ยท Forms, Ecommerce and Apps

Apps, Custom Code and Velo

Extend Wix and Webflow beyond the visual editor: app marketplaces, embed and custom code, Wix Velo, Webflow code injection and APIs, with runnable stand-ins.

Visual builders cover most needs, but eventually you want something they do not offer: a booking widget, a live chat, a custom calculator, a tracking script, a special database query. Both platforms give you three levels of extension: apps you install, embedded code you paste in, and developer platforms that let you write real code. Choosing the lowest level that works keeps your site simple and fast.

Wix and Webflow are hosted and cannot run here. Menu names and capabilities change over time, so use this lesson as a map and check the current documentation for exact steps. The code samples are stand-ins in plain JavaScript that show the ideas; they do not call the real platform APIs.

Level 1: apps and marketplaces

  • Wix App Market lists apps for bookings, events, chat, forms, subscriptions, SEO tools, analytics and more. You add an app from the editor or dashboard; some are free, some paid monthly, and many are made by third parties. Wix also has its own business apps (Bookings, Events, Blog, Restaurants and others).
  • Webflow Apps (the Apps marketplace) offers integrations such as form tools, analytics, marketing and ecommerce helpers. Many integrate through the Webflow API and install on a site with an authorization step. Webflow also has a long list of third-party tools that work through embeds and automation services rather than formal apps.

Before installing, ask:

  1. Does it solve one clear problem, and does a built-in feature already do that?
  2. What does it load on the page? Every app can add scripts and slow pages.
  3. What data does it access, and is it compliant with your privacy requirements?
  4. What does it cost, and what happens to your content if you cancel?

Level 2: embed and custom code

When an app does not exist, paste code:

  • Webflow: the Embed element lets you drop HTML, CSS and JavaScript anywhere in the page structure. In Site settings, Custom code has head and footer sections for sitewide scripts (analytics, fonts, tag managers), and each page's settings has its own head and body code fields. Custom code requires a paid site plan.
  • Wix: Embed Code (an HTML iframe element or embed a snippet) and, in the dashboard, Custom Code in settings for adding scripts site-wide (tracking tags, chat widgets), with options for where it loads (head, body start or end) and on which pages. Availability depends on the plan.

Some practical notes:

  • Third-party scripts can slow the page. Load them async or defer when the vendor allows it, and only on pages that need them.
  • An embedded iframe is isolated from your page's CSS; you set its size and responsive behavior.
  • Keep a document of every snippet: why it exists and who added it.
  • Never paste code from a source you do not trust. Scripts run with full access to the page, including forms.

A tag loader stand-in

A tag manager pattern loads scripts only on certain pages. The stand-in below shows the decision logic with a rules table, which you could adapt for a custom-code embed.

JS Stand-in: load scripts by page rule

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Level 3: developer platforms

Wix Velo

Velo (formerly Corvid) is Wix's full-stack development platform, built into the editor. It adds:

  • Dev mode: shows a code panel and a page code file for each page.
  • Frontend code: JavaScript that reads and changes page elements using $w selectors (for example $w('#submitButton')), and reacts to events like clicks.
  • Backend code: modules that run on the server for secrets, validation and calls to external services; web modules can be called from page code.
  • Databases: content collections you read and write with the data API.
  • Wix APIs: modules for members, stores, bookings, and so on.

A typical snippet looks like this (read-only; it needs the Wix editor to run):

JavaScript
// Velo page code (read-only, needs the Wix editor)
import wixData from 'wix-data';

$w.onReady(function () {
  $w('#searchButton').onClick(async () => {
    const term = $w('#searchInput').value;
    const results = await wixData.query('Products').contains('title', term).find();
    $w('#repeater').data = results.items;
  });
});

Webflow code and APIs

Webflow does not have a built-in code editor for backend logic, but offers:

  • Custom JavaScript and CSS through embeds and custom-code areas, using attributes and classes you set in the Designer to select elements.
  • The Webflow Data API (REST) for reading and writing CMS items, orders and site data from your own server, serverless function or automation tool. You authorize with a token and send HTTP requests.
  • Webflow Apps (Designer and Data extensions) for developers building products that extend the Designer or manage sites.
  • Webflow Cloud and related hosting options are newer features aimed at running server code alongside a site; check current documentation for availability.

A typical Webflow-side script selects elements by attribute and adds behavior:

JavaScript
// Webflow custom code (read-only here; runs on a published page)
document.querySelectorAll('[data-copy]').forEach((btn) => {
  btn.addEventListener('click', () => navigator.clipboard.writeText(btn.dataset.copy));
});

Mimicking the Velo pattern

The stand-in below reproduces the idea behind $w and a data query with a tiny in-memory model, so you can see the flow: user types, the code queries, the page list updates.

JS Stand-in: search and update a list

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Choosing the right level

Need Try first Then
Booking, chat, events App Embed from the vendor
Analytics, tag manager Custom code in head Tag manager rules
Custom calculator Embed HTML/JS Velo page code or a Webflow script
Secure server work (API keys) Velo backend or your own server Webflow Data API from a server
Sync data between tools Automation tool Custom integration (next lesson)

Common mistakes

  • Installing several apps that do the same thing.
  • Adding scripts to every page when only one page needs them.
  • Putting secret keys in frontend code where anyone can read them.
  • Forgetting that custom code may not run inside the editor's preview.
  • Skipping a plan check: some features need paid plans.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which is the lowest level of extension?

    Apps need no code, so try them first before moving to embeds and developer platforms.
  2. 2. What is Wix Velo?

    Velo adds page code, backend code and databases to Wix sites.
  3. 3. Why not place a secret API key in frontend page code?

    Visitors can view all code that reaches the browser, so secrets belong on the server side.
  4. 4. How can you reduce the speed impact of third-party scripts?

    Limiting where they load and deferring them keeps pages fast.

Summary

  • Extend a site with apps first, embedded code second, developer platforms third.
  • Wix Velo adds page code, backend modules and databases; Webflow uses custom code and the Data API.
  • Third-party scripts affect speed and privacy; load them only where needed.
  • Keep secrets off the frontend and document every snippet you add.

Next: Integrations, Webhooks and Automation