Resources · Make integration

IC Project Make integrationAutomate IC Project with Make.

Can Make take the busywork out of IC Project? The IC Project Make integration gives you 62 modules: 44 actions and 18 searches. This page is for teams that run projects in IC Project, and it walks you from the connection to a first working scenario.

Try the IC Project integration on MakeSee the 62 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IC Project Make integration automate?

The IC Project Make integration links your IC Project account to Make, a no-code tool where you chain apps together. Make can create projects, tasks, users and finance records in IC Project, or read them to feed another tool, as soon as something happens in the rest of your stack.

Projects that open themselves. A deal marked as won in your CRM triggers Create a Project, then Create a Task and Assign Users to Task, so the team finds its work ready without a kickoff email.

Finance numbers where management reads them. List Finance Invoices and List Finance Income copy IC Project figures into a spreadsheet or a reporting tool, and nobody exports anything by hand.

Time and people kept in sync. Create a Reported Time logs hours tracked elsewhere, while Create a User and Create a Department follow arrivals recorded in your HR tool.

Two limits to know. IC Project has no trigger in Make, so a scenario starts from another app or from a schedule. And Make's own documentation for this app is limited, which is why the page sticks to what each module is for. If you prefer to learn the editor step by step, the Make training covers it; the Make pricing page explains how operations are counted, and n8n vs Make helps if IC Project also sits on your n8n shortlist.

Connect

How do you connect IC Project to Make?

  1. 01

    Add an IC Project module

    In any scenario, add a module from IC Project, for example Create a Task, and click Create a connection. A connection is your IC Project account linked to Make once, then reused by every IC Project module.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the workspace or the client it belongs to. This step is optional, but it saves guesswork when several accounts end up connected.

  3. 03

    Authorize and save

    Either authorize Make on the IC Project page that opens, or paste the key IC Project gives you, depending on what the window asks for. Then click Save: Make can now read and write in your account.

First scenario

Your first scenario with IC Project

GoalWhen a new request comes in through your form tool, Make creates a project in IC Project and adds its first task.

  1. 01

    Create a new scenario

    Open the Scenarios page and create a new scenario, the automation you are about to build. Click the + in the middle of the editor to place the first module.

  2. 02

    Start from the app that receives requests

    IC Project has no trigger, so the first module belongs to your form tool. Search it by name, pick the module that watches new entries and create its connection.

  3. 03

    Add Create a Project

    Click the + on the right of the first module, search IC Project and choose Create a Project. Connect your account, then fill the fields with data mapped from the form entry.

  4. 04

    Chain Create a Task

    Add Create a Task after it and map the project returned by the previous module, so the task lands in the project Make has just created and not in an older one.

  5. 05

    Test with Run once

    Click Run once, submit a test entry, then open each module to read the bundle it received. A bundle is one item passed from a module to the next, here one request.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval Make allows.

Modules

What the IC Project modules do

IC Project gives you 62 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

IC Project1

Assign Users to Task

ActionIn the docs only

Puts the right people on a task without anyone opening IC Project: the scenario sets the assignees for you, so work never sits unowned.

When to use it
right after Create a Task, when the owner is already known from the form or the deal that started the scenario.
Watch out
map the task from the earlier module instead of picking one by hand, or every run lands on the same task.
IC Project2

Create a Board

ActionIn the docs only

A fresh board appears in IC Project, ready to hold tasks, so a new piece of work starts organized instead of scattered across inboxes.

When to use it
each new client or internal initiative needs its own board, set up the same way every time.
Watch out
every run adds another board, so test with Run once before you switch the scenario on.
IC Project3

Create a CRM Note

ActionIn the docs only

Leaves a written trace in the CRM side of IC Project, so the context of an exchange stays in the app instead of in one person's mailbox.

When to use it
an email, a call summary or a form reply collected by another app carries information the team should find later in IC Project.
Watch out
to correct a note, send it to Update a CRM Note rather than writing a second one.
IC Project4

Create a Checklist

ActionIn the docs only

Gives a piece of work its checklist without anyone rebuilding it by hand, which keeps recurring checks identical from one project to the next.

When to use it
every new project of the same type needs the same verification steps before delivery.
Watch out
Make documents this app only briefly, so run the module once and read the bundle it returns to see where the checklist ended up.
IC Project5

Create a Contact Person

ActionIn the docs only

