Resources · Make integration

Livespace CRM Make integrationAutomate Livespace CRM with Make.

What if every deal that moves in your pipeline created its own follow-up? The Livespace CRM Make integration gives you 33 modules: 9 triggers on deals, companies and people, plus 19 actions and 5 searches. This guide shows sales and ops teams how to link the account and build a first working scenario.

Try the Livespace CRM integration on MakeSee the 33 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Livespace CRM Make integration do for your sales team?

The Livespace CRM Make integration lets Make read and write your CRM for you: it spots new or changed deals, companies and people, then creates records, notes, tasks and call logs in response. You build this as a scenario, which is the automation you assemble in Make from small bricks called modules, with no code at all.

A follow-up task for every stage change. Watch Stage Changes in Deals picks up a deal that moved forward, and Create a Task puts the next step on the right person's list. Add Send a Notification to an User and the rep hears about it inside Livespace.

Clean company records from other tools. When a lead lands in a form or a spreadsheet, List Companies checks whether the company already exists, then Create a Company or Update a Company keeps a single record instead of duplicates.

A paper trail on closed business. Watch Closed Deals fires once a deal is closed; Create a Note for a Deal and Add a Cost to a Deal record what finance needs to know. The same pattern works for people, with Log a Call for a Person after a call from your phone system.

What Make does not do here: every Livespace CRM trigger is scheduled, so Make checks the CRM on the scenario's clock instead of reacting the second something changes. When a listed module falls short, Make an API Call reaches the rest of the Livespace API with the same connection. Want the bigger picture before you start? Read the Make review, check Make pricing to size your plan, and compare the two main tools in n8n vs Make.

Connect

How do you connect Livespace CRM to Make?

  1. 01

    Copy your API key and secret

    In Livespace CRM, open Account settings, click API in the sidebar, then Users of your Livespace account. Two values appear on screen: the API key and the API secret. Copy both, you will paste them into Make.

  2. 02

    Open the connection window

    In your Make scenario, add any Livespace CRM module and click Create a connection. A connection is your Livespace account linked to Make once; every Livespace module in your scenarios reuses it afterward.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name like "Livespace sales" helps when a teammate opens the scenario later. Paste the API key and API secret, save, and Make can now list your deals, companies and people.

First scenario

Build your first scenario: a task for every stage change

GoalWhen a deal moves to a new stage in Livespace CRM, Make creates a task for the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. This first module decides when the whole scenario starts.

  2. 02

    Add the stage trigger

    Search for Livespace CRM, pick Watch Stage Changes in Deals and click Create a connection if you have not linked your account yet. Fill the fields Make shows once the connection works.

  3. 03

    Add the task

    Click the + on the right of the trigger and choose Create a Task. Map data from the deal the trigger found into the task so the rep knows which deal it is about.

  4. 04

    Test with Run once

    Move a test deal to another stage in Livespace, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one deal. Check that the task appeared in the CRM.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Keep that or change it within your plan, then switch the scenario on so it runs without you.

Triggers

Triggers: what starts a Livespace CRM scenario

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

Livespace CRM1Watch Closed Deals

Watch Closed Deals

Scheduled trigger

In Make“Triggers when a deal has been closed.”

Hands your scenario each deal that has just been closed, so the work that follows a signature can start without anyone copying details by hand.

How it fires
scheduled. Make checks Livespace CRM on the scenario's schedule and collects the deals closed since the previous check.
When to use it
you want onboarding, invoicing or a thank-you step to begin as soon as a deal is won, for example by writing a deal note or telling the account manager.
Watch out
each closed deal counts as its own bundle, and every module after the trigger runs once per deal, which adds operations, the unit Make counts on your plan (one module run on one bundle).
Livespace CRM2Watch Completed Actions in Deals

Watch Completed Actions in Deals

Scheduled trigger

In Make“Triggers when a deal's process actions has been marked as done.”

Reacts when someone ticks off a process action inside a deal, which lets you chain the next step of your sales process to the one just finished.

How it fires
scheduled. Make asks Livespace CRM for newly completed deal actions each time the scenario runs.
When to use it
your pipeline has checklists per stage, and finishing one item (a demo held, a quote sent) should create a task, a note or an alert for someone else.
Watch out
this watches process actions in deals, not stage moves; if you care about the stage itself, pick Watch Stage Changes in Deals instead.
Livespace CRM3Watch Created Companies

Watch Created Companies

Scheduled trigger

In Make“Triggers when a company is added.”

Brings every newly added company into your scenario, a handy starting point when other tools need to know about a new account the moment sales records it.

How it fires
scheduled. On each run, Make looks for companies added to Livespace CRM since the last check.
When to use it
a new account should get a folder in your file storage, a row in a reporting sheet or a welcome task for the account owner.
Watch out
it only sees new companies; edits to an existing company go through Watch Modified Companies, so pick the right one before you build the rest of the flow.
Livespace CRM4Watch Created Deals

Watch Created Deals

Scheduled trigger

In Make“Triggers when a deal is added.”

Starts your scenario with each deal created in Livespace CRM, which is the cleanest way to react to fresh opportunities entering the pipeline.

How it fires
scheduled. Make checks for new deals at the interval set on the scenario, not the instant a rep saves one.
When to use it
every new opportunity should trigger a qualification task, a message to a sales channel or a first note with context pulled from another app.
Watch out
a deal changed later will not come through here again; for follow-up on existing deals, use Watch Modified Deals or the stage trigger.
Livespace CRM5Watch Created Persons

Watch Created Persons

Scheduled trigger

In Make“Triggers when a person is added.”

Passes each new contact person added to the CRM into your scenario, so your email tool, your support desk or your onboarding list can learn about them too.

How it fires
scheduled. Make polls Livespace CRM for persons created since the previous run of the scenario.
When to use it
a contact entered by sales should be added to a newsletter list or get a personal follow-up task from the account owner.
Watch out
if you also create persons from Make with Create a Person, this trigger will pick those up too; make sure the scenario does not loop back and create them again.
Livespace CRM6Watch Modified Companies

Watch Modified Companies

Scheduled trigger

In Make“Triggers when a company is modified.”

Catches companies whose record was edited, which keeps the copies of account data you hold in other tools in step with the CRM.

How it fires
scheduled. Each time the scenario runs, Make asks Livespace CRM which companies changed since the last check.
When to use it
your billing tool or a shared spreadsheet holds company details and must follow when sales corrects an address or a name.
Watch out
if the same scenario writes back to the company with Update a Company, that edit will most likely count as a new change and come back through the trigger; add a filter so edits made by Make are skipped.
Livespace CRM7Watch Modified Deals

Watch Modified Deals

Scheduled trigger

In Make“Triggers when a deal is modified.”

Returns deals that were edited in any way, a broad net for syncing deal data to a report, a forecast sheet or another team's tool.

How it fires
scheduled. Make checks Livespace CRM for modified deals on the scenario's clock, then processes each one as a bundle.
When to use it
you need a mirror of your pipeline elsewhere and any change, whether value, owner or date, should be reflected there.
Watch out
because every edit counts, this trigger can send far more bundles than the stage or closed triggers; choose one of those when only a specific moment matters.
Livespace CRM8Watch Modified Persons

Watch Modified Persons

Scheduled trigger

In Make“Triggers when a person is modified.”

Brings in contact persons whose record changed, so a new email address or phone number entered in Livespace reaches the other tools that use it.

How it fires
scheduled. On every run, Make collects the persons updated in Livespace CRM since its previous check.
When to use it
your mailing tool, helpdesk or a partner portal keeps its own copy of contacts and should stay aligned with sales.
Watch out
writing to the same person with Update a Person inside this scenario most likely counts as another modification; filter those out or the scenario feeds itself.
Livespace CRM9Watch Stage Changes in Deals

Watch Stage Changes in Deals

Scheduled trigger

In Make“Triggers when a deal's stage has been changed.”

Fires on the moment most sales automations care about: a deal moving from one pipeline stage to another. Your scenario gets the deal that moved.

How it fires
scheduled. Make checks Livespace CRM for stage changes each time the scenario runs, every 15 minutes on a new scenario.
When to use it
reaching a stage like "proposal" should create a task, notify a manager or add a cost line, with a different branch per stage if needed.
Watch out
test with Run once to see exactly what a stage change sends before you build branches on its data.
Modules

Actions and searches: what Make can do in Livespace CRM

Livespace CRM gives you 24 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Livespace CRM1

Add a Cost to a Deal

Action

In Make“Adds a cost to a deal.”

Records a cost against a deal, so margins in Livespace reflect what a sale really takes, whether that is travel, a subcontractor or a license.

When to use it
an expense approved in another tool belongs to a client deal and should show up there without retyping.
Watch out
run List Costs first if the same expense might be sent twice, otherwise the deal ends up with a duplicate line.
Livespace CRM2

Add a Product to a Deal

Action

In Make“Adds a product item to a deal.”

Attaches a product item to an existing deal, which keeps the deal's content accurate when the order is built somewhere else, such as a quote tool or a web form.

When to use it
a customer picks options online and the matching products should land on their deal automatically.
Watch out
the product has to exist in Livespace; List Products shows what is available before you map anything.
Livespace CRM3

Create a Company

Action

In Make“Creates a company.”

Adds a new company record to Livespace CRM, giving every lead from outside the CRM an account to hang deals, notes and people on.

When to use it
a signup, a trade-show list or a partner referral arrives and the company is not in your CRM yet.
Watch out
a duplicate company is easy to create; search with List Companies before this module and create only when the search comes back empty.
Livespace CRM4

Create a Deal

Action

In Make“Creates a deal.”

Opens a new deal in your pipeline from data held elsewhere, so an inbound request becomes a tracked opportunity without a rep typing it in.

When to use it
a quote request form, a booked meeting or a chat conversation should start a deal right away.
Watch out
if Watch Created Deals runs in another scenario, deals made here will start that scenario too, which is often what you want but worth knowing.
Livespace CRM5

Create a Note for a Company

Action

In Make“Creates a note for a company.”

Writes a note on a company record, a simple way to keep account history in the CRM even when the information comes from support, billing or a survey.

When to use it
a support ticket closes or a satisfaction answer comes in, and the account owner should see it on the company page.
Watch out
keep the note short and dated in its text; many automatic notes on one company quickly bury the useful ones.
Livespace CRM6

Create a Note for a Deal

Action

In Make“Creates a note for a deal.”

Adds context straight onto a deal, so whoever opens it sees what happened without digging through email or another app.

When to use it
a deal closes and you want the signature date, the source or a summary from your form tool written on it.
Watch out
it pairs well with Watch Closed Deals, but map the deal from the trigger, not a fixed value, or every note lands on one deal.
Livespace CRM7

Create a Note for a Person

Action

In Make“Creates a note for a person.”

Stores a note on a contact person, handy for recording interactions that happen outside Livespace, like a webinar attended or a reply to a campaign.

When to use it
your marketing tool knows something about a contact that the rep should read before the next call.
Watch out
you need the right person first; a Get a Person or List Persons step upstream avoids writing on the wrong contact.
Livespace CRM8

Create a Person

Action

In Make“Creates a person.”

Adds a new contact person to the CRM, turning a signup or a business card scan into a record that sales can work with.

When to use it
a lead fills in a form, registers for an event or books a meeting, and should become a person in Livespace.
Watch out
check with List Persons first, since a contact entered twice splits their history across two records.
Livespace CRM9

Create a Task

Action

In Make“Creates a task.”

Puts a to-do on someone's list in Livespace CRM, which is how an automation turns a signal into a clear next step for a person.

When to use it
a deal changes stage, a new company appears or a key action is completed, and a rep must act on it.
Watch out
a trigger that returns many deals at once creates one task per deal; test with Run once before switching the scenario on.
Livespace CRM10

Get a Company

Action

In Make“Return details of a company.”

Fetches the full record of one company, so later modules can use details the trigger did not include, without asking you for anything else.

When to use it
you start from a deal or a person and need the related company's information for a message or a document.
Watch out
it reads a single company you already point to; when you only have a name, List Companies is the module to search with.
Livespace CRM11

Get a Deal

Action

In Make“Return details of a deal.”

Pulls every detail of one deal into the scenario, useful when a trigger or another app only hands you a reference to it.

When to use it
a completed action or a note arrives, and you need the deal's full data to decide what happens next.
Watch out
it returns one deal, not a list; to go through several deals, start with List Deals instead.
Livespace CRM12

Get a Person

Action

In Make“Returns details of a person.”

Loads the complete record of one contact person, so you can personalize an email or fill a document with data stored in the CRM.

When to use it
your scenario knows which person it is dealing with and needs more than the trigger provided.
Watch out
it reads, it never changes anything; to correct the contact afterward, add Update a Person.
Livespace CRM13

Log a Call for a Company

Action

In Make“Creates a call log for a company.”

Adds a call entry to a company's history, so conversations held on a phone system outside Livespace still appear in the account timeline.

When to use it
your calling tool reports a finished call with a company line and the account view should show it.
Watch out
if the caller is a known contact, Log a Call for a Person places the call on that person instead, which is often clearer for the rep.
Livespace CRM14

Log a Call for a Person

Action

In Make“Creates a call log for a person.”

Records a call on a contact person, keeping the sales team's picture of who spoke to whom accurate without manual entry.

When to use it
a call ends in your phone or meeting tool and it matches a person already in the CRM.
Watch out
find the person first with List Persons; a call logged on the wrong contact misleads the next rep who reads it.
Livespace CRM15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Livespace CRM API to your scenario, using the same connection, for anything the other Livespace modules do not cover.

When to use it
you need an object or an operation that has no dedicated module and the Livespace API documentation describes it.
Watch out
you write the request yourself, so keep the API docs open and test each call with Run once before relying on it.
Livespace CRM16

Send a Notification to an User

Action

In Make“Sends notification to an user.”

Pings a Livespace user directly inside the CRM, a light way to alert a rep or a manager without adding another chat channel.

When to use it
a big deal closes, a key account changes or a task was created for someone who should know right now.
Watch out
too many alerts get ignored; keep this for moments that need action and use notes for the rest.
Livespace CRM17

Update a Company

Action

In Make“Updates a company.”

Changes an existing company record, so corrections made in billing, support or enrichment tools also reach the CRM.

When to use it
another system is the reference for an address or a company name and Livespace should follow it.
Watch out
an update inside a scenario started by Watch Modified Companies triggers that scenario again; filter out edits coming from Make.
Livespace CRM18

Update a Deal

Action

In Make“Updates a deal.”

Edits a deal already in your pipeline, letting outside events such as a signed contract or a paid invoice move the deal's data forward.

When to use it
your e-signature or accounting tool knows something the deal should reflect, without waiting for a rep.
Watch out
point it at a test deal and check the result with Run once before it touches your live pipeline.
Livespace CRM19

Update a Person

Action

In Make“Updates a person.”

Modifies a contact person, the right move when a newer email, title or phone number shows up in another tool.

When to use it
a contact updates their profile in a portal or a form, and the CRM should follow.
Watch out
paired with Watch Modified Persons on the same record, it makes the scenario restart itself; add a filter to stop that.
Livespace CRM20

List Companies

Search

In Make“Searches for companies.”

Searches your companies and returns zero, one or several matches, each one as its own bundle for the next modules.

When to use it
before creating a company, to check whether it already exists, or to build a list for a report.
Watch out
every match runs the following modules once, so a loose search can multiply operations; narrow it before adding actions.
Livespace CRM21

List Costs

Search

In Make“List costs.”

Retrieves cost entries from Livespace, which helps you check or report what has been spent on deals without exporting by hand.

When to use it
you want a cost summary in a spreadsheet, or to avoid adding the same cost to a deal twice.
Watch out
results come back as separate bundles; add an aggregator from Make's tools if you need one total instead of many rows.
Livespace CRM22

List Deals

Search

In Make“Searches for deals.”

Finds deals matching your search and sends each one down the scenario, the starting point for bulk checks and pipeline reports.

When to use it
you need every deal in a certain situation, for example to review them or sync them to a sheet.
Watch out
the search can bring back nothing, one deal or dozens; check how many bundles arrive with Run once before adding actions.
Livespace CRM23

List Persons

Search

In Make“Searches for persons.”

Looks up contact persons in the CRM and returns the matches, which is how a scenario finds out whether someone is already known.

When to use it
a form, an email or a call gives you a contact, and you must decide between Create a Person and Update a Person.
Watch out
several people can match; check how many bundles came back with Run once before writing to one of them.
Livespace CRM24

List Products

Search

In Make“List products.”

Returns the products stored in Livespace, the reference list you need before placing an item on a deal from another tool.

When to use it
an order or a quote built elsewhere must be matched to your Livespace catalog before Add a Product to a Deal runs.
Watch out
each product arrives as its own bundle, so place this search where it runs once, not inside a loop over deals.
Need help

Need help automating Livespace CRM with Make?

A person reads every message.

FAQ

Livespace CRM and Make: common questions

01Is the Livespace CRM Make integration free?
Yes, Livespace CRM is a standard app in Make, so you can use it on the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between 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, remove the cap on active scenarios and count usage in credits each month. You still need your own Livespace CRM subscription, which Make does not provide.
02What do you need to connect Livespace CRM to Make?
You need an active Livespace CRM account and its API credentials. In Livespace, go to Account settings, click API in the sidebar, then Users of your Livespace account, and copy both the API key and the API secret. In Make, add a Livespace CRM module, click Create a connection, give it a name if you like and paste the two values. That single connection then works for every Livespace module in all your scenarios.
03Do Livespace CRM triggers in Make fire instantly?
No. All 9 Livespace CRM triggers are scheduled: Make checks the CRM each time the scenario runs and collects what changed since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. For most sales follow-ups that delay is fine. If a step truly cannot wait, start it from another app that calls Make instead.
04What if a Livespace CRM module is missing in Make?
Use Make an API Call. It sends any request the Livespace CRM API accepts, reusing the connection you already created, so you are not limited to the listed modules. Check the Livespace API documentation for the exact request, then test it with Run once. If what you need is on the Make side, like merging results into one total, the built-in Make tools such as aggregators handle it alongside the Livespace modules.
05Should you use Make or n8n for Livespace CRM?
It depends on the tool your team already runs. On Make, Livespace CRM comes with 33 ready modules, including 9 triggers on deals, companies and people, and a visual editor where you test with Run once. n8n is another automation platform, and many apps have a node there too; check its catalog for Livespace before choosing it. Pick the platform your team knows, then build the same scenario on it.
Same platform

Other docs you might need on this stack.

Browse all integrations