Automate Wizup With Make: 4 Modules, Zero Code Required

What you can automate

What can the Wizup Make integration do for you?

The Wizup Make integration links your Wizup account to Make, a tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. With Wizup you get one trigger that watches received data and three actions: send a template, start a flow, or call the Wizup API directly.

Push received data into your other tools. Watch Received Data picks up what lands in Wizup and hands each item to the next module, so a spreadsheet, a CRM or a chat channel can react without anyone copying it by hand.

Send a template when another app says so. Put a form, a shop or a CRM first, then Send Template in Wizup. The event lives elsewhere, the message goes out from Wizup.

Start a Wizup flow from outside. Trigger Flow lets an event in another app kick off a flow you already built in Wizup, which keeps the logic where your team maintains it.

Be aware of one real limit: Make itself states that its Wizup documentation is incomplete, because too little public information exists about the app. Field names and behaviors are best confirmed in your own account with a test run. When the three listed actions fall short, Make an API Call reaches the rest of the Wizup API with the same connection. To go further, the Make training covers the editor step by step, Make pricing explains plans and operations, and n8n vs Make helps if you are still picking a platform.

Connect

How do you connect Wizup to Make?

01
Add a Wizup module
Open a scenario, click the + and search for Wizup. Pick any of its modules, then click Create a connection. A connection is your Wizup account linked to Make once and reused by every Wizup module afterwards.
02
Name it and authorize
Give the connection a name if you want, useful when you manage several accounts. Then either authorize Make on the Wizup page that opens, or paste the key Wizup gives you, depending on what the window asks for.
03
Save and check
Click Save. Back in the module, Make can now read your account. Make gives no Wizup-specific check, so your first Run once is what confirms the connection works.

First scenario

Your first scenario with Wizup

GoalWhen a new entry arrives in another app, Make sends a Wizup template built from that entry.

01
Create the scenario
From the Scenarios page, create a new scenario and click the + to add the first module. Choose the app where the event happens, for example your form tool or your CRM.
02
Set up the first module
Connect that app and fill in its fields. Once the connection exists, Make lists the forms, lists or objects it can read, so you pick from a menu instead of typing names.
03
Add Send Template
Click the + on the right of the first module, search for Wizup and pick Send Template. Create or reuse your Wizup connection, then map the data coming from the first module into the template fields.
04
Test with Run once
Click Run once and trigger a real event in the first app. Open the bubble above each module to read the bundles it received; a bundle is one item passing from a module to the next.
05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as an operation, the unit Make uses on your plan.

Triggers

What starts a Wizup scenario

1 module starts a scenario when something happens in Wizup. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Wizup as soon as it happens.

Wizup1Watch Received Data

Watch Received Data

triggerIn the docs only

Watch Received Data lets a scenario pick up the data that reaches your Wizup account and pass each new item along as its own bundle. It is the only Wizup module that can open a scenario on its own.

How it fires

scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, or as often as every minute on paid plans.

When to use it

when something collected in Wizup has to land in a spreadsheet, a CRM or a team channel without manual export.

Watch out

the scheduled type is deduced from the module's name, and Make's docs do not describe what counts as received data, so run it once and inspect the bundles before mapping anything.

Modules

What Wizup can do in Make

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

Wizup1

Make an API Call

ActionIn the docs only

Reach any endpoint of the Wizup API from your scenario, reusing the Wizup connection you already created, so no second login is needed.

When to use it

the three ready-made modules do not cover what you need, for example a Wizup feature Make has no module for yet.

Watch out

you write the request yourself, since Make documents no Wizup endpoint; test it with Run once before relying on it.

Wizup2

Send Template

ActionIn the docs only

Judging by its name, it sends a template you prepared in Wizup, filled with data from earlier modules instead of retyped by hand.

When to use it

a lead signs up in a form, or a deal moves forward in your CRM, and the follow-up message should leave from Wizup rather than from your inbox.

Watch out

Make does not document its fields, so map one test record, click Run once and check what was sent before going live.

Wizup3

Trigger Flow

ActionIn the docs only

As its name suggests, it starts a flow that already exists in Wizup from any other app in Make, so Wizup runs the sequence your team designed there.

When to use it

the steps live in Wizup, but the event that should launch them happens elsewhere, like a paid order or a closed ticket.

Watch out

the flow has to exist in Wizup first; Make only starts it and has no documented way to edit it.

Need help

Need help automating Wizup with Make?

A person reads every message.

FAQ

Wizup and Make: common questions

01Is the Wizup Make integration free?

Yes, Wizup is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations each month.

02What do you need to connect Wizup to Make?

A Wizup account and permission to authorize Make on it are the basics. The Make documentation lists no specific prerequisite and no official connection steps for Wizup, so the standard flow applies: add a Wizup module, click Create a connection, optionally name it, authorize Make on the Wizup page or paste the key Wizup provides, then click Save. The same connection then serves all four Wizup modules, including Make an API Call.

03Does the Wizup trigger react in real time?

No. Make's docs list no type for Watch Received Data, but its name points to a scheduled trigger. Make does not get notified by Wizup; it checks for new data on the scenario's schedule, which is every 15 minutes by default. On the Free plan that is also the shortest gap allowed, while paid plans can check as often as every minute. If near-immediate reaction matters, set the shortest interval your plan allows and keep in mind that each check uses operations.

04What if a Wizup module is missing in Make?

Use Make an API Call. It reaches any endpoint of the Wizup API with the connection you already set up, which covers features the three ready-made actions skip. Make also warns that its Wizup documentation is incomplete, so fields are best confirmed by running the module once on a test record. If a step still blocks after that, the Make troubleshooting guide is the next place to look, since it covers errors that are not specific to one app.

05Should you use Make or n8n for Wizup?

It depends on what you need to run. On Make, Wizup offers 4 modules: 1 scheduled trigger and 3 actions, including a generic API call for anything else. Whether n8n offers a Wizup node is not covered by the information behind this page, so check its node list before deciding. Compare the two on the modules you actually need and on the platform your team already knows, rather than on the app name alone.

Add a Wizup module

Name it and authorize

Save and check

Create the scenario

Set up the first module

Add Send Template

Test with Run once

Schedule and switch on

Need help automating Wizup with Make?