Resources · Make integration

LivingMetrics Make integrationAutomate LivingMetrics with Make.

Can Make keep your LivingMetrics contacts in sync with the rest of your tools? The LivingMetrics Make integration offers 12 modules: 3 triggers, 7 actions and 2 searches. This guide connects your account, then walks you through a first scenario, step by step.

Try the LivingMetrics integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the LivingMetrics Make integration do for you?

The LivingMetrics Make integration links your LivingMetrics account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or writes data in one app. Once linked, contacts and history records can move between LivingMetrics and your other apps without copy and paste.

Leads that land in the right place. A sign-up arrives in your form tool, and Creates a Contact adds that person to LivingMetrics, while Create a History Record can note where the lead came from. Nobody retypes a name.

A team that hears about changes. Watch Updated Contacts spots contacts that were edited, so a sales rep can get a message in the app of your choice when a record they follow changes.

A clean exit for a contact who asks. When a request to be removed comes in, Search Contacts finds the record and Forget a Contact handles it, without anyone digging through the interface.

A word of honesty: the official Make documentation for LivingMetrics is thin. It lists the module names but describes neither their fields nor their limits, so this page sticks to what those names tell and flags the rest. Before you build something critical, test each module on a dummy contact. If you want a second opinion on the platform first, read the Make review, and if you still hesitate between the two tools, the n8n vs Make comparison lays out the criteria. For the cost side, see Make pricing.

Connect

How do you connect LivingMetrics to Make?

  1. 01

    Add a LivingMetrics module

    In your scenario, add any LivingMetrics module, for instance Get a Contact, then click Create a connection. A connection is your LivingMetrics account linked to Make once, and every LivingMetrics module reuses it afterwards.

  2. 02

    Name the connection

    Giving it a name is optional, yet handy: if a colleague later adds a second LivingMetrics account, a label such as the account owner's name tells the two apart in every module's dropdown.

  3. 03

    Authorize Make and save

    Depending on what LivingMetrics asks, either approve access on the LivingMetrics page that opens, or paste the key the app gives you. Then click Save, and the module is ready to be filled.

First scenario

Your first scenario with LivingMetrics

GoalWhen a lead fills in a form in another app, Make creates the contact in LivingMetrics and logs a history record for it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module: the one from the app where your leads come in, such as your form tool.

  2. 02

    Add Creates a Contact

    Click the + on the right of that first module, search for LivingMetrics and pick Creates a Contact. Create the connection if this is your first LivingMetrics module.

  3. 03

    Map the form answers

    Fill the module fields by picking values from the previous module: the name and email the lead typed. Each lead travels as a bundle, one item passed from a module to the next.

  4. 04

    Log the origin

    Add Create a History Record after it, so the new contact carries a trace of where it came from. Map the data you want from the two previous modules.

  5. 05

    Test with Run once

    Submit a test entry in your form, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the contact in LivingMetrics.

  6. 06

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default for a new scenario, 15 minutes at the shortest on the Free plan), then switch the scenario on.

Triggers

What can start a LivingMetrics scenario?

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

LivingMetrics1Watch New Contacts

Watch New Contacts

triggerIn the docs only

Every contact added to LivingMetrics since the last check can start your scenario, one bundle per person, so the rest of your stack learns about a newcomer without anyone exporting a list.

How it fires
scheduled, Make checks the app on the scenario's schedule, so a new contact shows up at the next check rather than the second it is created.
When to use it
you want each new LivingMetrics contact copied to a spreadsheet, a CRM or a team chat.
Watch out
the Make documentation does not describe this trigger's settings, so run it once on a test contact and read the bundle before relying on it.
LivingMetrics2Watch New Histories

Watch New Histories

triggerIn the docs only

Here the starting point is a new history in LivingMetrics rather than a person: each one found since the previous check becomes a bundle your scenario can act on, for instance to notify whoever owns the account.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up whatever appeared in between.
When to use it
activity logged in LivingMetrics should reach another tool, like a reporting sheet or a message to the team.
Watch out
the documentation does not say what a history contains, so check a real bundle with Run once before mapping it.
LivingMetrics3Watch Updated Contacts

Watch Updated Contacts

triggerIn the docs only

Edits are what this one catches: a contact already in LivingMetrics that changed since the last check is handed to your scenario, which keeps copies of that record elsewhere from drifting out of date.

How it fires
scheduled, Make checks the app on the scenario's schedule, so an edit shows up at the next check.
When to use it
a second tool holds the same contacts and must follow every correction.
Watch out
if the same scenario also runs Update a Contact on LivingMetrics, its own edits can wake it up again, so avoid pairing the two on one record.
Modules

What LivingMetrics modules are available in Make?

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

LivingMetrics1

Create a Form Submit

ActionIn the docs only

Going by its name, this action sends a form submission into LivingMetrics, so an answer collected in another tool can count as if it had been filled in LivingMetrics itself.

