Resources · Make integration

Scopi Make integrationAutomate Scopi with Make.

Can Make keep your Scopi projects, phases and finances moving without code? The Scopi Make integration gives you 31 modules: 19 actions and 12 searches. This page explains what each one does, how to link your account and how to build a first scenario.

Try the Scopi integration on Make See the 31 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scopi Make integration do for your team?

The Scopi Make integration links your Scopi account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. Scopi brings 31 modules to that chain, to read, create and update projects, processes, phases, actions, finances and indicators.

A new stage opened from another tool. When a project moves forward in your CRM, Create a Project Phase adds the matching step in Scopi, and Create a Phase Action puts the first to-do inside it.

The right people told. List Project Team returns the people on a project; the next module can post a note to them in your chat app or add them to a sheet.

Finances kept in step. List Project Finances pulls the finances recorded on a project, and Update a Finance corrects one of them when the source changes in your accounting tool.

Two limits to know before you start. Scopi has no trigger in Make, so a scenario starts on its schedule or on a module of another app. The Make documentation for Scopi is also flagged as limited, so Make an API Call is the fallback for anything the modules miss. The same app may exist on n8n as well: n8n vs Make compares the two tools, Make pricing explains how operations are counted on each plan, and Make training helps if this is your first scenario.

Connect

How do you connect Scopi to Make?

01
Add a Scopi module
Open your scenario, click the +, type Scopi in the search box and pick any module, List Projects for instance. All Scopi modules share the same connection, so this step happens only once.
02
Create the connection
Click Create a connection. Giving it a name is optional, but a clear one (the team or the workspace it belongs to) saves confusion once several accounts sit side by side in Make.
03
Authorize and save
Make then asks you to authorize access on the Scopi page, or to paste the key Scopi gives you, depending on what the window shows. Click Save and the fields of the module open.

First scenario

Build your first Scopi scenario

GoalWhen a deal moves forward in your CRM, Make opens the matching phase on your Scopi project and puts its first action inside it.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Pick your CRM and the trigger that fires when a deal changes stage: Scopi has none of its own, so another app starts the flow.
02
Add Create a Project Phase
Click the + on the right, search Scopi and choose Create a Project Phase. Select your connection, pick the project in the list Make shows, then map the deal data from the first module into the fields.
03
Chain Create a Phase Action
Add Create a Phase Action after it and map the phase the previous module just created, so the to-do lands in the new stage. If you do not see it in the list, Run once shows what that bundle holds.
04
Test with Run once
Move a test deal in your CRM, then click Run once. Open the bubble above each module to read the bundles it received and check in Scopi that the phase and its action are there.
05
Switch it on
Switch the scenario on. If your CRM module is a scheduled trigger, open its clock first: every 15 minutes by default, never shorter on the Free plan.

Modules

What each Scopi module does

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

Scopi1

Create a Phase Action

Action

In Make“Creates an action for a specific phase.”

Adds a new action inside the phase you pick, so the work planned for that step shows up in Scopi without anyone typing it.

When to use it

a request arrives through a form or a ticket and should become a to-do in the current phase.

Watch out

the action lands in the phase you map; take it from a List Project Phases result rather than guessing, or the task ends up in the wrong step.

Scopi2

Create a Process Finance

Action

In Make“Creates an finance for a specific process.”

Records a new finance on a process, which keeps the money side of an ongoing activity next to the process itself.

When to use it

an expense or a budget is approved in another tool and must be tracked on the process it belongs to.

Watch out

this module writes to a process, not a project; for project spending, pick Create a Project Finance.

Scopi3

Create a Process Phase

Action

In Make“Creates an phase for a specific process.”

With this module, a process gains a new phase in Scopi, the stage that will then hold its own actions.

When to use it

a process gets an extra stage after a decision logged elsewhere, such as a validation step added to onboarding.

Watch out

creating the phase does not create its actions; chain Create a Phase Action right after it when the stage needs to-dos.

Scopi4

Create a Project Finance

Action

In Make“Creates an finance for a specific project.”

Your project gets a new finance entry, created straight from the scenario instead of by hand in Scopi.

When to use it

a purchase order or an invoice approved in your accounting tool should appear on the project it pays for.

Watch out

placed after a search, it runs once per bundle and can create several entries; test with Run once before switching the scenario on.

Scopi5

Create a Project Phase

Action

In Make“Creates an phase for a specific project.”

Opens a new phase on a Scopi project, giving the next stage of the work a place to live.

When to use it

a deal or a ticket moves forward in another app and the matching stage should exist in Scopi.

Watch out

this is the project version; processes have their own module, Create a Process Phase, and the two are not interchangeable.

Scopi6

Get a Finance

Action

In Make“Retrieves a finance.”

Fetches one finance on its own, so later modules can read it or pass its data along.

When to use it

you already know which finance you need, for example one returned by List Project Finances, and want its full record before you change it.

Watch out

it returns a single item; to go through every finance of a project, start from the list module instead.

Scopi7

Get an Action

Action

In Make“Retrieves an action.”

Reading one action in full is the whole job here: the module pulls it from Scopi as a single bundle.

When to use it

a scenario must check a specific to-do before sending a reminder or editing it with Update an Action.

Watch out

Get an Action reads one action; for all the actions of a phase, List Phase Actions is the right pick.

Scopi8

Get an Indicator

Action

In Make“Retrieves an indicator.”

Pulls one indicator out of Scopi so its data can travel to a report, a spreadsheet or a message.

When to use it

a single indicator matters to a meeting or a dashboard and should be copied out of Scopi when the scenario runs.

Watch out

to scan every indicator, use List Indicators first; this module is for the one you have already chosen.

Scopi9

Get a Phase

Action

In Make“Retrieves a phase.”

Gives the scenario the complete record of one phase, handy when later modules need its details.

When to use it

just before adding an action with Create a Phase Action, or before editing the stage with Update a Phase.

Watch out

map the phase from an earlier module rather than typing it; that way the scenario always reads the stage it was given.

Scopi10

Get a Process

Action

In Make“Retrieves a process.”

Retrieves one process from Scopi as a single bundle, ready for the next module to read.

When to use it

a scenario that reacts to an event about a process needs its context first, before listing its phases or its team.

Watch out

to find a process you do not know yet, run List Processes and pick the right one from its results.

Scopi11

Get a Process Cycle

Action

In Make“Retrieves a process cycle.”

Returns one cycle of a process, the single record you target instead of the whole history.

When to use it

you follow one run of a recurring process and want to copy its data to a report or a message.

Watch out

pick the cycle from List Process Cycles first; this module reads the cycle you point to, never the full list.

Scopi12

Get a Project

Action

In Make“Retrieves a project.”

A single Scopi project, in full, is what comes back from this module.

When to use it

an event in another app names a project and the scenario needs the Scopi record before creating a phase or a finance on it.

Watch out

one project per run; if the scenario must cover them all, place List Projects before it instead.

Scopi13

List Process Finances

Action

In Make“Retrieves a list of finances from a specified process.”

Retrieves the finances attached to one process, so the scenario can read, export or compare them.

When to use it

the money side of a process should be copied to a spreadsheet or checked against your accounting tool.

Watch out

it covers processes only; for a project, List Project Finances is the matching module.

Scopi14

List Project Finances

Action

In Make“Retrieves a list of finances from a specified project.”

Gathers the finances recorded on one project, the base for any export or correction.

When to use it

a project review needs its finances in a sheet, or Update a Finance has to fix one of them.

Watch out

choose the project first, with Get a Project or List Projects, so the list comes from the right place.

Scopi15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Scopi API from your scenario, with the connection you already created.

When to use it

none of the other modules covers what you need, such as writing to objectives, which the list only reads.

Watch out

you must know the endpoint you target; the Make documentation for Scopi is flagged as limited and does not describe the API.

Scopi16

Update a Finance

Action

In Make“Updates a finance.”

Changes an existing finance in Scopi instead of creating a duplicate next to it.

When to use it

the source record changes in your accounting tool and the project or process finance must follow.

Watch out

the new values replace the old ones; test with Run once on a single finance before the scenario touches them all.

Scopi17

Update an Action

Action

In Make“Updates an action.”

Edits an action that already exists, which keeps Scopi in line with the tool where the work really happens.

When to use it

a task is closed or handed over in your project tool and the matching Scopi action should say the same.

Watch out

map the action from Get an Action or List Phase Actions so the right one is edited.

Scopi18

Update an Indicator

Action

In Make“Updates an indicator.”

Writes fresh data into an indicator already set up in Scopi, so nobody copies it over by hand.

When to use it

a figure computed in a spreadsheet or a business app should land on its Scopi indicator.

Watch out

find the indicator with List Indicators or Get an Indicator first; this module never creates a new one.

Scopi19

Update a Phase

Action

In Make“Updates a phase.”

Modifies a phase already present on a project or a process, without a manual edit in Scopi.

When to use it

the plan changes in another tool and the Scopi stage should reflect it.

Watch out

this module edits only; to add a stage, use Create a Project Phase or Create a Process Phase.

Scopi20

List Divisions

In Make“Retrieves all divisions.”

Returns all the divisions of your Scopi account, each one as a separate bundle.

When to use it

a scenario routes data per division, or copies the list to a sheet other teams rely on.

Watch out

as a search, it can return zero, one or several bundles, and every module placed after it runs once per division.

Scopi21

List Indicators

In Make“Retrieves all indicators.”

Every indicator in Scopi comes out of this search, ready to be sorted or exported.

When to use it

you build a report that gathers all indicators in one sheet or one message.

Watch out

with many indicators, the modules after it run many times, and each run is an operation counted on your plan.

Scopi22

List Objectives

In Make“Retrieves all objectives.”

Fetches all the objectives stored in Scopi, and it is the only module of the app that reads them.

When to use it

a strategy review needs the list outside Scopi, in a document or a team channel.

Watch out

there is no Get, Create or Update module for objectives; anything beyond reading goes through Make an API Call.

Scopi23

List Phase Actions

In Make“Retrieves a list of actions from a specified phase.”

Brings back the actions of one phase, so the scenario can handle each to-do on its own.

When to use it

you want a digest of what is left in a stage, or to edit each of its actions with Update an Action.

Watch out

choose the phase first; the search works on one phase at a time.

Scopi24

List Process Cycles

In Make“Retrieves a list of cycles from a specified process.”

Sends back the cycles of a given process, one bundle per cycle.

When to use it

you compare the runs of a recurring process, or pick one to read in full with Get a Process Cycle.

Watch out

a search can return nothing; a process without cycles produces no bundle, and the modules after it have nothing to work on.

Scopi25

List Processes

In Make“Retrieves all processes.”

Lists all the processes in Scopi, the starting point when the scenario must go through each of them.

When to use it

you need phases, cycles or teams for every process, not just one.

Watch out

chaining it with other list modules multiplies the runs; test with Run once and count the bundles before switching the scenario on.

Scopi26

List Process Phases

In Make“Retrieves a list of phases from a specified process.”

Gets the phases of one process as separate bundles, one per stage.

When to use it

you want to add an action to each stage of a process, or copy its structure to a planning sheet.

Watch out

for the phases of a project, use List Project Phases; this search only reads processes.

Scopi27

List Process Team

In Make“Retrieves a team from a specified process.”

Tells the scenario who is on a process by returning its team.

When to use it

a message or an email should reach everyone working on a process, sent by the next module.

Watch out

this search reads the team, it does not change it; the app offers no module to add or remove members.

Scopi28

List Project Phases

In Make“Retrieves a list of phases from a specified project.”

Pulls the phases of a project, each as its own bundle, which makes it the natural second step after List Projects.

When to use it

you follow project progress in another tool and need every stage listed there.

Watch out

it reads one project per run, so pair it with a module that provides the project.

Scopi29

List Projects

In Make“Retrieves all projects.”

Hands the scenario all your Scopi projects, one bundle each.

When to use it

the scenario has to act on every project, for example to list their phases or their finances.

Watch out

on a busy account this means many bundles and many operations; test with Run once before turning the schedule on.

Scopi30

List Project Team

In Make“Retrieves a team from a specified project.”

Shows who works on a given project by returning its team.

When to use it

a status update from another tool must go to the people on the project, not to the whole company.

Watch out

List Process Team is the counterpart for processes; pick the one that matches where people are assigned.

Scopi31

List Users

In Make“Retrieves all registered users.”

Pulls the full list of people registered in your Scopi account.

When to use it

you keep a directory in a spreadsheet, or check that everyone in your HR tool also has a Scopi account.

Watch out

it reads users only; no module creates or changes one, so Make an API Call would be the route for that.

Need help

Need help automating Scopi with Make?

A person reads every message.

FAQ

Scopi and Make: common questions

01Is the Scopi Make integration free?

Yes. Scopi is a standard app, so its modules work on the Make Free plan. That plan allows 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. Every run of a module on one bundle is an operation, and your plan counts them. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution.

02What do you need to connect Scopi to Make?

A Scopi account and a Make account; the Make documentation lists no other prerequisite. Add any Scopi module, click Create a connection, name it if you like, then authorize Make on the Scopi page or paste the key Scopi provides, and click Save. The connection is stored once and reused by all 31 modules, so you never repeat the step inside a scenario. If it fails, sign in to Scopi again with the account that should own the automation and retry.

03Can Scopi trigger a Make scenario in real time?

No. Scopi has no trigger module in Make, neither scheduled nor instant, so a scenario that works with Scopi starts in one of two ways. The first is a schedule: the clock on the first module runs it every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. The second is a trigger from another app, such as a form whose instant trigger calls Make through a webhook as soon as someone submits it, followed by your Scopi modules.

04What if a Scopi module is missing in Make?

Use Make an API Call. This module reaches any endpoint of the Scopi API with the connection you already have, so it covers what the 31 listed modules leave out, provided the API offers it. Keep in mind that the Make documentation for Scopi is marked as limited, for lack of public information about the app, so you need to know the endpoint you target. If the API does not offer what you need either, the data has to come from another app in the scenario.

05Make or n8n for Scopi?

It depends on where your other automations already live. On Make, Scopi comes with 31 ready modules, 19 actions and 12 searches, plus Make an API Call for the rest, all built in the scenario editor. The same app may also have an n8n node, so compare its operations with your needs before choosing. The fair test is simple: write down the scenario you want first, then check which tool covers each of its steps without custom calls. Keeping Scopi next to your other automations also avoids splitting them across two tools.

Add a Scopi module

Create the connection

Authorize and save

Create the scenario

Add Create a Project Phase

Chain Create a Phase Action

Test with Run once

Switch it on

Need help automating Scopi with Make?