The tools to connect to Planitude: a guide to integrations

A schedule loses its value the day it stops matching the real work. It happens when tasks live in a ticketing system, conversations in a chat tool and deadlines in a calendar, while the Gantt chart remains a separate document that someone updates by hand once a week.

Planitude integrations are designed to prevent that gap: the plan, with its dependencies, calendars and critical path, remains the source of dates, and the other tools receive or return the information they are responsible for. This guide presents them one by one and suggests which ones to turn on first.

Why connect the plan to your team’s tools#

A project plan answers a precise question: when will we finish, and what could delay us? Answering it takes dependencies, durations and calendars. Operational tools answer other questions: who is working on what, what is blocked, what has been discussed.

Connecting the two worlds brings three concrete benefits:

• fewer manual updates: progress comes from the tracker rather than from a status meeting;
• delays surface earlier: if a critical task slips, the team channel knows straight away;
• one source for dates: whoever plans does not have to chase dates changed in three different tools.

All integrations are available inside the project, from the ⋯ › Integrations or ⋯ › Notifications menu, and are described on the Integrations page.

The available integrations at a glance#

Software development: Jira and Azure DevOps#

Jira shows dependencies on the timeline with the “Blocks” link type and flags in red when two linked items overlap^[2], but recalculating dates from dependencies and the critical path are not among the features it describes. That is where a scheduling engine helps: Planitude calculates the dates, Jira remains the tool where the team works.

The Jira Cloud sync creates an issue for each task (or imports existing issues), turns finish-to-start dependencies into “Blocks” links and applies a clear rule: Planitude owns name, notes, dates and dependencies; Jira owns status and assignee. The details are in the article Gantt and Jira.

The Azure DevOps Boards integration follows the same model: sign-in with Microsoft Entra ID or a Personal Access Token, the work item type detected from the process (User Story, Product Backlog Item, Issue or Requirement), dependencies as Successor/Predecessor links, and no automatic deletion on either side.

Communication: Slack, Microsoft Teams, email and calendars#

Channel notifications are designed not to become noise. Only the events that matter are posted: completed tasks, date changes on critical tasks and milestones, new assignments, tomorrow’s deadlines and overdue tasks. Updates that arrive close together are grouped into a single message and, if you turn it on, every Monday morning the channel receives a summary of progress against the plan.

On Slack, the Add to Slack button and a channel choice are enough. On Microsoft Teams you use a channel Workflow: Microsoft switched off Office 365 connectors between 18 and 22 May 2026 and points to Workflows as the replacement^[3]. Teams also offers a read-only tab with the project’s Gantt chart. The full setup is in the article Project notifications in Microsoft Teams and Slack.

For individuals there are two simpler channels: the morning email with upcoming and overdue deadlines, sent only to people who have something due, and the synced calendar, a private iCal link to add to Google Calendar, Outlook or Apple Calendar, covering all projects or just one.

AI assistants: ChatGPT, Claude and Gemini with MCP#

The Model Context Protocol is an open standard for connecting AI applications to external systems^[1]. Planitude exposes an MCP server with tools to read projects, analyze the critical path and float, estimate the impact of a delay, run a Monte Carlo simulation and create or edit plans with a preview.

ChatGPT, Claude.ai and Gemini connect with OAuth: you enter the server address, sign in to Planitude and choose whether to allow changes as well. In Gemini, custom apps are currently available only to personal Google accounts of adults in the United States^[5]. Claude Code, Codex, Gemini CLI, Cursor and VS Code also work with an API key. The complete guide is in Using ChatGPT, Claude and Gemini on your project plans.

Developers and automation: API and webhooks#

For internal systems there is a REST API documented in OpenAPI 3.1, with keys created from your profile and read-only or read-and-write permissions. Outgoing webhooks send events such as tasks created, completed or rescheduled, projects created, comments and saved baselines: every delivery is signed, failed attempts are retried at increasing intervals, and an endpoint that keeps failing is disabled with an email notice. The documentation is on the Developers page.

Files: Microsoft Project and Primavera#

Not every integration goes through an API. Many plans arrive as files: Planitude imports Microsoft Project .mpp files and .mpt templates, .mpx, Project XML, Primavera .xer and PMXML, with tasks, links, constraints, calendars and baselines. Project desktop can still save projects as .mpp or XML^[4]. On the way out, every project can be exported to Microsoft Project XML, CSV or PDF. If you are coming from Project Online, see the guide Migrating from Project Online to Planitude.

Which one to choose for your team#

• Software teams on Jira or Azure DevOps: start with the two-way sync, then add a Slack or Teams channel for delays on critical tasks.
• PMOs and managers of several projects: connect an AI assistant through MCP for questions such as “which projects are at risk this week?” and turn on the Monday summary.
• Construction, events, implementations: email reminders and the synced calendar are enough for assigned people; a Teams or Slack channel for the coordination group.
• Internal systems and reporting: the API and webhooks, with a read-only key when no changes are needed.
• Migration from Microsoft Project or Primavera: import the files, check the critical path and save a baseline right away.

Coming soon#

Integrations with Zapier, Make and n8n, built on the same API and webhooks, are in preparation, along with a PowerPoint add-in that places a project’s Gantt chart on a slide and keeps it up to date. News is announced on the Integrations page.

Frequently asked questions#