Resources · Zapier integration

Ganttic Zapier integrationAutomate Ganttic with Zapier.

The Ganttic Zapier integration gives you 9 triggers and 3 actions, with 0 searches. All 9 triggers are instant, so a project, resource or task added, changed or deleted in your plan reaches Zapier straight away, even on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Ganttic Zapier integration does for your planning

It connects your Ganttic account to Zapier so that changes in your resource plan start a Zap, and so that a Zap can add projects, resources and tasks to that plan. A Zap is the automation you build on Zapier: one starting event, then one or more steps that run on their own, every time.

Three outcomes come up again and again. First, a plan that is never empty on day one: Project Added starts a Zap, and Add Task books the first slot on the new project. Second, a schedule fed from the tools where work is sold: a deal signed or a form submitted elsewhere becomes a project through Add Project, without anyone retyping it. Third, a trail of every change: the three Updated triggers and the three Deleted triggers report each edit and removal to the place where you keep records.

What Zapier does not do here matters just as much. There is no search step for Ganttic, so a Zap cannot look up an existing project, resource or task. The actions only add: none edits, moves or deletes something already in the plan. If your workflow needs to change a task's dates after the fact, Zapier will not do it with this integration.

The same app has a Ganttic Make integration page, and if you are still choosing a platform, n8n vs Zapier puts the two side by side.

Vocabulary

Zapier vocabulary in one minute

Seven words do most of the work on this page. Here they are in plain language.

Trigger
The event in Ganttic that starts the Zap, such as a new project. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does after it starts: the step that adds a project, a resource or a task, or writes something in another app.
Task (Zapier)
Zapier's billing unit: one action that completed successfully. Not to be confused with a Ganttic task on your plan.
Instant trigger
A trigger Ganttic reports itself: it calls Zapier as soon as the event happens, so nothing waits for a timer.
Polling trigger
The other kind, checked by Zapier on a timer. Ganttic has none on Zapier, which is why the plan grid matters less here.
Filter
A step that lets the Zap continue only when what arrived matches your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes it one, and that needs a paid plan.
Cost

What a Ganttic Zap really costs

Ganttic is not a premium app on Zapier, so it runs on the free plan. Usage is counted in tasks, and the rules are short.

  • Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
  • BilledEach action that succeeds, one task each
  • Not billedThe trigger, and any action that fails
  • Ganttic triggers9 of 9 instant, so the grid below does not apply

The trigger never costs a task. Only an action that completes is counted, one task each, and an action that fails costs nothing. A Zap that adds one task in Ganttic per new project therefore costs one task per project. Because the 9 Ganttic triggers are instant, the polling grid below does not slow them down, even on Free. The real limit is elsewhere: the free plan stops at two steps. Add a filter before Add Task and the Zap needs a paid plan.

Connect

Connect your Ganttic account in three steps

  1. 01

    Open the Apps page

    In Zapier, open Apps and click + Add connection. Search for Ganttic in the dialog and select it. A connection is your Ganttic account linked once, then reused by every Zap that works with Ganttic.

  2. 02

    Sign in to Ganttic

    Click Add connection. Ganttic opens in a new tab: sign in with the account that holds the resource plan your Zaps should read from and write to, since every Zap will act on that one.

  3. 03

    Grant access

    Let Zapier act on the account. You need a Ganttic account, plus read or write access to any project or resource you do not own yourself and that the Zap should touch.

First Zap

Your first Zap: every client project starts with a kickoff slot

GoalA design studio plans its people in Ganttic. When a project is added, a kickoff task is booked on it, but only when a field you pick from the test holds the value you choose.

  1. 01

    Build the trigger

    Click Build, choose Ganttic and the Project Added event, then pick your connection. The lightning bolt in the editor tells you the trigger is instant.

  2. 02

    Test the trigger

    Run Test. Zapier brings back the three most recent projects of the account, so you set up the next steps on a real one.

  3. 03

    Add the filter

    Add a Filter step from the plus icon. Look at what the test project brought back, pick a field, the rule and the value. If no field tells your projects apart, drop the filter.

  4. 04

    Add the action

    Add Ganttic with Add Task. Fill Start time and End time, typed in or mapped from a value the test brought back, so the kickoff lands on the plan.

  5. 05

    Publish

    Test the action, check the task really appeared in Ganttic, then click Publish. With its filter, this Zap needs a paid plan.

