Ganttic

Ganttic is resource planning that books people, rooms and machines against projects on a shared timeline. Agents create and reschedule bookings, manage resources and projects, and read utilization so the plan matches real demand.

28 actions API key available

Ganttic website Platform Documentation Capability data verified 2026-08-18

A deal moves to closed won in the CRM with a requested install window

Agent reads the site, the dates, and the skills and equipment the job needs

Create Project opens the job so its bookings group under one name

List Tasks reads the existing schedule in that window to see what each candidate resource is already committed to

Agent confirms the requested window is inside the resource's working availability

The proposed booking goes to the scheduler with the conflicts and displaced work named

The scheduler approves the assignment, and Create Task books the people and equipment

What This Integration Enables

Ganttic is a capacity ledger rather than a task list, and the API makes that explicit: a task requires a start, an end, and at least one resource, because a Ganttic task is fundamentally a booking of something finite. That something does not have to be a person. Rooms, vehicles, machines, and rigs are first-class resources, which is why this tool tends to show up in teams whose real constraint is physical rather than headcount. Users and resources are deliberately different objects here: an account that can sign in is not the same thing as a thing work is booked against.

FlowRunner agents work the ledger end to end. They open projects for incoming jobs, read the existing schedule in a window before committing to anything, create and reschedule bookings, post actual time worked back against the booking that consumed it, and maintain the custom data fields that carry a team's own vocabulary for skills, certifications, and sites. Two properties of the API shape how a careful flow is built. Updates are full replacements rather than patches, so an agent reads the record and passes its current values back through. And archiving is a status rather than a route, so keeping history means writing a status, not calling a delete. Neither habit protects a person from being double-booked, which is why the human-in-the-loop gate on this connector sits on the reschedule.

Without FlowRunner

Capacity lives in a person's head Whoever owns the planner is the only one who knows what can actually be promised

Bookings made without the full picture A resource gets committed twice because the second request never saw the first

Actuals never come back The plan says what was booked, and nothing says what was really spent

With FlowRunner

Capacity queried before the promise The schedule in the requested window is read before anyone commits to a date

Conflicts surfaced with names attached A clash arrives as a proposal showing whose booking would move, not as a silent overwrite

Actuals fed back to the plan Time worked is posted against the booking it belongs to, so utilization reflects reality

Use Case Scenarios

The won deal books the crew

A deal reaches closed won in Pipedrive or HubSpot with a requested install window. The agent calls Create Project so the job's bookings group under one name, then List Resources filtered on the data fields that describe the required skill and equipment class. List Tasks over the requested window returns what those resources are already committed to. The agent assembles the assignment that fits, posts it to the scheduler in Slack with any clash spelled out, and after approval calls Create Task to book the crew and the equipment together in one booking. The sales team stops promising dates the planner has to walk back.
Actuals that reach the plan without a spreadsheet round trip

A Ganttic booking's total used time cannot be written by editing the task; it moves only through Add Task Used Time. That makes it a clean target for a flow. As timesheets are approved in Harvest or hours are closed out in Toggl, the agent matches each entry to its booking and posts the actual against it. A weekly job then reads bookings and used time across projects and appends the variance to a sheet in Google Sheets, so the utilization the planner shows is measured rather than assumed.
A resource model that stays accurate as people and gear change

New hires, new machines, and expiring certifications all change what can be booked. When a person is added in the HR system, the agent calls Create Resource and sets their skill and site data fields; when a certification lapses, it calls Update Resource to set the status so the planner stops offering them for work they can no longer take. List Data Fields and the option operations keep the vocabulary itself current, so the fields the scheduler filters on match the way the business actually describes its capacity. Retiring a resource sets an archived status rather than deleting it, because the bookings it carried are the record of what happened.

Human-in-Loop Highlight

Ganttic will let you double-book a person, and it will not complain. It has no notion of refusing a booking because the resource is already committed, which means an agent that reschedules on its own is guessing about the one thing it cannot see: whether the human being on that booking can absorb the change. The hazard is sharpened by how Update Task works. It is a full replacement that demands the start, the end, and the resources on every call, so a reschedule is not a nudge to one field, it is a rewrite of the whole booking, and a value not passed through is a value lost. So the scheduling agent reads the booking with Get Task, reads the window with List Tasks, builds the complete replacement, and then stops: "Moving booking INSTALL-77 to the week of the 14th puts Dana at two bookings on Tuesday and Wednesday. The clash is SITE-42, which is customer committed. Move INSTALL-77 anyway, move SITE-42, or hold?" The scheduler answers, and the agent writes exactly one of those outcomes. The same gate covers Delete Resource, which removes the resource and its bookings permanently while an archived status would have kept the history intact.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

28 actions

Resources

List Resources Returns the people, rooms, and machines that work is booked against. Archived resources stay hidden unless explicitly included, since archiving here is a status rather than a deletion.
Get Resource Returns one resource with its color, notes, and custom field values. Used to read the current record before a full-replacement update.
Create Resource Adds a resource that work can be booked against. Used when a new hire, vehicle, or machine joins the pool.
Update Resource Changes a resource, and is also how one is archived or restored, since Ganttic has no separate archive route. Agents pass the current name through, because the API requires it on every update.
Delete Resource Permanently deletes a resource together with its bookings. Gated behind a person, with an archived status as the alternative that keeps the history.

Bookings

List Tasks Returns bookings in a time window, optionally narrowed to one project or resource. The window is the filter that matters, because an unbounded read returns the entire schedule.
Get Task Returns one booking with its resources, times, utilization, and custom field values. Read before every reschedule.
Create Task Books time against one or more resources. A start, an end, and at least one resource are required, which is what makes a Ganttic task a commitment rather than a to-do.
Update Task Moves, renames, reassigns, or archives a booking. A full replacement rather than a patch, which is why the agent reads first and why the reschedule waits for a person.
Delete Task Permanently deletes a booking. An archived status keeps it on record instead, which is usually what a cancellation actually means.
Add Task Used Time Records actual time worked against a booking. The only route that can change a booking's used time, which makes it the single point where actuals reenter the plan.

Projects

List Projects Returns the projects that bookings group under. Archived projects stay hidden unless explicitly included.
Get Project Returns one project with its color, notes, and custom field values.
Create Project Opens a project for bookings to group under. Used to give an incoming job a home before anything is scheduled against it.
Update Project Changes a project, and is also how one is archived or restored. The current name is passed through on every call.
Delete Project Permanently deletes a project. Archiving is the reversible alternative and the default in cleanup flows.

Users

List Users Returns the people who can sign in to Ganttic. These are accounts, which is not the same set as resources, since a resource need not be a person at all.
Get User Returns one account with its name, email, and permission type.
Create User Creates an account that can sign in. The password is write only and can never be read back, so provisioning flows deliver it through the channel the security team specifies.
Update User Changes an account's name, email, or permission type. The current email is passed through on every call.
Delete User Deletes an account. It does not delete the resource of the same name, because accounts and resources are separate objects here.

Custom Data Fields

List Data Fields Returns the custom fields defined for one kind of record. Resource, task, and project fields are entirely separate sets, so a field defined on one is not available on the others.
Create Data Field Defines a custom field on resources, tasks, or projects. Used to give the planner the vocabulary the business already uses for skills, sites, and equipment class.
Update Data Field Renames a custom field or changes whether it appears on the planner label.
Delete Data Field Deletes a custom field together with its values on every record of that kind. Reviewed before it runs, because the values are not recoverable.
Create Data Field Option Adds an option to a list style custom field, which is what makes it selectable in the planner.
Update Data Field Option Renames an option on a list style custom field.
Delete Data Field Option Removes an option from a list style custom field.

Frequently Asked Questions

What can FlowRunner do with Ganttic?

FlowRunner agents can run List Resources, Get Resource, and Create Resource in Ganttic, plus 25 more actions.

Does connecting Ganttic to FlowRunner require OAuth?

No. Ganttic connects to FlowRunner with an API key, no OAuth flow required.

Can Ganttic trigger a FlowRunner workflow automatically?

Ganttic doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Ganttic

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us