Your contacts stop living in a side spreadsheet: this module adds a contact person to IC Project from the data another app sends.

When to use it
a lead fills in a form or a quote is signed, and the person has to exist in IC Project before the project starts.
Watch out
each run creates a new record, so a form submitted twice gives two contacts unless the scenario weeds out the repeat first.
IC Project6

Create a Contractor

ActionIn the docs only

New subcontractors get registered in IC Project the moment they are approved elsewhere, with no copying and pasting between tools.

When to use it
a supplier onboarding form or a signed agreement in another app marks the contractor as ready to work.
Watch out
to change their details later, use Update a Contractor; running this module again produces a duplicate contractor.
IC Project7

Create a Cost Resource

ActionIn the docs only

Adds a cost resource to IC Project, so what a project consumes gets declared by the scenario instead of by someone re-typing it.

When to use it
a purchase or an expense validated in another tool must show up in IC Project for project follow-up.
Watch out
Make's documentation does not describe its fields; once your connection exists, open the module in the editor and read what it asks for before mapping.
IC Project8

Create a Department

ActionIn the docs only

Your structure in IC Project follows the one in your HR or admin tool, because the scenario creates each department for you.

When to use it
a department is opened in another system and must exist in IC Project before people are placed in it.
Watch out
a slip here duplicates part of your organization; run List Departments first to see what already exists.
IC Project9

Create a Job Position

ActionIn the docs only

The job titles your team uses become records in IC Project, created by Make rather than by an admin clicking through settings.

When to use it
HR adds a new role and you want it available in IC Project before the hire, with Create a User following once the person arrives.
Watch out
List Job Positions tells you whether the title is already there, which avoids two near-identical positions.
IC Project10

Create a Location Resource

ActionIn the docs only

Saves someone from typing the same location twice: the scenario adds a location resource to IC Project from data that already lives elsewhere.

When to use it
a new site or address is confirmed in another tool and upcoming projects will need to refer to it.
Watch out
nothing in Make's documentation describes this module's fields, so open it in the editor and read what it asks for before mapping.
IC Project11

Create a Project

ActionIn the docs only

The module most IC Project scenarios revolve around: a project is created the moment a deal is won or a request is accepted in another app.

When to use it
the signal comes from outside IC Project, since the app has no trigger in Make, and the project must exist before tasks or stages are added.
Watch out
map the project it returns into the next modules instead of searching for it again, which costs an extra operation.
IC Project12

Create a Reported Time

ActionIn the docs only

Hours worked get logged in IC Project without anyone filling in a timesheet twice, because the module records the reported time itself.

When to use it
time is already tracked in another tool, or a calendar event ends, and IC Project must reflect it for billing or follow-up.
Watch out
one bundle means one entry, so ten time slots cost ten operations, the unit Make counts on your plan.
IC Project13

Create a Stage

ActionIn the docs only

Splits a project into stages created by the scenario, so every new project starts with the same phases already in place.

When to use it
just after Create a Project, when your projects always follow the same sequence from brief to delivery.
Watch out
one module creates one stage per bundle; for several phases, add one module per phase or feed it a list through an iterator.
IC Project14

Create a Task

ActionIn the docs only

Turns an incoming request into work someone can act on: an email, a form reply or a support message becomes a task in IC Project.

When to use it
the request is clear enough to hand to someone; chain Assign Users to Task right after it.
Watch out
every bundle the first module sends becomes a task, including the test data you pushed while using Run once.
IC Project15

Create a Task Comment

ActionIn the docs only

Writes a comment on a task for you, so updates coming from other tools appear where the team already discusses the work.

When to use it
a client replies by email or a file is approved elsewhere, and whoever owns the task should see it without switching apps.
Watch out
target the task by mapping it from an earlier module; a comment on the wrong task is easy to miss.
IC Project16

Create a TaxRate

ActionIn the docs only

Adds a tax rate to IC Project, which spares you re-entering it when your accounting tool already holds the value.

When to use it
a new rate starts to apply and the finance side of IC Project has to use it too.
Watch out
tax settings deserve care; test with Run once, read the bundle, and fix mistakes with Update a TaxRate rather than a second creation.
IC Project17

Create a Ticket

ActionIn the docs only

Support requests land in IC Project as tickets without anyone forwarding them, because the scenario opens each ticket itself.