Triggers

The 9 Ganttic triggers, one by one

9 events start a Zap when something happens in Ganttic, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Project Deleted

Instant trigger

In Zapier“Triggers when a project is deleted.”

Fires when someone removes a project from Ganttic. The removal stops being silent: another tool learns about it as soon as it happens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
finance tracks billable projects in a spreadsheet and needs to know when one disappears from the plan, so nothing gets invoiced by mistake.
Watch out
the project is already gone in Ganttic when the Zap runs, so do not count on a later step finding it there.
2

Resource Deleted

Instant trigger

In Zapier“Triggers when a resource is deleted.”

Reacts when a resource is taken out of your Ganttic plan. It is the signal that capacity just shrank.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an operations manager wants a heads-up in the team chat whenever a resource leaves the plan, so open bookings can be reviewed.
Watch out
do not use it to add the resource back with Add Resource; you would only recreate what someone removed on purpose.
3

Task Deleted

Instant trigger

In Zapier“Triggers when a task is deleted.”

Starts a Zap when a task is removed from the plan. Useful when a cancelled slot has consequences outside Ganttic.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a training company books trainers in Ganttic and wants each cancelled session logged in its booking sheet.
Watch out
each deleted task is its own run, so a big clean-up of the plan can trigger many runs at once.
4

Project Added

Instant trigger

In Zapier“Triggers when a new project is added.”

Fires each time a new project is created in Ganttic. It is the natural starting point for anything that should happen once per project.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an agency creates a matching folder and channel for every new project, so the team never starts work without a place to put it.
Watch out
never pair it with Add Project, or each new project creates another one in an endless loop.
5

Resource Added

Instant trigger

In Zapier“Triggers when a new resource is added.”

A resource joining your Ganttic plan is what sets this one off. New capacity becomes an event other tools can act on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a field service company adds each new technician as a resource and wants an onboarding checklist opened for them.
Watch out
a bulk import of resources sends a large batch at once, which Zapier's flood protection may hold back.
6

Task Added

Instant trigger

In Zapier“Triggers when a new task is added.”

Fires whenever a task is put on the plan. Every booking in Ganttic can then reach the people or tools that depend on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a video production team wants each shoot booked in Ganttic to appear in the shared calendar the crew reads.
Watch out
a Zap that answers Task Added with Add Task feeds itself; keep the action in another app.
7

Project Updated

Instant trigger

In Zapier“Triggers when a project is updated.”

Fires when an existing project is changed. It catches edits that would otherwise only be visible to whoever opens the plan.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a project lead wants the client-facing status board refreshed whenever a project changes in Ganttic.
Watch out
it fires on every edit, so it must never create something; use it to update or notify, or you will pile up duplicates.
8

Resource Updated

Instant trigger

In Zapier“Triggers when a resource is updated.”

Any change to a resource's details sets off this trigger. Your other tools stay in step with the plan without a manual check.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an HR coordinator wants changes to a resource reflected in the staff directory the rest of the company uses.
Watch out
every change starts a run, so pairing it with Add Resource would add a new resource on each edit.
9

Task Updated

Instant trigger

In Zapier“Triggers when a task is updated.”

Edit a task already on the plan and this trigger runs. The schedule's churn becomes visible outside Ganttic.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a consultancy wants the consultant concerned to get a message when their booking changes, instead of finding out on the day.
Watch out
one task edited several times starts several runs, and never let it trigger Add Task.
Actions

The 3 Ganttic actions

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

1

Add Project

Action

In Zapier“Creates a new project.”

Creates a project in Ganttic from what the Zap passes in. Sold work lands on the plan without anyone retyping it.

When to use it
a deal marked won in your CRM should open the matching project for the planners.
Watch out
the Name field is required.
2

Add Resource

Action

In Zapier“Creates a new resource.”

Adds a new resource to the plan, ready to receive bookings. Capacity grows from the system where it is decided.

When to use it
a new hire recorded in your HR tool should be bookable in Ganttic from the start.
Watch out
Name is required here too.
3

Add Task

Action

In Zapier“Creates a new task.”

Books a new task on the plan between a start and an end. It is the action that actually fills the calendar.

When to use it
a form for internal requests should reserve the time on the plan once submitted.
Watch out
Start time and End time are both required, so the earlier step must supply them.
When it breaks

When a Ganttic Zap breaks

Zapier links no help article to Ganttic, and no Ganttic-specific limit is documented. The surprises come from how Zaps behave in general, and three of them hit planning tools hard.

Know these four situations before you publish and most of them never happen. If a Zap still misbehaves, start from the Zapier troubleshooting page.

  • A Zap that feeds itself

    Task Added followed by Add Task, or Project Added followed by Add Project: each creation starts the Zap again. The loop burns through your tasks fast.
  • Duplicates from Updated triggers

    Project, Resource and Task Updated fire on every edit. Use them to notify or sync, never to create, or each change adds another record.
  • The existing plan is ignored

    A Zap only reacts to what happens after it is published. Projects, resources and tasks already in Ganttic stay out of reach; moving them is a separate job.
  • A bulk change is held back

    Importing or deleting many items at once can return a huge batch, which Zapier's flood protection may hold instead of running everything.
Need help

Need help automating Ganttic with Zapier?

A person reads every message.

FAQ

Ganttic and Zapier: frequent questions

01Is the Ganttic Zapier integration free?
Yes. Ganttic is not a premium app on Zapier, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The limit is the size of each Zap: two steps, one trigger and one action. Booking a kickoff task on every new project fits. Booking it only for client projects needs a filter, which makes the Zap multi-step and moves you to a paid plan. Check that point before you design a workflow with conditions.
02How many tasks does a Ganttic Zap use?
One Zapier task per action that succeeds, and none for the trigger. Watch the vocabulary: a Zapier task is a billing unit, not a task on your Ganttic plan. A Zap that adds one Ganttic task for each new project costs one Zapier task per project. If it also posts a message, that is two per project. An action that fails is not counted, so a broken Zap does not eat your quota, it simply stops doing its job.
03Is the Ganttic Zapier integration real time?
Yes, for all 9 triggers. Project, Resource and Task Added, Updated and Deleted are instant: Ganttic tells Zapier the moment something happens, and the Zap starts right away whatever your plan. The polling grid, 15 minutes on Free down to one minute on Team and Enterprise, does not apply to them. In the editor, a Zap built on one of these triggers shows a lightning bolt, which is the quickest way to check.
04What does it take to connect Ganttic to Zapier?
A Ganttic account and a Zapier account. You add the connection from the Apps page in Zapier, sign in to Ganttic in the tab that opens, then grant access. If your Zaps should touch projects or resources owned by someone else, the connected account needs read or write rights on them. Plan the values the actions require: a Name for Add Project and Add Resource, a Start time and an End time for Add Task.
05Why does a Ganttic Zap keep creating duplicates?
Usually because an Updated trigger is wired to an Add action. Project Updated, Resource Updated and Task Updated fire on every edit, so a Zap that creates something each time adds a new record on each change. The other cause is a loop: Task Added followed by Add Task, or Project Added followed by Add Project, restarts the Zap on its own output. Keep creation Zaps on Added triggers and send their output to a different app.
06What if the Ganttic operation you need is not in Zapier?
Then the Zap cannot do it directly. On Zapier, Ganttic offers 9 triggers and 3 actions, all three of which add something, and no search step. There is no way to edit a task's dates, delete a project or look up an existing resource from a Zap. You can redesign the workflow around what exists, for instance notifying a planner instead of editing, or check whether another automation tool exposes the Ganttic operation the workflow depends on.
07Zapier, Make or n8n for Ganttic?
It depends on the criterion, not on a ranking. On Zapier, Ganttic brings 9 instant triggers on projects, resources and tasks, which react straight away even on the free plan, and 3 actions that only add. There is no search step and no action that edits or deletes. If the workflow only needs to react to the plan and add items, Zapier covers it. If it must change dates or remove something, check which Ganttic operations Make and n8n expose before choosing, and weigh the tool your team already uses.