Resources · Make integration

WEBLUCY™ Make integrationAutomate WEBLUCY™ with Make.

Can a booking or a form on your website update your contacts on its own? The WEBLUCY™ Make integration gives you 26 modules: 6 triggers, 13 actions and 7 searches. This page walks you through the connection and your first scenario, step by step.

Try the WEBLUCY™ integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the WEBLUCY™ Make integration do for you?

The WEBLUCY™ Make integration links your WEBLUCY™ website to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that pass data along. Each module is one brick, like watching new orders or creating a contact. You pick them, connect your account once and Make does the rest.

Every form entry becomes a contact on a list. Watch Form Submissions picks up new entries, Create a Contact files the person, and Add Contact to Email List places them in the audience you choose. Nobody retypes a name again.

Orders reach the rest of your tools. Watch Order Created and Watch Order Updated start a scenario when your shop moves, and Get an Order brings back the details another app needs, for example your accounting sheet or a team chat.

Your catalog stays in sync. Watch Product Created and Watch Product Updated let a spreadsheet or another store follow your WEBLUCY™ products, while List Products gives you the full catalog in one pass.

A word of honesty: Make itself says its documentation for WEBLUCY™ is limited, because little public information exists about the app. What each module does is read here from its name, and a test with Run once on real data is the safest way to confirm it. When a listed module falls short, Make an API Call reaches the rest of the app. If you are still choosing your tool, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted. Stuck on an error? See Make troubleshooting.

Connect

How do you connect WEBLUCY™ to Make?

  1. 01

    Add a WEBLUCY™ module

    In your scenario, click the + and type WEBLUCY™ in the search. Pick any module, for instance Watch Form Submissions, then click Create a connection. A connection is your WEBLUCY™ account linked to Make once, then reused by every module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, handy when you manage several sites. Then either approve Make on the WEBLUCY™ page that opens, or paste the key WEBLUCY™ gives you, depending on what the window asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now read your account and offers the objects it finds, so you pick from a list instead of typing IDs from memory.

First scenario

Build your first scenario with WEBLUCY™

GoalWhen someone submits a form on your WEBLUCY™ site, Make creates the contact and adds it to your email list.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle. That empty circle is where your first module, the trigger, will sit.

  2. 02

    Set the trigger

    Search WEBLUCY™, choose Watch Form Submissions and select your connection. Fill the fields Make shows you; once connected, it lists what it can read in your account.

  3. 03

    Add the contact

    Click the + on the right of the trigger, add Create a Contact and map the details that came with the form entry into its fields. Each entry travels as one bundle, one item passed along.

  4. 04

    Put it on a list

    Add Add Contact to Email List after it, choose the list and map the contact created one step earlier. The chain now reads form, contact, list.

  5. 05

    Test with Run once

    Submit a test entry on your site, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can see exactly what went through.

  6. 06

    Schedule and switch it on

    Open the clock on the first module: a new scenario checks every 15 minutes by default. Keep that or shorten it on a paid plan, then switch the scenario on.

Triggers

Which WEBLUCY™ triggers start a scenario?

6 modules start a scenario when something happens in WEBLUCY™. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by WEBLUCY™ as soon as it happens.

WEBLUCY™1Watch Booking Created

Watch Booking Created

triggerIn the docs only

Going by its name, Watch Booking Created starts your scenario with each new booking taken on your WEBLUCY™ site, so a reservation can reach your calendar or your team without anyone copying it over.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when the booking itself is the moment that matters, such as a client reserving a consultation slot.
Watch out
the app's documentation is thin, so make a test booking and read the bundle before mapping anything.
WEBLUCY™2Watch Form Submissions

Watch Form Submissions

triggerIn the docs only

Watch Form Submissions brings every new entry from your WEBLUCY™ forms into Make, one bundle per entry, ready to become a contact, a ticket or a message to your team.

How it fires
scheduled. Make checks the app on the scenario's schedule; on the Free plan the shortest gap between two checks is 15 minutes.
When to use it
for a contact or quote form whose answers you currently copy by hand.
Watch out
a scheduled check means entries arrive in batches, not one by one the second they are sent.
WEBLUCY™3Watch Order Created

Watch Order Created

triggerIn the docs only

With Watch Order Created, each fresh order from your WEBLUCY™ shop opens a scenario run, which is how you push sales into a spreadsheet, an invoicing tool or a team channel.

How it fires
scheduled. Make checks the app on the scenario's schedule, and a paid plan brings the gap down to 1 minute.
When to use it
when an order should start a follow-up, like a shipping note or a welcome email.
Watch out
it reacts to new orders only; changes to an existing order belong to Watch Order Updated.
WEBLUCY™4Watch Order Updated

Watch Order Updated

triggerIn the docs only

Watch Order Updated is the trigger to follow an order after it exists: as its name says, it picks up orders that changed, so your other tools see the latest state.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the instant the change is saved.
When to use it
to update a row in your tracking sheet or warn a colleague when an order moves along.
Watch out
the documentation does not list which changes count, so run it once after editing a test order to see what it returns.
WEBLUCY™5Watch Product Created