When to use it
a help form, a chat widget or a support inbox in another app receives a request the project team must handle.
Watch out
a customer who writes twice produces two tickets unless the scenario sets the second message aside.
IC Project18

Create a ToDo

ActionIn the docs only

Reminders go straight into IC Project as to-dos: the module creates one from whatever the previous module passes along.

When to use it
your team tracks small follow-ups as to-dos, for example a missing document to chase after a signature in another tool.
Watch out
once created, change it with Update a ToDo; List ToDos shows what already exists before you add more.
IC Project19

Create a User

ActionIn the docs only

New colleagues get their IC Project account from the scenario, so onboarding no longer waits for an admin to find the time.

When to use it
your HR tool or a signed contract confirms an arrival, and the person needs access on day one.
Watch out
you do not want to create users by accident; check List Users first and switch the scenario on only after a clean Run once.
IC Project20

List Boards

SearchIn the docs only

Returns the boards of IC Project as bundles, one per board, which lets the scenario find the right board before touching anything.

When to use it
a later module needs an existing board and the scenario has to look it up first.
Watch out
like any search, it can return zero, one or many boards; make sure the next module works on the one you intend.
IC Project21

List CRM Locations

SearchIn the docs only

Brings back the CRM locations stored in IC Project, each as a bundle the following modules can reuse without anyone typing it.

When to use it
a scenario needs an existing location as input, for instance before writing a CRM note about a client site.
Watch out
an empty result is normal for a search, not an error; decide what the next module should do when nothing comes back.
IC Project22

List CRM Notes

SearchIn the docs only

Pulls the notes already written in the CRM part of IC Project, so another tool, a report or a chat message, can reuse that history.

When to use it
a salesperson wants the background before a call, and the scenario sends it to the tool they actually read.
Watch out
a long history means many bundles, and each module after it runs once per note, which adds operations.
IC Project23

List Costs

SearchIn the docs only

Hands you the costs recorded in IC Project, one bundle per cost, ready to be copied into a spreadsheet or an accounting tool.

When to use it
finance wants project spending outside IC Project without an export done by hand.
Watch out
this module only reads; to change one of the costs it found, pass it on to Update a Cost.
IC Project24

List Departments

SearchIn the docs only

Tells the scenario which departments exist in IC Project, so it can place a new user or check a name before creating anything.

When to use it
just before Create a Department or Create a User, as a safety check against duplicates.
Watch out
zero results means nothing matched, not that the module failed; plan what happens next in that case.
IC Project25

List Finance Cost Category

SearchIn the docs only

Reads the cost categories set up on the finance side of IC Project and passes them on, so incoming costs can be sorted the way your team expects.

When to use it
a cost coming from another tool has to match an existing category before it is written anywhere.
Watch out
categories rarely change, so calling this search for every bundle spends operations on the same answer; place it once, early.
IC Project26

List Finance Currencies

SearchIn the docs only

Gives the scenario the currencies configured in IC Project, so amounts from other tools can be matched to one the app knows.

When to use it
invoices or costs arrive in several currencies and IC Project must receive the right one each time.
Watch out
the output fields are not documented; run it once and look at the bundle to see how each currency is written.
IC Project27

List Finance Income

SearchIn the docs only

Takes the income recorded in IC Project out of the app, one bundle per entry, so it can feed a report or a dashboard elsewhere.

When to use it
management reads its figures in a spreadsheet and does not want to log into IC Project for that.
Watch out
if you only need a total, add an aggregator after the search to group the entries into a single bundle.
IC Project28

List Finance Income Category

SearchIn the docs only

Lists the income categories defined in IC Project, the revenue-side counterpart of List Finance Cost Category.

When to use it
a scenario has to label incoming revenue with an existing category before recording it in another system.
Watch out
category names are whatever a person typed in IC Project, so compare them carefully with the labels your other tool uses.
IC Project29

List Finance Invoices

SearchIn the docs only

Your IC Project invoices become bundles Make can send elsewhere: an accounting tool, a spreadsheet or a message to the finance team.

When to use it
invoices are issued in IC Project but paid or followed up in another system.
Watch out
the modules after it process every invoice returned, so keep only the ones you need before operations pile up.
IC Project30

List Finance Tax Rate

SearchIn the docs only

Reads the tax rates stored in IC Project so the scenario applies an existing one instead of guessing a value.

