GanttPRO

GanttPRO is online Gantt chart software where work is a tree of tasks with durations, dependencies and resources laid over a working calendar. Agents open projects from approved plans, add tasks and dependencies, assign resources, log time and post comments.

47 actions API key available

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

HR publishes next year's public holiday calendar for each office

Agent reads the dates and which projects the affected teams deliver

List Project Calendars returns each project's working days, working hours, and existing custom days

List Tasks and the project's dependency links show which chains cross each new non-working day

The agent reports the projected end date movement for every project, largest slip first

The delivery lead approves each calendar change before Create Custom Day writes it

What This Integration Enables

GanttPRO is a scheduling engine wearing a chart. The dates on a task are not stored facts so much as results: give it two of start date, end date, and duration and it derives the third, run that through the project's working calendar, and propagate it along the dependency links. That is a genuinely different commitment from a board tool, and it changes what an agent should be doing here. The useful work is not moving bars. It is feeding the engine accurate inputs, durations, links, resource assignments, calendars, and actual time logged, and letting it recompute the plan.

FlowRunner agents open projects from approved scopes and build the task tree beneath them, create and adjust dependency links, assign resources with the share of capacity each task consumes, attach specifications to the tasks they belong to, log time against the work that consumed it, and read the project's comment stream into a status update. Reference operations exist for the values the writes need, since task fields, colors, roles, and languages are all per account rather than universal, and a flow reads them rather than assuming them. The recalculation is what makes this connector powerful and also what makes a human-in-the-loop gate necessary, because one small input can move a lot of committed dates.

Without FlowRunner

Schedules maintained by dragging A change in scope means a person moves bars until the chart looks right again

Calendars updated late Holidays reach the plan after commitments have already been made against the old dates

Estimates never compared to reality Logged hours sit in a time tracker that the schedule never reads

With FlowRunner

Schedules computed from facts The agent supplies durations, links, and calendars, and the plan recalculates itself

Calendars updated with the slip shown A working day change is proposed with the end date movement it causes attached

Estimates checked against logs Time logged per resource is read back against the estimate that justified the date

Use Case Scenarios

The approved scope becomes a task tree

A statement of work is signed in DocuSign or a scope document is finalized in Google Docs. The agent calls Create Project, setting the duration view and estimation mode up front because they decide how every task in the project is measured afterwards. It then builds the tree with Create Task, supplying a start date and a duration rather than all three date fields, and wires the sequence with Create Link so the schedule moves as a unit. Assign Task Resources attaches the people and the share of their capacity each task consumes, which is what makes the workload view meaningful rather than decorative. The plan that comes out is the plan the contract was priced on.
Estimates checked against what actually happened

Hours are captured wherever the team really records them, in Harvest, Toggl, or Clockify. The agent matches each approved entry to its task and calls Create Time Log for the reporting resource, expressed in the project's own estimation unit. Once a week it reads List Project Time Logs against the task estimates and appends the variance per resource and per task to a sheet in Google Sheets, with the tasks whose estimate was furthest from reality called out to the delivery lead in Slack. The next plan is estimated from evidence instead of optimism.
The status update that writes itself

Client updates usually get assembled by hand from three places. The agent calls List Project Comments to read the whole project's discussion without walking task by task, List Tasks for progress and slipped dates, and List Project Attachments for what has been delivered. It drafts a status summary grouped by workstream, names the tasks that moved and why the comments say they moved, and posts the draft for the account lead to edit before it goes out. The assembly is automated. The claim to the client is not.

Human-in-Loop Highlight

The most consequential write in this connector looks like a housekeeping task. Create Custom Day adds a holiday or a shortened working day to a project's calendar, and because the calendar is what turns a duration into dates, every task whose chain crosses that day moves, along with everything linked downstream of it. Pushing next year's public holidays into every project in one pass is exactly the kind of chore worth automating, and it is also a single call that can shift committed delivery dates across an entire portfolio with no preview and no undo beyond deleting the day again.

So the calendar agent does the arithmetic and then stops. It reads List Project Calendars and List Tasks, computes the projected end date for each affected project, and asks the delivery lead: "Adding 8 public holidays to the Northfield rollout calendar moves its end date from 14 November to 26 November. Three tasks on the critical path shift past the client milestone on 20 November. Apply to this project, apply to all 11 projects, or skip the ones with committed milestones?" The lead decides which dates are allowed to move, and the agent writes only that. Delete Task carries a similar warning for a different reason: it removes the task and its subtasks along with their links, comments, attachments, and time logs, which means it deletes a billing record as well as a plan item.

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

47 actions

Team and Projects

Get Team Retrieves the team the API key belongs to. Used to confirm which account a connection points at before anything writes to it.
List Projects Retrieves every project in the team with its dates, status, and configuration, in a single unpaginated response.
Get Project Retrieves one project including its calendar configuration and duration view. Read before any write whose meaning depends on the estimation unit.
Create Project Creates a project. The duration view and estimation mode decide how every task in it is measured afterwards, so a flow sets them here rather than correcting later.
Update Project Updates a project's description or its favorite flag. GanttPRO exposes only these two fields on this route, so the name and calendar are not editable through the API.
List Project Task Fields Retrieves the task fields available on a project including its custom fields. Read before writing custom field values, since the field identifiers are per account.

Calendars and Working Days

List Project Calendars Retrieves the working calendars of the team's projects, with their working hours, working days, and custom days. This is what decides how a duration becomes dates.
Create Custom Day Adds a custom day to a project's calendar, which is how a holiday or a shortened working day is expressed. It moves every dependent task's dates, which is why this page's human gate sits here.
Update Custom Day Updates a custom day on a project's calendar, rescheduling the tasks that depend on those dates.
Delete Custom Day Removes a custom day, returning those dates to the normal working pattern and rescheduling the tasks that depended on them.

Users

List Users Retrieves the users in the team with their roles and locales. Users are the people who sign in; resources are what tasks are assigned to, and the two lists are not the same.
Get User Retrieves one user including their locale and display settings.
Update User Updates a user's locale or display settings.
Update User Notification Switches one of a user's notification settings on or off. The environment and action type together name which notification is being changed.

Tasks

List Tasks Retrieves the tasks of a project with dates, durations, progress, and assigned resources. Always read within one project, because that is how GanttPRO scopes tasks.
Get Task Retrieves one task including its custom field values and resource assignments.
Create Task Creates a task in a project, optionally nested under a parent. Supply two of start date, end date, and duration and let GanttPRO derive the third, since sending all three means the end date is ignored and recalculated anyway.
Update Task Updates a task's editable fields, sending only what changed. The same date arithmetic applies, so a start date and a duration are enough to move the end.
Delete Task Permanently deletes a task and its subtasks, and the links, comments, attachments, and time logs attached to them go too. Reviewed before it runs, because time logs are billing records.

Resources and Assignments

Assign Task Resources Assigns resources to a task, adding to whatever is already assigned. Each entry carries how much of that resource the task consumes, which is what drives the workload view.
Update Task Resources Replaces the resource assignments on a task. The overwriting counterpart, used when the assignment set is being restated rather than extended.
Remove Task Resources Removes resource assignments from a task. Time already logged by those resources against the task is kept.
List Resources Retrieves the team's resources, the people and things tasks are assigned to. A resource can exist without a login, so this is not the same list as the users.

Dependencies

Create Link Creates a dependency between two tasks, which is what makes one move when the other does. GanttPRO refuses a self link and allows only one link between a given pair.
Get Link Retrieves one dependency by its identifier.
Update Link Changes a dependency's type or lag, which reschedules the target task.
Delete Link Removes a dependency, freeing the target to be scheduled independently.

Comments

List Task Comments Retrieves the comments on one task.
List Project Comments Retrieves every comment across a project's tasks, which is how a flow reads the discussion without walking tasks one by one.
Create Comment Adds a comment to a task, attributed to a specific user. GanttPRO requires the user rather than inferring it, because the key belongs to the team rather than to a person.
Update Comment Rewrites the text of a comment. Pointed only at comments the automation itself wrote.
Delete Comment Permanently deletes a comment from a task.

Attachments

List Task Attachments Retrieves the files attached to one task.
List Project Attachments Retrieves every file attached across a project's tasks, which is also how a flow sees what is consuming the account's storage.
Add Task Attachment Attaches a file to a task by fetching it from a URL and uploading it. The account has a storage limit, and the upload is refused once it is reached.
Delete Attachment Permanently deletes one attachment, freeing its storage.
Delete Attachments Permanently deletes several attachments in one call, which is how a cleanup job reclaims storage without one request per file.

Time Logs

List Task Time Logs Retrieves the time logged against one task, with the reporting resource and the date.
List Project Time Logs Retrieves every time log across a project's tasks. This is what a project timesheet reads from.
Get Time Log Retrieves one time log entry.
Create Time Log Logs time against a task for a resource, expressed in the project's estimation unit, so a flow reads the project configuration rather than assuming hours.
Update Time Log Changes a time log's amount, date, resource, or note, and the task's reported total moves with it.
Delete Time Log Permanently deletes a time log. The amount comes off the task's reported total and off every report that included it.

Account Reference Data

List Account Roles Retrieves the account level roles and the rights each one grants, which govern what a person can do across the whole team.
List Project Roles Retrieves the project level roles and the rights each one grants inside a single project.
List Languages Retrieves the interface languages GanttPRO supports, which are the values a user locale update accepts.
List Colors Retrieves the task colors available in the account, which are the values a task's color parameter accepts.

Frequently Asked Questions

What can FlowRunner do with GanttPRO?

FlowRunner agents can run Get Team, List Projects, and Get Project in GanttPRO, plus 44 more actions.

Does connecting GanttPRO to FlowRunner require OAuth?

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

Can GanttPRO trigger a FlowRunner workflow automatically?

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

Start building with GanttPRO

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us