Watch Product Created

triggerIn the docs only

Watch Product Created lets the rest of your stack know when you add something to your WEBLUCY™ catalog: a spreadsheet, another sales channel or a note to your marketing team.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes unless you change the clock.
When to use it
when a new product should be announced or copied somewhere else once it goes live.
Watch out
it only covers creation; price or stock edits on an old product need Watch Product Updated.
WEBLUCY™6Watch Product Updated

Watch Product Updated

triggerIn the docs only

Watch Product Updated keeps copies of your catalog honest: from what the name tells, it hands Make each product that was edited, so a mirror sheet or a second store can follow.

How it fires
scheduled. Make checks the app on the scenario's schedule, which you set with the clock on the first module.
When to use it
when you edit products in WEBLUCY™ and another tool must show the same thing.
Watch out
pair it with Watch Product Created if new items must follow too.
Modules

What can the WEBLUCY™ modules do?

WEBLUCY™ gives you 20 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

WEBLUCY™1

Add Contact to Email List

ActionIn the docs only

Add Contact to Email List places a WEBLUCY™ contact on one of your email lists, so the person starts getting the messages that audience receives.

When to use it
right after a newsletter form or a first order, when the person belongs in a given audience.
Watch out
the name points to a contact already in WEBLUCY™, so put Create a Contact or Search Contact before it.
WEBLUCY™2

Create a Contact

ActionIn the docs only

Create a Contact files a new person in your WEBLUCY™ contacts from data another module brought in: a form entry, a sheet row or a lead from another app.

When to use it
when your leads start outside WEBLUCY™ and you want them all in one address book.
Watch out
run Search Contact first if the same person may come back twice, or duplicates will pile up.
WEBLUCY™3

Create a Member

ActionIn the docs only

Create a Member registers someone as a member of your WEBLUCY™ site. Make keeps members and contacts in separate modules, so choose the one that matches the list you actually manage.

When to use it
when a paid order or an approved form should give a person member status.
Watch out
the documentation says nothing about what a new member receives, so try it on a test person first.
WEBLUCY™4

Delete a Contact

ActionIn the docs only

Delete a Contact removes one person from your WEBLUCY™ contacts for good, which keeps your address book clean when someone leaves or asks to be erased.

When to use it
in a scenario that handles removal requests coming from a form or another tool.
Watch out
a deletion cannot be taken back from Make; test it on a dummy contact with Run once before switching the scenario on.
WEBLUCY™5

Delete a Member

ActionIn the docs only

Delete a Member takes a member off your WEBLUCY™ site, the natural last step when a subscription or an access right comes to an end elsewhere.

When to use it
when your payment tool reports a cancellation and the member area should follow without anyone logging in.
Watch out
nothing brings the member back afterwards, so feed it one precise member, never the output of a broad list.
WEBLUCY™6

Delete a Product

ActionIn the docs only

Delete a Product pulls an item out of your WEBLUCY™ catalog, which saves you from selling something that no longer exists in your stock system.

When to use it
when a product is retired in your inventory sheet or your supplier tool and the site must drop it too.
Watch out
removal is final and Make offers no undo, so let it act only on a product you identified with Get a Product or List Products.
WEBLUCY™7

Get a Contact

ActionIn the docs only

Get a Contact fetches the full record of one contact you can already identify, so later modules have every detail at hand instead of the few a trigger passed along.

When to use it
after a booking or an order, to enrich the message you send with what WEBLUCY™ knows about that person.
Watch out
it needs one precise contact; when you only have a name or a clue, start with Search Contact.
WEBLUCY™8

Get a Member

ActionIn the docs only

Get a Member returns what WEBLUCY™ holds about one member, handy when a scenario must check who someone is before granting or refusing something.

When to use it
when a request arrives from a form and you want the member's details before replying.
Watch out
it reads one member at a time; to go through all of them, List Members is the module you want.
WEBLUCY™9

Get a Product

ActionIn the docs only

Get a Product brings back the complete sheet of a single product, useful when a trigger only gave you a reference and the next tool needs more.

When to use it
after Watch Order Created, to add product details to an invoice line or a message to the warehouse.
Watch out
since the documentation is limited, run it once and look at the bundle to learn which details come back.
WEBLUCY™10

Get an Order

ActionIn the docs only

Get an Order pulls one order in full from your WEBLUCY™ shop, so whoever handles fulfillment or accounting gets the whole picture in their own tool.

When to use it
when Watch Order Updated tells you an order moved and you need its current state before acting.
Watch out
it reads a single order; for a batch, use List Orders and remember each bundle adds operations downstream.
WEBLUCY™11

List Bookings

SearchIn the docs only

List Bookings gathers the bookings in your WEBLUCY™ account into bundles, which gives you material for a recap, a planning sheet or a reminder run.

When to use it
when you need the bookings as a set rather than one at a time as they come in.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
WEBLUCY™12

List Contacts

SearchIn the docs only

List Contacts pulls your WEBLUCY™ address book into Make, one bundle per person, to copy it into a CRM, a sheet or an email tool.

