Integrations
The plan stays in Planitude; everything else stays where people work. Tasks sync with Jira and Azure DevOps, updates reach Slack and Microsoft Teams, deadlines appear in your calendar, and your AI assistant reads and updates the plan. Each connection takes a few clicks and can be removed at any time.
5 integrations
All integrations are included for free.
Where to find it
Open a project, choose ⋯ in the top bar, then Integrations or Notifications. Each app has its own page with the connection status, the settings and a disconnect button.
How it works
For each main integration: how to connect it, what travels in which direction and who has the last word when both sides change the same thing.
Work management
Each task becomes an issue in the Jira project you choose, and every change travels on its own within seconds. Planitude decides the plan, Jira decides who works on what and how far along it is.
Work management
The same model as Jira, for teams on Azure DevOps: each task becomes a work item, dependencies become Successor links, and state and assignee come back to the plan.
Communication
The team sees what matters without opening the plan: completed tasks, moved deadlines, new assignments, plus a morning summary and a weekly one.
Communication
Two independent parts. Notifications go to a channel through a Teams Workflow, with no app to install. The Planitude tab shows the project's Gantt chart inside Teams.
Communication
Link your account and ask in plain language: “How are we doing?”, “What is late?”, “Will we finish on time?”. The Planitude AI assistant answers in the chat, about the projects you can see and with your role. From Telegram you only check: changes are made in the app.
Calendars
A private calendar link puts your tasks and milestones in the calendar you already use; a morning email reminds you what is due.
AI and MCP
Planitude has an MCP server: your assistant can answer “are we on time?”, list late tasks or move a phase, always with your permissions.
Automation and developers
For everything that does not have a ready-made integration: a signed event as soon as something changes, and an API to read and write the plan.
Files
Drop the file, check the preview and the project is ready, with dependencies, calendars and baselines. No software to install and no licenses.
Files
The plan is never locked in Planitude: export it in a format Microsoft Project opens, to a spreadsheet, or as an image or PDF to attach to a report.
Reports
An OData feed in read-only mode: Power BI and Excel load your plans as tables and refresh them when you want, with no file to export.
Automation
The apps for Zapier, Make and n8n are ready and being published. They will use the same webhooks and the same REST API that you can already connect today with each platform’s HTTP modules.
Files
A PowerPoint add-in draws the project’s Gantt chart on a slide with native shapes, which stay editable, and refreshes it from Planitude data without touching the rest of the slide.
No. Every integration is included in Planitude, which is free. You only need your own access to the other tool (for example a Jira, Slack or Microsoft 365 account) under its own terms.
Connections use the official sign-in of each service (OAuth) whenever possible. Tokens and addresses are encrypted at rest, never shown in full and never written to logs. Incoming messages from Jira, Azure DevOps and Slack are verified before they are used.
Only what the connection needs. Jira and Azure DevOps receive the tasks of the connected project; Slack and Teams receive the updates you choose; AI assistants see only the projects you can open, with your role, and with read-only access they cannot change anything.
From the app's page in the project, with Disconnect, at any time. Nothing is deleted: tasks stay in Planitude, issues and messages stay in the other tool. Connected AI apps are revoked from Profile → API keys.
The owner and the editors of the project. Viewers see the status of the connections but cannot change them. Calendar links and email reminders are personal and everyone manages their own.
Not at the moment: the integration works with Jira Cloud. For other systems you can use the REST API and the webhooks.
Blog
Planitude integrations: Jira, Azure DevOps, Slack, Teams, calendars, ChatGPT, Claude and Gemini via MCP, API and webhooks, .mpp and .xer files. Which to choose.
Blog
Syncing a Gantt chart with Jira Cloud: who owns dates and status, dependencies as Blocks links, conflicts and deletions. A step-by-step guide with Planitude.
Blog
Project notifications in Slack and Microsoft Teams with Planitude: what reaches the channel, noise filters, the Monday summary, Teams Workflows and a Gantt tab.
Blog
Connect ChatGPT, Claude and Gemini to Planitude plans with MCP: critical path, delay impact, Monte Carlo, edits with a preview, OAuth and permissions.
Developers
Authentication, rate limits, webhook signatures and the OpenAPI 3.1 reference.
The trademarks mentioned (Jira, Azure DevOps, Slack, Telegram, Microsoft Teams, Microsoft Outlook, Microsoft PowerPoint, Microsoft Project, Microsoft Power BI, Microsoft Excel, Visual Studio Code, Google Calendar, Gemini, Apple Calendar, ChatGPT, Codex, Claude, Cursor, Zapier, Make, n8n, Primavera) belong to their respective owners; Planitude is not affiliated with or endorsed by them. Power BI and Excel are trademarks of Microsoft Corporation. Planitude is not affiliated with Microsoft.
Advertising keeps Planitude free
