Resources · Make integration

Nexweave Make integrationAutomate Nexweave with Make.

Can Make create Nexweave experiences for you while you work elsewhere? Yes: the Nexweave Make integration gives you 3 action modules, one per way of building an experience. This guide is for marketers new to Make, and it walks you from connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Nexweave Make integration let you automate?

The Nexweave Make integration links your Nexweave account to Make so that a scenario, the automation you build in Make, can create Nexweave experiences for you. It offers 3 action modules and no trigger, so another app or a schedule starts the flow.

Every new lead gets its own campaign experience. A form tool or CRM starts the scenario, and Create Experience Using Campaign builds a Nexweave experience from a campaign you already set up. Sales reps stop doing it by hand for each contact.

Visual follow-ups from an image or GIF template. When an order ships or a webinar seat is booked in another app, Create Experience Using Image/GIF Template produces a still or animated visual for that person, based on a template you picked.

Video touchpoints at scale. Recruiters or account managers can feed a list of names into Create Experience Using Video Template and get one video experience per bundle, meaning one item passed between modules.

Know the limit before you start: Make's own documentation for Nexweave is marked as limited, because little public information exists about the app. Make gives no description of the 3 modules either, so what this page says about them is read from their names. Test each module with Run once before you trust it. If you want a guided path, the Make training covers the editor basics, and the Make review gives a wider view of the platform.

Weighing another tool? The n8n vs Make comparison lays out the criteria without picking a winner for you.

Connect

How do you connect Nexweave to Make?

  1. 01

    Add a Nexweave module

    Open your scenario, click the + and search for Nexweave. Pick any of its 3 modules, then click Create a connection. A connection is your Nexweave account linked to Make once and reused by every Nexweave module.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps as soon as you manage more than one account. A label such as the workspace or client name makes the right account easy to spot in the list later.

  3. 03

    Authorize and save

    Follow what Make shows next: either an authorization page from Nexweave, or a field where you paste the key Nexweave gives you. Then click Save and Make links the account to your module.

First scenario

Build your first scenario with Nexweave

GoalWhen a new contact arrives in another app, Make creates a Nexweave experience from your campaign.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + to add the first module. Since Nexweave has no trigger, this first bubble belongs to the app where your contacts come from, such as a form or a CRM.

  2. 02

    Add the Nexweave action

    Click the + on the right of that first module, search for Nexweave and choose Create Experience Using Campaign. Click Create a connection if your account is not linked yet.

  3. 03

    Map the contact data

    Fill the module fields. Once the connection exists, Make lists what it can read from your account, and you map data from the first module into the Nexweave one so each contact gets its own experience.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open the bubble above each module to read the bundles it received and check that the Nexweave step returned what you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. Each Nexweave run counts as an operation, the unit Make tracks on your plan.

Modules

What can the Nexweave modules do?

Nexweave gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Nexweave1

Create Experience Using Campaign

ActionIn the docs only

This module gives you a Nexweave experience built on a campaign you already prepared in Nexweave, one for each bundle that reaches it. Pick it when the design work is done and you only want Make to produce a copy per contact.

When to use it
a new lead lands in your CRM and should receive the campaign right away.
Watch out
the documentation is limited, so read the output of Run once before you switch the scenario on.
Nexweave2

Create Experience Using Image/GIF Template

ActionIn the docs only

Here you get a still image or GIF experience generated from a Nexweave template, for when a picture or a short animation says enough. Choose it over the campaign module when you start from a template rather than a finished campaign.

When to use it
an order ships in your store and the customer should get a visual that matches it.
Watch out
nothing in the documentation describes the template fields, so check them in the editor once connected.
Nexweave3

Create Experience Using Video Template

ActionIn the docs only

The result is a video experience created from a Nexweave video template, one per contact that flows through the scenario. It is the option for a personal touch that a picture cannot carry.

When to use it
a candidate reaches the interview stage in your recruiting tool and should get a video message.
Watch out
each bundle means one operation, so a long list of contacts consumes your plan faster than you might think.
Need help

Need help automating Nexweave with Make?

A person reads every message.

FAQ

Nexweave and Make: common questions

01Is the Nexweave Make integration free?
Yes, Nexweave is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Nexweave subscription is a separate matter, handled on the Nexweave side.
02What do you need to connect Nexweave to Make?
You need a Nexweave account and a Make account. Make's documentation lists no specific prerequisite for Nexweave, and it does not describe the connection steps in detail, so the generic Make flow applies. Add a Nexweave module, click Create a connection, optionally name it, then either authorize Make on the Nexweave page or paste the key Nexweave provides, and click Save. The same connection then serves all 3 Nexweave modules in every scenario you build.
03Can a Nexweave scenario start in real time?
Not from Nexweave itself, because the app has no trigger module in Make. The scenario has to start elsewhere. One option is a schedule on the first module: every 15 minutes by default, where Make checks at set intervals, so it is not real time. The other is an instant trigger from another app, which calls Make through a webhook as soon as something happens there, for example a new form entry. Nexweave then acts as the next step of that flow.
04What if a Nexweave module you need is missing in Make?
Nexweave has no Make an API Call module, so you cannot reach other parts of its API from Make with a generic request. Your options are the 3 existing modules, a different app that covers the missing step, or outside help. Keep in mind that Make's documentation for Nexweave is marked as limited, which means testing with Run once matters more than usual. If the gap blocks a project, the help form on this page reaches a team that builds Make scenarios for clients.
05Should you use Make or n8n for Nexweave?
It depends on your criteria, not on a ranking. Many apps available in Make also have an n8n node, so first check whether Nexweave does and which actions each side offers. In Make you get 3 Nexweave action modules, a visual editor and the Free plan to try them. Compare what each tool offers for the exact steps you need, how your team prefers to build, and what the rest of your stack already uses, then decide.