When to use it
for a first bulk export, or to compare what WEBLUCY™ holds against another tool.
Watch out
a long list means many operations on the next modules; test on a small account before a full run.
WEBLUCY™13

List Form Submissions

SearchIn the docs only

List Form Submissions collects the entries already sent through your WEBLUCY™ forms, including the ones received before you built any scenario.

When to use it
to catch up on past answers once, before Watch Form Submissions takes over the new ones.
Watch out
if you chain both in the same flow, you may process the same entry twice; keep the catch-up in its own scenario.
WEBLUCY™14

List Members

SearchIn the docs only

List Members hands you every member of your WEBLUCY™ site as separate bundles, which is the starting point for an audit or a sync with another member tool.

When to use it
when you want to check your member base against your payment records or a mailing tool.
Watch out
each member flowing out counts as work for every following module, so keep the chain short.
WEBLUCY™15

List Orders

SearchIn the docs only

List Orders returns the orders of your WEBLUCY™ shop as a set, which suits a sales report or a transfer into accounting better than order by order.

When to use it
for a one-off export or a reconciliation with your bank or invoicing tool.
Watch out
the documentation gives no filter for this module, so expect the whole set and check the first bundles with Run once.
WEBLUCY™16

List Products

SearchIn the docs only

List Products gives you the whole WEBLUCY™ catalog in bundles, the quickest way to fill a spreadsheet or feed another store with what you sell.

When to use it
when you set up a product mirror for the first time, before the product triggers keep it current.
Watch out
with a large catalog, the modules after it run once per product, which adds up on your plan.
WEBLUCY™17

Make an API Call

ActionIn the docs only

Make an API Call is your way around the gaps: it calls any endpoint of the WEBLUCY™ API with the connection you already set up, even for actions no listed module covers.

When to use it
when you need something the other modules skip, such as a WEBLUCY™ feature that none of the 26 listed modules reaches.
Watch out
you have to know the endpoint yourself, and Make's documentation for this app is limited.
WEBLUCY™18

Search Contact

SearchIn the docs only

Search Contact looks for people in your WEBLUCY™ contacts from what you know about them, and tells you whether they already exist before you create anything.

When to use it
as a check in front of Create a Contact, so a returning visitor does not become a second record.
Watch out
a search may find nobody, one person or several, so plan what the scenario does in each case.
WEBLUCY™19

Update a Contact

ActionIn the docs only

Update a Contact changes the details of a person already in WEBLUCY™, so your address book reflects what they told you last, wherever they told it.

When to use it
when a returning customer fills a form again or a CRM holds fresher data than your site.
Watch out
find the right person first with Search Contact or Get a Contact, or you may overwrite someone else.
WEBLUCY™20

Update a Member

ActionIn the docs only

Update a Member edits a member's record on your WEBLUCY™ site, which keeps access and profile details aligned with your other tools.

When to use it
when a plan change in your payment tool or a new answer on a form should show up on the member side.
Watch out
map only the details you really want to change, and test with Run once on a test member.
Need help

Need help automating WEBLUCY™ with Make?

A person reads every message.

FAQ

Questions about the WEBLUCY™ Make integration

01Is the WEBLUCY™ Make integration free?
Yes, you can start for free. WEBLUCY™ is a standard app, available from the Make Free plan. That plan keeps 2 active scenarios, a gap of 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 gap to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, each month. Any cost of WEBLUCY™ itself is a separate matter.
02What do you need to connect WEBLUCY™ to Make?
A WEBLUCY™ account and a Make account. Make's documentation lists no special prerequisite and no official connection steps for this app, so the generic path applies: add a WEBLUCY™ module, click Create a connection, give it a name if you want, then either approve Make on the WEBLUCY™ page that opens or paste the key the app provides, and click Save. The connection is reused by every WEBLUCY™ module in your scenarios afterwards.
03Do WEBLUCY™ triggers react instantly in Make?
Most likely not. Make's app directory was unavailable, so the 6 WEBLUCY™ triggers are typed as scheduled from their Watch names, a deduction: Make then checks the app on the scenario's schedule instead of being called by WEBLUCY™ when something happens. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. On a paid plan you can bring it down to 1 minute. For bookings, forms and orders that is usually plenty, as long as you know entries arrive grouped per check.
04What if a WEBLUCY™ module is missing in Make?
It depends on what you need, but there is a way out. The app has a Make an API Call module that calls any endpoint of the WEBLUCY™ API with the connection you already set up, so actions the 26 listed modules skip can still be reached. Keep in mind that Make describes its WEBLUCY™ documentation as limited, for lack of public information about the app, so you will need the endpoint details from WEBLUCY™ and a test with Run once.
05Should you use Make or n8n for WEBLUCY™?
It depends on your criteria rather than on WEBLUCY™. On the Make side, the facts are simple: 26 ready modules, 6 scheduled triggers, a Make an API Call module for the rest, and a start on the Free plan. The same app often has an n8n node too, so check that first if n8n is already part of your stack. Compare how each tool fits your team and your existing automations, and see the n8n vs Make comparison linked above for the details.
Same platform

Other docs you might need on this stack.

Browse all integrations