Resources · Make integration

Celoxis Make integrationAutomate Celoxis with Make.

Can Make keep your Celoxis projects moving without code? The Celoxis Make integration gives you 27 modules: 2 scheduled triggers, 20 actions and 5 searches. This guide is for project and ops leads who want to connect the account, build a first scenario and pick the right module.

Try the Celoxis integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Celoxis Make integration automate?

The Celoxis Make integration links your Celoxis account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick (a trigger, an action or a search). Make can watch tasks in Celoxis, create or update projects, tasks, users and time entries, and pass the result to your other apps.

Projects that open themselves. When a deal is won in your CRM, Create a Project sets it up in Celoxis and Create a Task adds the kickoff work, so nobody retypes the client brief.

Time that reaches billing. List Time Entries pulls the logged hours and hands them to your invoicing or reporting tool, one bundle (one item passed between modules) per entry.

New hires ready on day one. When HR adds a person in its own tool, Create a User gives them a Celoxis account, and Watch New Task can then tell them about their first assignment.

Know the limit before you start: Make itself says its documentation for Celoxis is limited, because little public information exists about the app. Test each module with Run once before you rely on it. If you are weighing Make against another tool, read n8n vs Make; for a broader opinion of the platform, see the Make review, and if you would rather hand the build over, the Make agency team can take it.

Connect

How do you connect Celoxis to Make?

  1. 01

    Add a Celoxis module

    In your scenario, click the +, search for Celoxis and pick any module. Then click Create a connection. A connection is your Celoxis account linked to Make once and reused by every Celoxis module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, such as the workspace it points to. Make then asks you to authorize it on the Celoxis page or to paste the key Celoxis gives you; the documentation does not say which of the two Celoxis uses.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and Make can list the Celoxis items it is able to read, so you pick them instead of typing them.

First scenario

Your first scenario with Celoxis

GoalWhen a deal is won in your CRM, Make creates the project in Celoxis and adds its kickoff task.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick your CRM and the trigger that fires when a deal is won. That module starts the flow.

  2. 02

    Add Create a Project

    Click the + on the right of the CRM module, search Celoxis and choose Create a Project. Create the connection, then map the deal name and client from the CRM module into the fields Make shows.

  3. 03

    Chain Create a Task

    Add one more module with the +: Create a Task. Fill it with the kickoff work your team always starts with, and map values from the previous modules where they help.

  4. 04

    Test with Run once

    Click Run once and win a test deal, or use an existing one. Open each module's bubble to read the bundles it received, then check that the project and task appear in Celoxis.

  5. 05

    Schedule and switch on

    On the first module, open the clock of Scheduling. A new scenario runs every 15 minutes by default. Keep that or change it, then switch the scenario on.

Triggers

What starts a Celoxis scenario?

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

Celoxis1Watch New Task

Watch New Task

Scheduled trigger

In Make“Watches for new created tasks.”

Watch New Task starts your scenario with the tasks created in Celoxis since the previous check, one bundle per task, so fresh work can travel to the tools your team already reads.

How it fires
scheduled. Make checks Celoxis on the scenario's schedule, every 15 minutes by default, or as often as every minute on a paid plan. It is not instant.
When to use it
a project manager adds a task and the assignee should hear about it in the team chat, or the task should land in a shared planning sheet.
Watch out
tasks created between two checks arrive together on the next run, and each one uses operations in every module that follows.
Celoxis2Watch Task Update

Watch Task Update

Scheduled trigger

In Make“Watches for new updated tasks.”

Watch Task Update catches tasks that were edited in Celoxis, so a change to existing work can set off the rest of the scenario instead of waiting for someone to report it.

How it fires
scheduled. Make checks Celoxis on the scenario's schedule, which you set with the clock on the first module. There is no instant version of this trigger.
When to use it
a client-facing tracker or a management report must stay in step with the work, without anyone copying edits by hand.
Watch out
if this same scenario writes back to the task with Update a Task, that write is itself an update, so the next check may pick it up again.
Modules

What each Celoxis module does

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

Celoxis1

Create an App

Action

In Make“Creates a new app.”

Create an App adds a new app record to Celoxis from data another module hands over, so the object exists without anyone typing it into Celoxis.

When to use it
an item approved in another tool should appear in Celoxis as an app, the way your workspace already uses that object.
Watch out
every run creates a new one, so run List Apps first if the same source can come back twice.
Celoxis2

Create a Project

Action

In Make“Creates a new project.”

Opening a project from a won deal takes this one module: Create a Project builds the project in Celoxis with the details you map from the previous step.

When to use it
sales closes in the CRM and delivery works in Celoxis, and the handoff should not depend on someone remembering it.
Watch out
the project starts empty, so chain Create a Task right after it when every project needs the same first steps.
Celoxis3

Create a Task

Action

In Make“Creates a new task.”

Requests that arrive by form, email or ticket become real Celoxis tasks with Create a Task, one task for each bundle the module receives.

When to use it
your team takes requests outside Celoxis and wants them planned where the rest of the work lives.
Watch out
if a search placed before it returns several items, Create a Task runs once per item and creates as many tasks.
Celoxis4

Create a Time Entry

Action

In Make“Creates a new time entry.”

Hours spent elsewhere, in a calendar or a separate timer, can be logged in Celoxis with Create a Time Entry, so timesheets fill up without double entry.

When to use it
consultants track time in another app but billing and project costs are read in Celoxis.
Watch out
Run once logs a real entry; test on a sandbox project and remove it afterwards with Delete a Time Entry.
Celoxis5

Create a User

Action

In Make“Creates a new user.”

A new colleague gets a Celoxis account through Create a User as soon as the source tool says they exist, so project managers can assign them work from the start.

When to use it
HR or IT keeps the list of staff in its own system and wants Celoxis to follow it.
Watch out
testing with Run once creates a real person in Celoxis; use a test profile and clean it up afterwards.
Celoxis6

Delete an App

Action

In Make“Deletes a specified app.”

Delete an App removes a chosen app from Celoxis, which keeps the workspace clear of objects that no longer match anything in your other tools.

When to use it
the item behind the app was retired elsewhere and the record in Celoxis has no reason to stay.
Watch out
a deletion cannot be undone from Make, so read the app with Get an App before this step to be sure you target the right one.
Celoxis7

Delete a Project

Action

In Make“Deletes a project.”

A project created by mistake, or opened for a deal that fell through, disappears from Celoxis with Delete a Project.

When to use it
the CRM marks a deal as lost after your scenario already opened its project, and the portfolio should not show it.
Watch out
the project goes with no way back from Make; keep this module at the end of the flow and test it on a dummy project only.
Celoxis8

Delete a Task

Action

In Make“Deletes a task.”

Delete a Task takes a task out of Celoxis, handy for tidying duplicates that an earlier automation or an import left behind.

When to use it
a request is cancelled in the tool it came from and its task should go too.
Watch out
Run once deletes for real, and placed after List Tasks it deletes every task the search returned, not only the first.
Celoxis9

Delete a Time Entry

Action

In Make“Deletes a specified time log.”

A wrong time log can be removed with Delete a Time Entry, so reports and invoices built on Celoxis hours stay accurate.

When to use it
an entry was synced twice, or a manager rejects it in another tool and Celoxis should no longer count it.
Watch out
point it at one specific entry; mapped from List Time Entries, it removes every entry the search found.
Celoxis10

Get an App

Action

In Make“Returns information about an app.”

Get an App reads the details of one app you already know, so the modules that follow can use its current information.

When to use it
an earlier module gives you the app to look at and you need its details, for example before a message or an update.
Watch out
it fetches a single app; when you do not know which one you need, List Apps is the module to start with.
Celoxis11

Get a Project

Action

In Make“Returns information about a project.”

Status reports read better with the full picture: Get a Project returns what Celoxis holds about one project, ready to place in an email, a sheet or a chat message.

When to use it
a client or a manager should receive the details of a specific project without logging in to Celoxis.
Watch out
one project per run; for a portfolio view, List Projects fits better.
Celoxis12

Get a Task

Action

In Make“Returns information about a task.”

Before your scenario decides anything about a task, Get a Task reads its current state in Celoxis, so you work from fresh data rather than an old copy.

When to use it
another app mentions a task and the scenario needs its latest information before it notifies someone or changes it.
Watch out
the module needs to know which task to read, so map it from a previous module rather than typing it.
Celoxis13

Get a Time Entry

Action

In Make“Returns information about a time entry.”

Get a Time Entry pulls one logged entry out of Celoxis, which lets you check it or copy it to billing without opening the timesheet.

When to use it
finance needs the details of a single entry flagged in another tool before approving it.
Watch out
to read all entries of a period, this is the wrong module; List Time Entries returns them together.
Celoxis14

Get a User

Action

In Make“Returns information about a user.”

Notifications reach the right person when Get a User looks up the details Celoxis has on them first.

When to use it
a task names an assignee and the next module, an email or a chat app, needs more than a name to reach that person.
Watch out
each lookup is one operation, so a scenario that reads the same user for every bundle spends more than it needs.
Celoxis15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call covers whatever the other Celoxis modules leave out: it calls any endpoint of the Celoxis API from your scenario, with the same connection.

When to use it
you need an operation that no listed module offers, and the Celoxis API provides it.
Watch out
you write the request yourself, and Make's documentation cannot help much since it calls its Celoxis coverage limited; so start with one small call and read what comes back with Run once.
Celoxis16

Update an App

Action

In Make“Updates information about an app.”

When an app changes in the tool where it is managed, Update an App brings the same change into Celoxis, so both sides tell the same story.

When to use it
the app is edited in its source tool and the Celoxis record should follow without manual edits.
Watch out
Run once edits the real record, so try the scenario on a test app in Celoxis before switching it on.
Celoxis17

Update a Project

Action

In Make“Updates information about a project.”

Update a Project keeps a Celoxis project in line with changes made elsewhere, in the CRM or in a contract tool.

When to use it
the client extends the scope in your sales tool and the project in Celoxis should reflect it the same day.
Watch out
the scenario must know which project to change; read it with Get a Project or List Projects first when the source does not identify it.
Celoxis18

Update a Task

Action

In Make“Updates information about a task.”

Edits made outside Celoxis, such as a ticket closed or a request reworded, land on the matching task through Update a Task.

When to use it
your support or sales tool is where the change happens, and the Celoxis task must not fall behind.
Watch out
avoid pairing it with Watch Task Update in the same scenario, or your own write may start the scenario again.
Celoxis19

Update a Time Entry

Action

In Make“Updates information about a time entry.”

After a review, Update a Time Entry corrects an existing log in Celoxis instead of deleting it and entering it again.

When to use it
a manager adjusts hours in an approval tool and Celoxis should hold the approved figure.
Watch out
map the entry from Get a Time Entry or List Time Entries, and test on a sandbox project first, since Run once changes real data.
Celoxis20

Update a User

Action

In Make“Updates information about a user.”

People change teams, titles and managers; Update a User carries those changes from your HR system into their Celoxis profile.

When to use it
the staff directory lives in another tool and Celoxis should not be the one place with outdated details.
Watch out
match people carefully, reading them with List Users or Get a User before the update, so the change hits the right profile.
Celoxis21

List Apps

Search

In Make“Returns a list of apps.”

List Apps returns the apps stored in Celoxis as separate bundles, which you can then check, copy or filter in later modules.

When to use it
you want an inventory in a spreadsheet, or you need to find whether an app already exists before creating it.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
Celoxis22

List Projects

Search

In Make“Returns a list of projects.”

Portfolio reviews start with List Projects, which sends each Celoxis project down the scenario as its own bundle.

When to use it
management wants all projects in a shared sheet or a dashboard, refreshed by the scenario rather than exported by hand.
Watch out
when the search finds nothing, the modules after it do not run, so an empty sheet usually means an empty result.
Celoxis23

List Tasks

Search

In Make“Returns a list of tasks.”

A digest of open work, a board in another tool or a cleanup pass all begin with List Tasks, which returns Celoxis tasks as a series of bundles.

When to use it
you need many tasks at once, whereas Get a Task is for one task you can already name.
Watch out
each task found multiplies the operations of the following modules, so keep what comes after it short.
Celoxis24

List Time Entries

Search

In Make“Returns a list of time entries.”

Billing and cost tracking rely on List Time Entries, which returns the hours logged in Celoxis so another app can total or invoice them.

When to use it
finance closes a period and needs every entry in its accounting or reporting tool.
Watch out
sending each entry to a sheet one by one uses one operation per entry; plan your volume against your Make plan.
Celoxis25

List Users

Search

In Make“Returns a list of users.”

List Users gives you the people in your Celoxis account as bundles, a handy base for checks and syncs with other systems.

When to use it
IT wants to compare Celoxis accounts with the HR directory and spot people who left or never got access.
Watch out
treat the output as a list to compare, not a trigger; it does not tell you who is new unless you compare it with something.
Need help

Need help automating Celoxis with Make?

A person reads every message.

FAQ

Questions about Celoxis and Make

01Is the Celoxis Make integration free?
Yes. Celoxis is a standard app in Make, so its 27 modules are available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes of execution, and caps files at 5 MB and data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle. The price of Celoxis itself is a separate matter not covered here.
02What does connecting Celoxis to Make require?
A Celoxis account and a Make account. Make's documentation lists no special prerequisite for Celoxis and no Celoxis-specific connection steps, so the usual Make flow applies: add a Celoxis module, click Create a connection, name it if you want, authorize Make on the Celoxis page or paste the key Celoxis gives you, then click Save. The same connection serves all 27 modules. Because Make describes its Celoxis documentation as limited, test the connection with Run once on a simple module such as List Projects before you build around it.
03Does the Celoxis trigger in Make react in real time?
No. Both Celoxis triggers, Watch New Task and Watch Task Update, are scheduled: Make checks Celoxis on the scenario's schedule instead of being called by Celoxis. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; on a paid plan you can go down to 1 minute. Whatever changed between two checks arrives together on the next run, one bundle per task. If you need a faster reaction, a shorter interval on a paid plan is the lever available here.
04What if a Celoxis module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Celoxis API from your scenario, reusing the Celoxis connection you already created, so you are not limited to the 27 listed modules. You write the request yourself, and Make states that its own documentation for Celoxis is limited by the lack of public information, so test each call with Run once. Before going that way, check whether a Get or List module followed by an Update already covers the case: it is simpler to maintain.
05Should you use Make or n8n for Celoxis?
It depends on where the rest of your automations run. Many apps have both a Make app and an n8n node, so check what each side offers for Celoxis before choosing. On Make, the facts are clear: 27 modules, 2 scheduled triggers, available from the Free plan, plus Make an API Call for anything else. If your team already builds scenarios in Make, keeping Celoxis there avoids splitting your work between two tools. The comparison page linked above sets out the criteria without ranking either one.
Same platform

Other docs you might need on this stack.

Browse all integrations