When to use it
your leads fill a form elsewhere, and you want LivingMetrics to receive them as submissions rather than as bare contacts.
Watch out
the documentation lists no fields for it, so open the module in Make and check what it asks before mapping.
LivingMetrics2

Create a History Record

ActionIn the docs only

Adding an entry to the history kept in LivingMetrics gives your team a written trace of what happened, logged by the scenario instead of by hand.

When to use it
right after another module did something worth remembering, like creating a contact from a web form or sending a quote from another app.
Watch out
the fields are not documented; run the scenario once and look at the record in LivingMetrics to confirm it reads well.
LivingMetrics3

Creates a Contact

ActionIn the docs only

New people reach LivingMetrics through this action: each bundle it receives becomes a fresh contact, with the details you map from earlier modules.

When to use it
a lead, a buyer or a sign-up appears in another app and should exist in LivingMetrics too.
Watch out
nothing in the documentation says it checks for duplicates, so put Search Contacts in front of it when the same person may arrive twice.
LivingMetrics4

Forget a Contact

ActionIn the docs only

As its name suggests, this action tells LivingMetrics to forget a given contact, which saves you from hunting down that person by hand when they ask to leave your lists.

When to use it
a removal request comes in through a form or an email, and you want it handled the same way every time.
Watch out
the documentation does not say whether this can be undone, so treat it as final and test it on a dummy contact only.
LivingMetrics5

Get a Contact

ActionIn the docs only

With one known contact in hand, this action fetches its current record from LivingMetrics, so later modules work on fresh data instead of what a trigger saw earlier.

When to use it
you already have the contact's identifier from a previous module and need its full details, for a message or a sync.
Watch out
it reads one contact; to find people by a criterion, Search Contacts is the right module.
LivingMetrics6

List Histories

SearchIn the docs only

Pulling several history entries out of LivingMetrics in one pass is the job here, each entry coming out as its own bundle for the modules that follow.

When to use it
you want to review or export past activity, for example to feed a report in a spreadsheet.
Watch out
a search can return zero, one or many bundles, and every following module then runs once per bundle, which costs one operation each time.
LivingMetrics7

Make an API Call

ActionIn the docs only

Anything the listed modules leave out can still be reached: this module calls any endpoint of the LivingMetrics API from your scenario, using the same connection as the others.

When to use it
you need a LivingMetrics feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the LivingMetrics API documentation open next to Make, since the Make documentation does not cover it.
LivingMetrics8

Search Contacts

SearchIn the docs only

Finding who is already in LivingMetrics before acting avoids duplicates and blind updates: this search returns the matching contacts, one bundle per result.

When to use it
before Creates a Contact, Update a Contact or Forget a Contact, to make sure you touch the right person.
Watch out
an empty result is possible, and several matches are too; test both cases with Run once before switching the scenario on.
LivingMetrics9

Update a Contact

ActionIn the docs only

Changes made elsewhere land on an existing LivingMetrics contact through this action, which keeps the record current without anyone opening it.

When to use it
a customer edits their details in another tool, and LivingMetrics should follow.
Watch out
you need to know which contact to change, so pair it with Search Contacts, and avoid combining it with Watch Updated Contacts on the same record to prevent a loop.
Need help

Need help automating LivingMetrics with Make?

A person reads every message.

FAQ

LivingMetrics and Make: frequent questions

01Is the LivingMetrics Make integration free?
Yes, LivingMetrics is a standard app in Make, so its modules work from the Free plan. That plan keeps 2 active scenarios, waits at least 15 minutes between two scheduled runs, stops a run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Each module execution counts as an operation on your plan. Your LivingMetrics subscription is a separate matter.
02What do you need to connect LivingMetrics to Make?
A LivingMetrics account and a Make account are enough to start, since the Make documentation lists no other prerequisite. Add a LivingMetrics module, click Create a connection, give it a name if you like, then either approve access on the LivingMetrics page or paste the key the app provides, and save. The connection is then reused by every LivingMetrics module. If it fails, check that you are signed in to the right LivingMetrics account.
03Do LivingMetrics triggers in Make fire in real time?
No. The three LivingMetrics triggers are scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, and handles everything that changed since the previous check. On a paid plan you can shorten that interval down to 1 minute. None of them is listed as an instant trigger, which would let LivingMetrics call Make the moment something happens. For most syncs of contacts and histories, a scheduled check is plenty.
04What if a LivingMetrics module is missing in Make?
Use Make an API Call. It reaches any endpoint of the LivingMetrics API from your scenario with the same connection, so a feature without a dedicated module is still within reach. You write the request yourself, which means reading the LivingMetrics API documentation, because the Make documentation for this app is limited and describes no fields. If the result still falls short, another app can take over that part of the scenario.
05Should you use Make or n8n for LivingMetrics?
It depends on the tool your team already uses. On Make, LivingMetrics comes with 12 ready modules covering contacts, histories and form submissions, plus Make an API Call for the rest. The same app often has an n8n node too, but that is worth checking before choosing. Compare the modules available on each side against your scenario, then pick the tool your team is ready to maintain. The comparison page linked above sets out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations