Resources · Make integration

Valuecase Make integrationAutomate Valuecase with Make.

What can the Valuecase Make integration do for your Spaces? Make offers 15 Valuecase modules: 3 triggers, 6 actions and 6 searches. This guide shows how to link your account and build a first working scenario, one click at a time.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Valuecase Make integration let you automate?

The Valuecase Make integration links your Valuecase account to Make, a no-code tool where you chain modules into a scenario. A scenario is the automation you build; a module is one brick of it, like a trigger that watches for new Spaces or an action that creates one. You get Spaces that react to the rest of your stack without anyone copying data by hand.

Open a Space from your CRM. When a record in another app reaches the right stage, Create a Space builds the Valuecase Space, then Add an External ID to Space stamps it with the CRM ID. Later, List Spaces by External ID finds that Space again from the CRM side.

Follow progress without opening Valuecase. Watch Completed Task and Watch Completed Form start a scenario when your contact finishes something. Pair them with List All Outstanding Tasks for a Space to see what is still open and pass that list to your team chat or your CRM.

Keep Space data tidy. Update a Custom Property of a Space writes a value you track in Valuecase, and Update a Space changes the owner or archives the Space once the work is done.

A limit to know: all three triggers are scheduled, so Make checks Valuecase on the scenario's schedule rather than hearing from it instantly. When a listed module does not cover your need, Make an API Call reaches other endpoints of the Valuecase API with the same connection. To weigh this setup against the alternative, read the n8n vs Make comparison, and check Make pricing before you switch several scenarios on.

Connect

How do you connect Valuecase to Make?

  1. 01

    Get your OAuth credentials in Valuecase

    In Valuecase, go to Admin Settings, then API & Custom Apps. If Valuecase asks for a callback URI, paste https://www.integromat.com/oauth/cb/valuecase. Copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a Valuecase module in Make

    Log in to Make, open your scenario and add any Valuecase module. Click Create a connection. A connection is your Valuecase account linked to Make once, then reused by every Valuecase module you add later.

  3. 03

    Name and save the connection

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the credentials you copied from Valuecase, or follow the on-screen instructions, and save. Make can now read your Spaces.

First scenario

Your first scenario with Valuecase

GoalWhen a task is completed in Valuecase, Make lists the tasks still open in that Space.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Valuecase and pick Watch Completed Task as your first module.

  2. 02

    Link your account

    Click Create a connection and paste your Valuecase credentials. Once the connection exists, Make can read your account and fill in the options the trigger needs.

  3. 03

    Add the task search

    Click the + on the right of the trigger and add List All Outstanding Tasks for a Space. Map the Space from the completed task into it, so the search looks at the right Space.

  4. 04

    Test with Run once

    Complete a test task in Valuecase, then click Run once. Open the bubbles above each module to read the bundles: a bundle is one item, here one task, passed from a module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario runs every 15 minutes by default; the Free plan cannot go lower than that. Switch the scenario on and it keeps watching.

Triggers

Valuecase triggers in Make

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

Valuecase1Watch Completed Form

Watch Completed Form

Scheduled trigger

In MakeTriggers when a new completed task is discovered.

Watch Completed Form starts your scenario when Make finds a newly completed item in Valuecase, so the answers your contact gave can move on to the next tool. Each new find arrives as one bundle you can map into later modules.

How it fires
scheduled. Make checks Valuecase on the scenario's schedule, not the moment the form is sent.
When to use it
a qualification form in a Space whose answers belong in your CRM or in a shared sheet.
Watch out
the official description of this module mentions completed tasks, not forms, so run it once on a test Space to see what it returns.
Valuecase2Watch Completed Task

Watch Completed Task

Scheduled trigger

In MakeTriggers when a new completed task is discovered.

Watch Completed Task gives you a signal each time a task gets ticked off in Valuecase. Every completed task found becomes one bundle, carrying what you need to act on it in the next module.

How it fires
scheduled. Make checks Valuecase on the scenario's schedule, so a task done a few minutes ago shows up at the next check.
When to use it
your contact has signed off a step of the plan and the account owner should hear about it without logging in.
Watch out
each check that finds tasks costs operations, meaning executions of a module counted on your Make plan.
Valuecase3Watch Created Space

Watch Created Space

Scheduled trigger

In MakeTriggers when a new Space is discovered.

Watch Created Space lets the rest of your tools know that a new Space exists in Valuecase. Each Space it finds arrives as a bundle, ready to be logged, tagged or pushed to another app.

How it fires
scheduled. Make checks Valuecase for new Spaces at the rhythm set on the scenario's clock.
When to use it
someone on the team opens Spaces by hand and you want each one recorded in the CRM with its link.
Watch out
if your scenario also creates Spaces with Create a Space, this trigger will pick those up too, so filter them out or keep the flows apart.
Modules

Valuecase actions and searches in Make

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

Valuecase1

Add an External ID to Space

Action

In MakeSets integration properties of a Space (e.g. HubSpot Deal ID, etc.).

Add an External ID to Space ties a Valuecase Space to the matching record elsewhere, such as a HubSpot deal ID. Once the ID is stored, other scenarios can find the Space from that record.

When to use it
right after Create a Space, while the CRM ID is still in the scenario.
Valuecase2

Complete a Task

Action

In MakeMarks an Action Plan Task as Completed.

Complete a Task ticks off an Action Plan task in Valuecase from another tool. The plan stays in step with what really happened, even when the proof lives outside Valuecase.

When to use it
a contract gets signed in your e-signature tool and the matching step in the Space should close on its own.
Watch out
you need the task first, so place List All Outstanding Tasks for a Space before it.
Valuecase3

Create a Space

Action

In MakeCreates a new Valuecase Space.

Create a Space opens a fresh Valuecase Space from data sitting in another app. Nobody has to rebuild it by hand when a new deal or customer shows up.

When to use it
a deal reaches a given stage in your CRM and the account team wants the Space ready.
Watch out
a Watch Created Space trigger in another scenario will see this new Space too.
Valuecase4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the way out when none of the listed modules does what you need. It calls any endpoint of the Valuecase API, reusing the connection you already made.

When to use it
you need a Valuecase feature that has no dedicated module in Make.
Watch out
you build the request yourself, so keep the Valuecase API documentation open while you set it up.
Valuecase5

Update a Custom Property of a Space

Action

In MakeSets Custom Property value on an existing Space.

Update a Custom Property of a Space writes a new value into one of the custom properties of an existing Space. Your Spaces carry the same facts as your other tools, without retyping.

When to use it
a deal amount or a renewal status changes in the CRM and the Space should show it.
Watch out
check the property names first with List all Custom Properties for a Space.
Valuecase6

Update a Space

Action

In MakeAllows you to change the owner of a Space or archive it.

Update a Space handles two housekeeping jobs: giving the Space a new owner or archiving it. Handovers and closed deals stop cluttering the list of active Spaces.

When to use it
an account moves to another rep, or the deal is marked lost or won in your CRM.
Watch out
test the archive on a dummy Space before switching the scenario on.
Valuecase7

Get a Space by Slug

Search

In MakeGets a Space in Valuecase by its slug.

Get a Space by Slug fetches one Space from the slug in its address. It is the quickest path when a link to the Space is all your other tool holds.

When to use it
a teammate pastes a Space link into a form or a ticket and the scenario needs the Space details.
Watch out
the slug is only the last part of the link, not the full URL.
Valuecase8

List all Custom Properties for a Space

Search

In MakeLists all Custom Properties associated with the Space.

List all Custom Properties for a Space returns every custom property tied to one Space. You see what the Space holds before you copy it elsewhere or change it.

When to use it
you want to send those values to a reporting sheet, or check a value before an update.
Watch out
as a search, it can return several bundles, one per property, so later modules run once for each.
Valuecase9

List All Forms for a Space

Search

In MakeFetches all forms (completed or not) for a particular space by space ID

List All Forms for a Space pulls every form of a Space, filled in or not. You get a clear view of what your contact has answered and what is still waiting.

When to use it
before a call, to gather form answers into a summary for the account owner.
Watch out
completed and open forms come back together, so add a filter if you only need one kind.
Valuecase10

List All Outstanding Tasks for a Space

Search

In MakeFetches all tasks that are not marked as completed for a particular space.

List All Outstanding Tasks for a Space returns the tasks of a Space that nobody has completed yet. It turns a Space into a to-do list your other tools can read.

When to use it
after a task is completed, to post what remains in your team chat.
Watch out
an empty result means everything is done, so plan what the scenario should do in that case.
Valuecase11

List External IDs by Space ID

Search

In MakeFetches external IDs associated with a Space (such as Hubspot Deal ID, etc.).

List External IDs by Space ID reads back the outside IDs stored on a Space, a HubSpot deal ID for example. From Valuecase you get the key that opens the right record in the other app.

When to use it
a Valuecase trigger fires and you need to update the matching CRM deal.
Watch out
a Space with no stored ID returns nothing, so Add an External ID to Space has to come first.
Valuecase12

List Spaces by External ID

Search

In MakeLists Spaces in Valuecase by a third party ID provided during space creation (e.g. CRM ID).

List Spaces by External ID works the other way round: from a CRM ID or another third-party ID given when the Space was created, it finds the matching Spaces in Valuecase.

When to use it
a deal changes in the CRM and you want to update or archive its Space.
Watch out
it only finds Spaces that received that ID, so set it at creation.
Need help

Need help automating Valuecase with Make?

A person reads every message.

FAQ

Questions about the Valuecase Make integration

01Is the Valuecase Make integration free?
Yes, on the Make side. Valuecase is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your Valuecase subscription is separate: you still need an active Valuecase account with API access, and its price is set by Valuecase, not by Make.
02What do you need to connect Valuecase to Make?
You need an active Valuecase account and API keys requested from Valuecase. In Valuecase, open Admin Settings, then API & Custom Apps, enter the callback URI if asked, and copy the Client ID and Client secret. In Make, add a Valuecase module, click Create a connection, give it a name if you like and paste those credentials. That one connection then serves every Valuecase module in your scenarios, so you only do this setup once per account.
03Do the Valuecase triggers in Make fire in real time?
No. All 3 Valuecase triggers are scheduled: Make checks Valuecase on the scenario's schedule and picks up what changed since the previous check. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Paid plans allow a check every minute. If you need a faster reaction, shorten the schedule on a paid plan, or start the scenario from another app that calls Make and then read Valuecase with the search modules.
04What if a Valuecase module is missing in Make?
Use Make an API Call. It is part of the 15 Valuecase modules and calls any endpoint of the Valuecase API with the connection you already set up, so you are not limited to the 6 actions and 6 searches listed. You write the request yourself from the Valuecase API documentation. The official Make documentation for this app gives no further limits, so test each new call with Run once on a test Space before you switch the scenario on.
05Should you use Make or n8n for Valuecase?
It depends on what you check first. On Make, Valuecase comes with 15 ready modules, including 3 scheduled triggers, and Make an API Call covers the rest of its API. This guide does not confirm an n8n node for Valuecase, so check on the n8n side whether one exists before you compare. Then pick the tool your team already runs and can maintain. If you are unsure, a first Make scenario on the Free plan is a cheap way to see if the modules fit.