Resources · Make integration

Ganttic Make integrationAutomate Ganttic with Make.

What if your Ganttic planner told the rest of your tools the moment a plan changes? The Ganttic Make integration gives you 25 modules: 9 instant triggers, 13 actions and 3 searches. This page walks planners and ops leads through the connection, a first scenario and every module.

Try the Ganttic integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ganttic Make integration do for you?

The Ganttic Make integration links your Ganttic account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, a trigger, an action or a search. Ganttic can call Make the second a project, a resource or a task changes, and Make can create, update, read or delete those same objects for you.

A kickoff task on every new project. Watch Project Created fires when someone adds a project, and Create a Task drops the first planning task onto it, so no project starts with an empty timeline.

Requests from another app that land as planned work. A form, a ticket or a row in another tool can start the scenario; Search Resources finds the right person and Create a Task books the work in Ganttic without anyone retyping it.

A team that hears about changes. Watch Task Updated and Watch Task Deleted pass each change to a chat or email module, so the people affected learn about a moved or cancelled task without opening the planner.

Know the limits before you start: Make says its documentation for Ganttic is incomplete, because little public information about the app exists. Anything the listed modules do not cover goes through Make an API Call. If you are still weighing tools, read our Make review and the n8n vs Make comparison, and when you want to build faster, the Make training covers the editor step by step.

Connect

How do you connect Ganttic to Make?

  1. 01

    Add a Ganttic module

    Open a scenario, search for Ganttic and pick any module, for example Watch Task Created. In the module panel, click Create a connection. The connection is your Ganttic account linked to Make once, then reused by every Ganttic module.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the workspace or the team it belongs to. This step is optional, but it helps a lot once you manage more than one account.

  3. 03

    Authorize and save

    Authorize Make on the Ganttic page that opens, or paste the key Ganttic gives you, depending on what the window asks for. Then click Save, and the module can read your projects, resources and tasks.

First scenario

Your first scenario: a kickoff task for each new Ganttic project

GoalWhen a project is created in Ganttic, Make adds a first task to it so the plan never starts empty.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Ganttic and choose Watch Project Created.

  2. 02

    Connect Ganttic

    Click Create a connection and link your Ganttic account. Because this trigger is instant, Ganttic will call Make through a webhook each time a project appears.

  3. 03

    Add the task module

    Click the + on the right of the trigger, pick Ganttic again, then Create a Task. It reuses the same connection. Map data from the trigger's bundle, the item it received, into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once, then create a test project in Ganttic. Open the bubbles above each module to read the bundles they received and check the new task in your planner.

  5. 05

    Switch it on

    Save the scenario and switch it on. From then on, every project created in Ganttic gets its kickoff task, and each module run counts as one operation on your Make plan.

Triggers

Ganttic triggers in Make

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

Ganttic1Watch Project Created

Watch Project Created

Instant trigger

In Make“Triggers when a new project has been created.”

This trigger starts your scenario each time a project appears in Ganttic, so the work that follows a new project begins on its own. It hands Make the new project as one bundle.

How it fires
instant, Ganttic calls Make through a webhook as soon as the project is created.
When to use it
when every new project needs the same follow-up, a kickoff task, a folder in another app or a message to the account manager.
Watch out
it reacts to new projects only; to act on projects already in the planner, start from Search Projects instead.
Ganttic2Watch Project Deteled

Watch Project Deteled

Instant trigger

In Make“Triggers when a project has been deleted.”

You get a signal the moment a project leaves Ganttic, which lets you clean up what depended on it elsewhere. Make shows the module under this exact spelling, typo included, so search for it as written.

How it fires
instant, Ganttic calls Make through a webhook as soon as the deletion happens.
When to use it
when a cancelled project should also close its channel, archive its row in a reporting sheet or warn the finance team.
Watch out
the project is already gone in Ganttic, so a Get a Project placed after this trigger may find nothing to read.
Ganttic3Watch Project Updated

Watch Project Updated

Instant trigger

In Make“Triggers when a project has been updated.”

Changes to a project, a new name or a shifted date, reach your other tools without anyone copying them over. The updated project arrives in Make as a bundle ready to map.

How it fires
instant, Ganttic calls Make through a webhook as soon as the project is saved.
When to use it
when a CRM, a client portal or a shared sheet has to mirror the project as it stands in the planner.
Watch out
every edit sends a bundle, so a scenario that writes back to the same project with Update a Project can fire itself again; add a filter to break that loop.
Ganttic4Watch Resource Created

Watch Resource Created

Instant trigger

In Make“Triggers when a new resource has been created.”

A new person, room or machine added to Ganttic becomes a starting point for your onboarding flow. Resources are what you schedule in Ganttic, and this module watches their arrival.

How it fires
instant, Ganttic calls Make through a webhook as soon as the resource exists.
When to use it
when a new team member in the planner should also get an account request in the HR tool or a welcome message in chat.
Watch out
the trigger only knows about Ganttic; it will not tell you whether the person already exists in your other apps, so search there before creating a duplicate.
Ganttic5Watch Resource Deleted

Watch Resource Deleted

Instant trigger

In Make“Triggers when a resource has been deleted.”

Removing a resource in Ganttic can close the loop in every tool that relied on it. Make receives the deletion and your scenario decides what to tidy up.

How it fires
instant, Ganttic calls Make through a webhook as soon as the resource is removed.
When to use it
when an equipment item is retired or someone leaves the team, and a booking tool or an access list must follow.
Watch out
deleting a resource by mistake in Ganttic will run the same cleanup, so point this trigger at reversible steps such as a notification first.
Ganttic6Watch Resource Updated

Watch Resource Updated

Instant trigger

In Make“Triggers when a resource has been updated.”

When a resource's details change in Ganttic, this trigger passes the new version to the rest of your stack. Your directory or your capacity sheet stays in step with the planner.

How it fires
instant, Ganttic calls Make through a webhook as soon as the resource is edited.
When to use it
when a renamed or edited resource has to show up in a staff list kept in another app.
Watch out
Make's documentation does not list what the bundle holds; run the scenario once and read the output before mapping anything.
Ganttic7Watch Task Created

Watch Task Created

Instant trigger

In Make“Triggers when a new task has been created.”

Each new task planned in Ganttic can appear in the calendar or the chat of the person who has to do it. That is the most common reason to connect Ganttic to Make.

How it fires
instant, Ganttic calls Make through a webhook as soon as the task is added.
When to use it
when your crew works from a shared calendar or a messaging app and never opens the planner itself.
Watch out
if the same scenario also runs Create a Task in Ganttic, the task it creates will start the scenario again; keep those two in separate scenarios or filter them.
Ganttic8Watch Task Deleted

Watch Task Deleted

Instant trigger

In Make“Triggers when a task has been deleted.”

A task removed from the plan should not survive as a ghost event in someone's calendar. This trigger tells Make as soon as it happens, so your scenario can remove or flag the copy.

How it fires
instant, Ganttic calls Make through a webhook as soon as the task is deleted.
When to use it
when you already push tasks elsewhere with Watch Task Created and need the reverse path too.
Watch out
to delete the copy in the other app, you need a link between both items; store the Ganttic task ID there when you create the copy.
Ganttic9Watch Task Updated

Watch Task Updated

Instant trigger

In Make“Triggers when a task has been updated.”

Rescheduling in Ganttic reaches the people concerned without a phone call. Any edit to a task sends its new state to Make, and the scenario takes it from there.

How it fires
instant, Ganttic calls Make through a webhook as soon as the task changes.
When to use it
when a moved task should update a calendar event, post in the project channel or change a ticket status.
Watch out
small edits count too, so a busy planner sends many bundles and each module run is an operation; a filter right after the trigger keeps only the changes that matter.
Modules

Ganttic actions and searches in Make

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

Ganttic1

Create a Project

Action

In Make“Creates a new project.”

A signed deal or an approved request becomes a Ganttic project without anyone opening the planner. The scenario fills in the project from the data of the previous module.

When to use it
when a deal is won in your CRM and the delivery team plans the work in Ganttic.
Watch out
run Search Projects first if the same request can arrive twice, or you will end up with twin projects.
Ganttic2

Create a Resource

Action

In Make“Creates a new resource.”

New people or equipment show up in Ganttic as soon as they exist elsewhere, ready to be scheduled. Your HR tool or inventory stays the place where they are first entered.

When to use it
when a hire is confirmed in the HR app and planners need the person available in Ganttic on day one.
Watch out
check with Search Resources that the name is not already taken.
Ganttic3

Create a Task

Action

In Make“Creates a new task.”

This is how requests from other apps land in the plan as real, scheduled work. Each bundle that reaches the module turns into one Ganttic task.

When to use it
when a form answer, a support ticket or a new project in Ganttic should produce a task without retyping.
Watch out
a scenario started by Watch Task Created that also creates tasks will loop; keep them apart.
Ganttic4

Delete a Project

Action

In Make“Deletes a project.”

Removes a project from Ganttic, which keeps the planner free of cancelled or test work. The module needs to know which project to delete, usually from a search or a trigger before it.

When to use it
when a deal is lost in the CRM and the tentative project should disappear from the plan.
Watch out
treat the deletion as final and test it on a dummy project with Run once first.
Ganttic5

Delete a Resource

Action

In Make“Deletes a resource.”

Takes a person or an asset out of Ganttic when it is gone for good in the source system. The planner then stops offering it for new bookings.

When to use it
when an offboarding is completed in the HR tool, or when a machine is scrapped in the inventory app.
Watch out
check with Search Tasks whether planned work still points to the resource before you remove it.
Ganttic6

Delete a Task

Action

In Make“Deletes a task.”

Clears a task from the plan when the request behind it is cancelled somewhere else. The schedule shows only work that will really happen.

When to use it
when a customer cancels a booking in another app and the matching Ganttic task must go too.
Watch out
you need the task's ID; save it in the other app when the task is first created, or find it with Search Tasks.
Ganttic7

Get a Project

Action

In Make“Retrieves an existing project.”

Fetches the full record of one project you already know, so later modules can use details the trigger did not bring. It reads, it never changes anything.

When to use it
when your scenario holds a project ID from another app and your message needs the full project record.
Watch out
it expects one known project; to find projects by criteria, use Search Projects instead.
Ganttic8

Get a Resource

Action

In Make“Retrieves an existing resource.”

Reads one resource in full, so a later module can use its details in another tool. Nothing is modified in Ganttic.

When to use it
after Watch Resource Updated, to read the complete record before copying it to your staff directory.
Watch out
run the scenario once and read the output, since Make's documentation does not list what the record contains.
Ganttic9

Get a Task

Action

In Make“Retrieves an existing task.”

Pulls the current state of a single task, which is handy when your scenario starts from another app and only holds the Ganttic task ID.

When to use it
when a ticket in your help desk stores the task ID and an agent wants the planned dates shown in the ticket.
Watch out
a task deleted in Ganttic cannot be read anymore, so plan for an error route.
Ganttic10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers what the other Ganttic modules do not, by calling any endpoint of the Ganttic API with the connection you already set up. No second login is needed.

When to use it
when you need an object or an option that none of the 25 listed modules offers.
Watch out
you write the request yourself, so keep the Ganttic API reference open; Make's own Ganttic documentation is incomplete.
Ganttic11

Update a Project

Action

In Make“Updates an existing project.”

Keeps a Ganttic project in line with the system that owns the facts, for example a CRM that tracks the client's deadline. Only the project you point to changes.

When to use it
when the delivery date moves in the sales tool and the planner has to reflect it.
Watch out
paired with Watch Project Updated in the same scenario, each update can start the scenario again; add a filter.
Ganttic12

Update a Resource

Action

In Make“Updates an existing resource.”

Brings a resource's record up to date in Ganttic from your directory or your inventory. Planners see current information without editing it by hand.

When to use it
when someone's details change in the HR app and their Ganttic record should follow.
Watch out
find the resource first with Search Resources, because the update needs to know exactly which one to change.
Ganttic13

Update a Task

Action

In Make“Updates an existing task.”

Moves or renames a Ganttic task from the outside, so changes decided in another tool reach the plan straight away.

When to use it
when a client reschedules an appointment in a booking app and the matching task in Ganttic must shift with it.
Watch out
a scenario that listens with Watch Task Updated and writes with this module will loop without a filter between them.
Ganttic14

Search Projects

Search

In Make“Searches for projects or lists them all.”

Finds the projects that match what you ask for, or lists them all, and returns zero, one or several bundles. Each project found runs the next modules once.

When to use it
before creating a project, to check that it does not exist yet, or to build a project list in a sheet.
Watch out
an empty result stops the flow for that bundle, so decide what should happen when nothing matches.
Ganttic15

Search Resources

Search

In Make“Searches for resources or lists them all.”

Looks up people or equipment in Ganttic so the scenario can pick who gets the work. The result can hold several resources, each passed on as its own bundle.

When to use it
when a request names a person by name and you need their Ganttic resource to assign a new task.
Watch out
a vague search returns many bundles and each one costs an operation downstream.
Ganttic16

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Returns the tasks that match your query, or every task, so you can report on the plan or act on a batch of work at once.

When to use it
when a resource is about to be deleted and you want to see which tasks still point to it.
Watch out
listing everything in a large planner produces a lot of bundles, and every module after it runs once per task.
Need help

Need help automating Ganttic with Make?

A person reads every message.

FAQ

Ganttic and Make: frequently asked questions

01Is the Ganttic Make integration free?
Yes, Ganttic is a standard app in Make, so it works from the Free plan. That plan has real limits: 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. Paid plans (Core, Pro, Teams and Enterprise) lift those limits, and usage is counted in operations, one per module run on one bundle. Your Ganttic subscription is separate and not covered here.
02What do you need to connect Ganttic to Make?
A Ganttic account and a Make account are enough to start. Make's documentation lists no specific prerequisite for Ganttic and no official connection steps, so the generic flow applies: add a Ganttic module, click Create a connection, optionally name it, authorize Make on the Ganttic page or paste the key Ganttic gives you, then click Save. The same connection then serves all 25 Ganttic modules, triggers included. If the authorization window asks for something unclear, the Ganttic account admin is the right person to ask.
03Do Ganttic triggers in Make react in real time?
Yes. All 9 Ganttic triggers are instant: Ganttic calls Make through a webhook as soon as a project, a resource or a task is created, updated or deleted. You do not wait for the scenario's schedule, which is every 15 minutes by default for scheduled triggers. The lightning badge on the module in the editor shows this. Each event still counts as operations for every module that runs after the trigger.
04What if a Ganttic module is missing or too limited in Make?
Use Make an API Call. It calls any endpoint of the Ganttic API with the connection you already created, so you can reach what the 13 actions and 3 searches do not cover. Be aware that Make describes its Ganttic documentation as limited, because little public information about the app exists; keep the Ganttic API reference at hand when writing the request, and test it with Run once before switching the scenario on.
05Make or n8n for Ganttic automations?
It depends on what you need to see before choosing. On Make, Ganttic comes with 25 ready modules, 9 of them instant triggers, plus Make an API Call for the rest, all set up with one connection. Many apps also have an n8n node, and this page does not rank the two tools or compare their prices. Check the module list on each side against the scenario you have in mind, then decide on that basis.
Same platform

Other docs you might need on this stack.

Browse all integrations