When to use it
before Create a TaxRate, to avoid adding a rate that already exists, or before sending finance data that needs one.
Watch out
a search can return several rates at once; check that the next module picks the one you mean.
IC Project31

List Finance Units

SearchIn the docs only

Returns the finance units defined in IC Project, so a scenario can reuse them instead of inventing its own labels.

When to use it
amounts from another tool come with a unit and the scenario must match it to one IC Project already knows.
Watch out
Make says little about this app, so read the bundle after Run once before relying on any value it returns.
IC Project32

List Job Positions

SearchIn the docs only

Brings back the job positions of IC Project, handy for checking a title before an onboarding scenario creates anything.

When to use it
a new person arrives and the scenario must either reuse an existing position or call Create a Job Position.
Watch out
positions with close names can come back together; decide which one the next module should use.
IC Project33

List Projects

SearchIn the docs only

Gets you the projects of IC Project as bundles, the starting point of any report or sync that covers your whole portfolio.

When to use it
a scenario starts on a schedule rather than on an event, since IC Project has no trigger in Make, and needs to go through the projects.
Watch out
each project returned runs every module that follows, so a large portfolio costs more operations per run.
IC Project34

List Projects Stages

SearchIn the docs only

Shows the stages your projects contain, so the scenario knows where things stand before it creates or updates anything.

When to use it
before Create a Stage, to avoid duplicating a phase, or to send stage progress to a report outside IC Project.
Watch out
Make's documentation does not describe what this search filters on; test it with Run once and read the bundles.
IC Project35

List Projects Tasks

SearchIn the docs only

Returns project tasks one by one, which is what you need to review open work or copy tasks into another tool.

When to use it
a team lead wants the tasks in a shared spreadsheet or summed up in a chat message.
Watch out
many tasks means many bundles; an aggregator after the search groups them into one message instead of one message per task.
IC Project36

List ToDos

SearchIn the docs only

Pulls the to-dos out of IC Project, so reminders can reach people in the tools where they actually spend their day.

When to use it
the team lives in a chat app and tends to forget what waits in IC Project.
Watch out
pair it with Update a ToDo when the scenario should also change the items it has just read.
IC Project37

List Users

SearchIn the docs only

Gives the scenario the users of IC Project, so it can find the right person to assign or to notify.

When to use it
before Assign Users to Task, when the assignee comes from a name or an email address in another tool.
Watch out
if two users share a name, both come back; pick on something more precise when you can.
IC Project38

Lists Contractors

ActionIn the docs only

Brings out the contractors registered in IC Project, so the scenario can check who is already there or share the list with another tool.

When to use it
before Create a Contractor, to avoid adding a company twice, or to send the list to a purchasing tool.
Watch out
Make classes this module as an action even though its name starts with Lists; run it once and count the bundles it returns.
IC Project39

Make an API Call

ActionIn the docs only

Covers whatever the listed modules leave out: it calls any endpoint of the IC Project API, using the connection you already set up.

When to use it
the action you need is missing from the list, or a search does not return what your scenario requires.
Watch out
you need the IC Project API documentation to write the request; if an error comes back, the Make troubleshooting guide helps you read it.
IC Project40

Move a Task to Other Column

ActionIn the docs only

Moves a task to another column of its board, which is how a scenario shows progress that happened somewhere else.

When to use it
a file gets approved, a payment arrives or a ticket closes in another tool, and the task should move forward on its own.
Watch out
Read a Kanban Tasks and Board Columns tells you which columns exist before you move anything.
IC Project41

Read a Contractor

ActionIn the docs only

Pulls the full record of one contractor from IC Project into your scenario, so the modules after it can reuse that contractor's details without anyone retyping them.

When to use it
a contractor's name shows up in data from another app and you need the matching IC Project record before writing anything.
Watch out
it reads one contractor only; to go through all of them, add Lists Contractors instead.
IC Project42

Read a Finance Project

ActionIn the docs only

Gives your scenario the finance side of one IC Project project, ready to map into a spreadsheet or reporting module further down the chain.

When to use it
a project wraps up in your workflow and the finance team wants its record copied into the tool they already use.
Watch out
IC Project's documentation on Make is limited, so click Run once and read the bundle to see exactly what comes back.
IC Project43

Read a Kanban Tasks and Board Columns

ActionIn the docs only

Brings back a board the way it looks in IC Project: its columns and the tasks sitting in each one, as data your scenario can filter or pass along.

When to use it
before moving a task, to check which column it currently sits in.
Watch out
pair it with Move a Task to Other Column rather than typing column names by hand, which breaks as soon as someone renames one.
IC Project44

Read a Project

ActionIn the docs only

Hands your scenario the details of a single project, so every module that follows can map them instead of asking you to fill them in again.

When to use it
a deal is won in your CRM and you want the matching project's data before creating tasks under it.
Watch out
this module fetches one project; List Projects is the search that returns several, one bundle each.
IC Project45

Read a Stage

ActionIn the docs only

Lets a scenario check one project stage and pass what IC Project knows about it to the next module in line.

When to use it
a routing step depends on how far a project has gone, and you want that answer straight from IC Project rather than from a copy.
Watch out
to see every stage of a project at once, List Projects Stages fits better, since each stage then arrives as its own bundle.
IC Project46

Read a Task

ActionIn the docs only

Fetches a single task with what IC Project keeps on it, ready to post in a chat channel, copy into a sheet or check with a filter.

When to use it
a comment or a time entry points to a task and you need that task's details next to it.
Watch out
each run of this module uses one operation, the unit Make counts on your plan, so avoid reading the same task again and again in one scenario.
IC Project47

Read a User

ActionIn the docs only

Returns one IC Project user to your scenario, which helps when a later module needs to know exactly who someone is before assigning or notifying them.

When to use it
right before Assign Users to Task, to confirm you picked the right person.
Watch out
when you only know part of the team, start from List Users, which hands back every user as a separate bundle.
IC Project48

Update a Board

ActionIn the docs only

Changes a board that already exists in IC Project, straight from your scenario, instead of opening the app and editing it by hand.

When to use it
a project gets renamed or reorganized in another tool and its board should follow.
Watch out
the board has to exist first; find it with List Boards, map it into this module, then test with Run once.
IC Project49

Update a CRM Note

ActionIn the docs only

Rewrites a CRM note already stored in IC Project, which keeps the client history accurate when the information changes somewhere else.

When to use it
a sales call summary gets corrected in your meeting tool and the note in IC Project should say the same thing.
Watch out
locate the note with List CRM Notes first; editing the wrong one is easy when several notes concern the same client.
IC Project50

Update a Contractor

ActionIn the docs only

Keeps a contractor's record in IC Project in step with the source you trust, without anyone copying details across by hand.

When to use it
a supplier sends new contact details through a form and you want IC Project updated as soon as the submission arrives.
Watch out
an update changes live data, so test on one contractor with Run once before switching the scenario on.
IC Project51

Update a Cost

ActionIn the docs only

Edits a cost entry that already lives in IC Project, so project spending there matches what your accounting side has recorded.

When to use it
an expense gets approved or corrected in another tool and the IC Project cost should reflect it.
Watch out
map the cost you want to change, found with List Costs, instead of picking one by hand, or every run will edit that same entry.
IC Project52

Update a Cost Resource

ActionIn the docs only

Adjusts a cost resource, the kind of item Create a Cost Resource adds, directly from a scenario so nobody has to reopen it in IC Project.

When to use it
a resource you track costs against changes in your source system and IC Project needs the same version.
Watch out
Make's documentation for IC Project is thin, so read the output bundle after Run once to confirm what the module took into account.
IC Project53

Update a Department

ActionIn the docs only

Updates a department in IC Project from inside a scenario, so your org structure reads the same in every tool your team opens.

When to use it
HR reshapes a team in its own software and IC Project should follow without a manual edit.
Watch out
List Departments returns every department as a separate bundle; add a filter so only the one you mean reaches this module.
IC Project54

Update a Job Position

ActionIn the docs only

Brings a job position in IC Project up to date when its title or scope changes in the tool where HR maintains roles.

When to use it
a role gets redefined after a reorganization and IC Project still shows the previous wording.
Watch out
find the position through List Job Positions and map it here, rather than choosing it once from a dropdown that will not follow later changes.
IC Project55

Update a Project

ActionIn the docs only

Updates a project that already exists in IC Project, so its details follow what happens in your sales or client tools.

When to use it
a client extends a contract in your CRM and the project should show the change without anyone logging in to IC Project.
Watch out
IC Project has no trigger in Make, so this scenario needs another app's trigger or Make's schedule, the clock on the first module, to start.
IC Project56

Update a Reported Time

ActionIn the docs only

Corrects a time entry someone already reported in IC Project, which keeps logged hours clean before anyone bills them.

When to use it
a timesheet is fixed in another tracker while IC Project still holds the old version.
Watch out
Create a Reported Time adds a new entry; pick this module when the entry exists already, or the hours end up counted twice.
IC Project57

Update a Stage

ActionIn the docs only

Moves a project stage's details forward from a scenario, instead of editing that stage by hand in IC Project.

When to use it
a milestone is signed off in another tool and the matching stage in IC Project should reflect it.
Watch out
add Read a Stage before it to check the current state first, a useful safeguard when several scenarios touch the same project.
IC Project58

Update a Task

ActionIn the docs only

Changes an existing task, so the version in IC Project follows the ticket, email or form where the request actually evolved.

When to use it
a client edits a request in your helpdesk and the linked task should carry the new details.
Watch out
to shift a task between board columns, Make also lists Move a Task to Other Column, the module named for that exact job.
IC Project59

Update a TaxRate

ActionIn the docs only

Edits a tax rate stored in IC Project, so the value there matches the one your accountant has validated.

When to use it
a rate changes in your accounting software and IC Project should carry the same number without a manual correction.
Watch out
List Finance Tax Rate shows the rates available; make sure the scenario points at the right one before you switch it on.
IC Project60

Update a ToDo

ActionIn the docs only

Updates a to-do in IC Project, a quick way to keep small action items in sync with the tool where the work really gets done.

When to use it
an item gets reworded in your notes app and IC Project should show the same text.
Watch out
List ToDos returns several bundles, and each one then runs this module once, which adds operations on your plan.
IC Project61

Update a User

ActionIn the docs only

Keeps a user profile in IC Project aligned with your directory or HR tool, so nobody edits the same person in two places.

When to use it
an employee changes team or contact details and IC Project should learn about it without a ticket to the admin.
Watch out
place Read a User before this module and click Run once to check the scenario targets the right person.
IC Project62

Upload a Project File

ActionIn the docs only

Sends a file into an IC Project project, so contracts, briefs or deliverables land where the team already works on them.

When to use it
an email attachment or a file dropped in cloud storage belongs to a client project and should sit next to its tasks.
Watch out
on Make's Free plan, files are capped at 5 MB, so check your plan's limit before you switch the scenario on.
Need help

Need help automating IC Project with Make?

A person reads every message.

FAQ

IC Project and Make: common questions

01Is the IC Project Make integration free?
Yes. IC Project is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution, 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 allow 40 minutes per execution. Usage is counted in operations: one module processing one bundle. Your IC Project subscription is a separate matter this page does not cover.
02What do you need to connect IC Project to Make?
An IC Project account and a Make account. Make's documentation lists no prerequisite for this app. Add any IC Project module, click Create a connection, optionally give it a name, then either authorize Make on the IC Project page that opens or paste the key IC Project provides, and save. The connection is created once and reused by all 62 modules, so pick it from the list in the next modules instead of creating a new one each time.
03Can IC Project start a Make scenario in real time?
No. IC Project has no trigger module in Make, so nothing in the app can launch a scenario on its own. You have two ways to start. Either the first module comes from another app, such as your form tool or CRM, and IC Project modules act afterward. Or the scenario runs on a schedule set on its first module, every 15 minutes by default, 15 minutes at least on the Free plan and down to 1 minute on paid plans, and a module like List Projects fetches what changed.
04What if an IC Project module is missing in Make?
Use Make an API Call. This module calls any endpoint of the IC Project API with the same connection as the other modules, so it covers what the 44 actions and 18 searches leave out. You will need the IC Project API documentation to write the request. Keep in mind that Make currently offers only limited documentation for this app, because little public information about it is available, so test each new request with Run once and read the returned bundle before relying on it.
05Should you use Make or n8n for IC Project?
It depends on which tool your team already builds in. On the Make side, the facts are simple: 62 IC Project modules, 44 actions and 18 searches, no trigger, a Make an API Call module for the rest, and access from the Free plan. Many apps also have an n8n node, so check whether IC Project has one before you decide. Neither tool is ranked here: compare what each offers for your own scenario, then build in the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations