Resources · Make integration

Webmetic Make integrationAutomate Webmetic with Make.

Turn every visit Webmetic records into a next step in your other tools. The Webmetic Make integration offers 3 triggers that watch visits and 1 module that calls the Webmetic API. This guide explains each one and walks you through a first working scenario.

Try the Webmetic integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Webmetic Make integration automate?

The Webmetic Make integration links your Webmetic account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Here, the triggers pick up visits Webmetic has recorded, and the action lets you call the Webmetic API directly.

Hand fresh visits to sales. Start with Watch New Visits, then add a module from another app, a CRM or a team chat, so each new visit becomes a record or a message someone can act on.

Spot the people who come back. Watch Returning Visits fits a follow-up flow: if a return visit matters more to you than a first one, you can route those visits to a different list or owner than first-timers.

Give priority to engaged visits. Watch Intensive Visits isolates the visits Webmetic labels as intensive, which makes it the natural start for an alert that should only fire on the visits worth a closer look.

Be aware of one limit: Make itself notes that its documentation for Webmetic is limited, because little public information exists about the app. Test each module with real data before you rely on it. For anything the three triggers do not cover, Make an API Call reaches the Webmetic API with the same connection. If you are still choosing your tool, read the n8n vs Make comparison, and when a run fails, the Make troubleshooting guide lists the usual fixes.

Connect

How do you connect Webmetic to Make?

  1. 01

    Add a Webmetic module

    In your scenario, click the +, search for Webmetic and pick any of its modules, for example Watch New Visits. Then click Create a connection. A connection is your Webmetic account linked to Make once and reused by every Webmetic module.

  2. 02

    Authorize Make

    Give the connection a name if you like, which helps when you manage several accounts. Then either authorize Make on the Webmetic page that opens, or paste the key Webmetic gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and every other Webmetic module in this scenario or the next ones can reuse it without asking you to sign in again.

First scenario

Your first scenario with Webmetic

GoalWhen Webmetic records a new visit, Make picks it up and calls the Webmetic API for the extra detail you need.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. This first slot holds the trigger, the module that starts everything.

  2. 02

    Add Watch New Visits

    Search for Webmetic, choose Watch New Visits and select the connection you created. Fill in the fields Make shows you; once the connection exists, it lists what it can read from your account.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call from Webmetic. Map values from the visit bundle, the item passed along by the trigger, into the request you want to send.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check that the visit data looks right before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Pick your interval, then switch the scenario on.

Triggers

Webmetic triggers in Make

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

Webmetic1Watch Intensive Visits

Watch Intensive Visits

triggerIn the docs only

Watch Intensive Visits hands your scenario only the visits Webmetic marks as intensive, so the rest of the flow works on the visits that stand out instead of all of them. Each one arrives as a bundle, one item for the next module to use.

How it fires
scheduled. Make checks Webmetic on the scenario's schedule, so visits reach you at the next check rather than the moment they happen.
When to use it
for an alert to a salesperson that should stay quiet on casual traffic.
Watch out
Make's documentation does not define what counts as intensive, so compare a few test bundles with what you see in Webmetic.
Webmetic2Watch New Visits

Watch New Visits

triggerIn the docs only

Watch New Visits gives you the broadest view: each visit Webmetic has recorded since the last check becomes a bundle your scenario can send elsewhere, whether to a spreadsheet, a CRM or a chat channel.

How it fires
scheduled. Make asks Webmetic for visits at each run of the scenario, every 15 minutes by default.
When to use it
to keep a complete log of visits in another tool, or to feed your first test scenario.
Watch out
every bundle processed costs an operation, one run of one module that Make counts on your plan, so a busy site can use up a small plan faster than expected.
Webmetic3Watch Returning Visits

Watch Returning Visits

triggerIn the docs only

Watch Returning Visits lets you react to people who come back to your site, which you may treat as a stronger signal than a first visit. The scenario receives those visits as bundles and can route them to a follow-up list or a named owner.

How it fires
scheduled. Make polls Webmetic at the interval set on the first module.
When to use it
when a second visit should trigger a reminder to the person who already spoke with that prospect.
Watch out
Make's documentation does not say how Webmetic tells a returning visit from a new one, so check a few test bundles against your Webmetic data.
Modules

Webmetic modules in Make

Webmetic gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Webmetic1

Make an API Call

ActionIn the docs only

Make an API Call is your way past the three triggers: it sends a request of your choice to the Webmetic API, reusing the connection you already created, so you never have to handle authentication yourself.

When to use it
when you need something from Webmetic that none of the watch modules returns, for instance right after a visit arrives.
Watch out
you write the endpoint and its parameters yourself, and Make's documentation does not list them for Webmetic, so check each response with Run once.
Need help

Need help automating Webmetic with Make?

A person reads every message.

FAQ

Webmetic and Make: frequent questions

01Is the Webmetic Make integration free?
Yes, Webmetic is a standard app in Make, so you can use it from 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 minimum interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Webmetic subscription is a separate matter that this page does not cover.
02What does it take to connect Webmetic to Make?
A Webmetic account and a Make account. Make's documentation lists no specific prerequisite and no dedicated steps for this app, so the standard flow applies: add a Webmetic module, click Create a connection, optionally name it, authorize Make on the Webmetic page or paste the key Webmetic gives you, then click Save. The connection is then reused by every Webmetic module. If the requested information is unclear, look in your Webmetic account settings, since the official documentation is limited.
03Do the Webmetic triggers in Make fire in real time?
No. Make's documentation lists Watch Intensive Visits, Watch New Visits and Watch Returning Visits without describing them, and their Watch names point to scheduled triggers: Make checks Webmetic on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default. On a paid plan you can shorten this to 1 minute, while the Free plan keeps 15 minutes as its minimum. A visit therefore reaches your scenario at the next check, not at the instant it is recorded.
04What if the Webmetic module you need is missing in Make?
Use Make an API Call. It exists for Webmetic and lets you call any endpoint of the Webmetic API from your scenario with the connection you already have. You define the endpoint and the parameters, then check the response with Run once. Keep in mind that Make describes its own Webmetic documentation as limited, so test each request with Run once and read the bundle it returns before you build on it.
05Should you use Make or n8n for Webmetic?
It depends on the tool your team already builds in. On Make, Webmetic comes with 3 scheduled triggers about visits and a Make an API Call module that covers the rest of the API. Many apps also have an n8n node, so check whether Webmetic has one before deciding. The fair way to choose is to list the Webmetic events you want to act on and confirm that the tool you prefer can reach them, then test with a real visit.
Same platform

Other docs you might need on this stack.

Browse all integrations