--- title: "Planitude integrations: Jira, Slack, Microsoft Teams, ChatGPT" description: "Free Jira integration with two-way sync, Gantt chart for Microsoft Teams, Slack notifications, Azure DevOps, calendar sync, ChatGPT and Claude via MCP, REST API and webhooks." url: https://planitude.app/integrations language: en --- # Planitude connects to the tools your team already uses 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. All integrations are included for free. [Create a free account](https://planitude.app/signup) ## All integrations Grouped by what they do. Each card says what the connection is for; the main ones are explained step by step further down. ### Work management Two-way sync with the tools developers already plan in. - **Jira Cloud** (Available): Two-way sync between tasks and issues of a Jira Cloud project. - **Azure DevOps Boards** (Available): Two-way sync between tasks and work items, with a Microsoft account or a personal token. ### Communication Project updates where the team talks. - **Slack** (Available): Project updates in a channel and the /planitude status command. - **Microsoft Teams** (Available): Updates in a channel through Workflows and a tab with the Gantt chart. - **Email reminders** (Available): One email at 8:00 with the deadlines that concern you. ### Calendars Your tasks and milestones next to your meetings. - **Google Calendar** (Available): Subscribe to your private calendar link. - **Microsoft Outlook** (Available): Subscribe to your private calendar link. - **Apple Calendar** (Available): Subscribe to your private calendar link. ### AI and MCP Assistants and coding tools that read and update your plans. - **ChatGPT** (Available): Connector with OAuth: add the server address, sign in, allow. - **Claude** (Available): Custom connector on Claude.ai with OAuth, no key to copy. - **Gemini** (Available): Custom app with OAuth (Google currently limits it to personal accounts in the US). - **Claude Code** (Available): MCP server with OAuth or an API key. - **Codex** (Available): MCP server with OAuth or an API key. - **Cursor** (Available): MCP server in mcp.json, with OAuth or an API key. - **Gemini CLI** (Available): MCP server with OAuth or an API key. - **Visual Studio Code** (Available): MCP server in .vscode/mcp.json, with OAuth or an API key. ### Automation and developers Events and data for your own workflows. - **Webhooks** (Available): Signed HTTPS events whenever something changes in a project. - **REST API** (Available): Read and write projects and tasks; OpenAPI 3.1 reference. - **Zapier** (Coming soon): Triggers and actions for thousands of apps. - **Make** (Coming soon): Scenarios with Planitude modules and instant triggers. - **n8n** (Coming soon): Community node, also for self-hosted n8n. ### Files Plans in and out, without retyping. - **Microsoft Project** (Available): Import .mpp, .mpt, .mpx and XML files; export to Microsoft Project XML. - **Primavera P6** (Available): Import Primavera P6 .xer and .pmxml files. - **Export** (Available): Microsoft Project XML, CSV, print and PDF. - **Microsoft PowerPoint** (Coming soon): Add-in that draws the Gantt chart on a slide. ## Everything starts from the project 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. - Project owners and editors can connect; viewers see the status - Connected apps appear at the top, the others by category - Calendar and email reminders are personal settings in your profile ## Three steps, then it runs on its own 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. ### Jira integration: the Gantt chart and the issues stay aligned 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. Apps involved: Jira Cloud 1. **Connect Jira Cloud**: From the project, open Integrations → Jira and sign in with Atlassian. Planitude acts with your Jira account and your permissions. 2. **Choose the project**: Pick the Jira project and the issue type, check how statuses map to progress and who is who. Then export the plan to Jira, import the existing issues, or both. 3. **Keep working as usual**: Move a bar in the Gantt and the issue changes; close an issue in Jira and the task reaches 100%. Conflicts and errors are listed on the integration page. **What travels where** (→ From Planitude to Jira, ← From Jira to Planitude) - → Task name and notes → issue summary and description (Planitude decides) - → Start and finish → start date and due date (Planitude decides: a date changed in Jira is set back to the plan) - → Finish-to-start dependencies → “blocks” links between issues - ← Issue status → task progress (Jira decides) - ← Assignee → person assigned to the task (Jira decides) - Nothing is ever deleted automatically: a deleted task leaves the issue in Jira with the label planitude-unlinked, and a deleted issue leaves the task in the plan. - Summary tasks can become Epics, with the issues of the phase underneath. - Jira Cloud only; Jira Data Center and Server are not supported. [Read the full guide](https://planitude.app/blog/gantt-jira-sync) ### Azure DevOps Boards: work items and plan in sync 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. Apps involved: Azure DevOps Boards 1. **Connect Azure DevOps**: Sign in with your Microsoft work account, or paste a personal access token with Work Items (read and write) if your organization does not allow external apps. 2. **Choose organization and project**: Planitude detects the process (Agile, Scrum, Basic, CMMI). Choose the work item type and the state mapping, then export the plan, import the work items, or both. 3. **Keep working as usual**: Changes travel in both directions; every work item gets an “Open in Planitude” link back to the task. **What travels where** (→ From Planitude to Azure DevOps, ← From Azure DevOps to Planitude) - → Task name and notes → work item title and description (Planitude decides) - → Start and finish → start and target dates (Planitude decides) - → Finish-to-start dependencies → Successor and Predecessor links - ← Work item state → task progress (Azure DevOps decides) - ← Assigned To → person assigned to the task (Azure DevOps decides) - No automatic deletions in either direction. - Personal Microsoft accounts cannot use Microsoft sign-in with Azure DevOps: use a personal access token. - Phases can become Features or Epics, with the work items underneath. ### Slack: project updates in the channel The team sees what matters without opening the plan: completed tasks, moved deadlines, new assignments, plus a morning summary and a weekly one. Apps involved: Slack 1. **Add to Slack**: From the project, open Notifications → Slack, choose the workspace and allow. Public channels are ready at once; for a private one, first type /invite @planitude there. 2. **Choose channel and updates**: Pick the channel, which updates to send, how to group close changes (from immediately to 60 minutes), the language and the time zone of the messages. 3. **Read and ask**: Updates arrive in the channel with a link to the task. Type /planitude status to get the project status: only you see the answer. **What travels where** (→ From Planitude to Slack, ← From Slack to Planitude) - → Completed tasks, dates moved on critical tasks and milestones, new assignments - → At 8:00: tasks due the next working day and overdue tasks - → On Monday at 9:00: weekly summary with progress, delay against the baseline and next milestones - ↔ /planitude status: you ask from the channel, Planitude answers only to you - Pause or disconnect in one click; when no other project uses the workspace, the Slack token is revoked. - The command only sees the projects connected to that channel. [Read the full guide](https://planitude.app/blog/teams-slack-project-notifications) ### Gantt chart for Microsoft Teams: updates in the channel and the plan in a tab 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. Apps involved: Microsoft Teams 1. **Create a Workflow in the channel**: In Teams, open ⋯ next to the channel → Workflows → “Send webhook alerts to a channel”, then copy the address it shows at the end. 2. **Paste it into Planitude**: From the project, open Notifications → Microsoft Teams, paste the address and choose updates, grouping, language and time zone, as for Slack. 3. **Add the Gantt tab**: Add the Planitude app to Teams (your Teams administrator can upload it), add the tab to the channel and choose the project. **What travels where** (→ From Planitude to Microsoft Teams, ← From Microsoft Teams to Planitude) - → Completed tasks, dates moved on critical tasks and milestones, new assignments - → Morning summary at 8:00 and weekly summary on Monday - → Gantt chart of the project in a tab, read-only, for people who have access to the project - Messages are posted by Microsoft's “Workflows” bot: its name and icon cannot be changed. - The Workflow address is encrypted and only shown shortened; the tab signs in with your Planitude account. [Read the full guide](https://planitude.app/blog/teams-slack-project-notifications) ### Google Calendar, Outlook and Apple Calendar: deadlines next to your meetings A private calendar link puts your tasks and milestones in the calendar you already use; a morning email reminds you what is due. Apps involved: Google Calendar, Microsoft Outlook, Apple Calendar, Email reminders 1. **Create your link**: In your profile, under Calendar, create the private link: all projects or one, only your tasks or all of them. 2. **Add it to your calendar**: In Google Calendar, Outlook or Apple Calendar, add a calendar “from URL” or “subscribe” and paste the link. 3. **Let it update itself**: Changes to the plan reach the calendar at the refresh interval of your calendar app. Email reminders are on by default. **What travels where** (→ From Planitude to Calendar, ← From Calendar to Planitude) - → Tasks and milestones → calendar events (read-only) - → Email at 8:00 with tasks due the next working day, overdue tasks and deadlines - The link can be revoked and regenerated at any time; the old one stops working. - Reminders can be turned off from your profile or with one click from the email. ### ChatGPT, Claude, Gemini and coding tools, through 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. Apps involved: ChatGPT, Claude, Gemini, Claude Code, Codex, Cursor, Visual Studio Code 1. **Add Planitude**: In ChatGPT, Claude.ai or Gemini, add a connector with the server address shown in Profile → API keys. In Claude Code, Codex, Cursor, Gemini CLI or VS Code, add the same address to the MCP configuration. 2. **Sign in and allow**: Sign in to Planitude and choose read-only or read and write access. Developer tools can also use an API key created in your profile. 3. **Ask**: “Which tasks are late?”, “What is on the critical path?”, “Move testing one week later.” The assistant works on the real plan. **What travels where** (→ From Planitude to Assistant, ← From Assistant to Planitude) - ← The assistant reads projects, tasks, critical path, workload, risk and portfolio - ↔ With write access it creates and updates tasks and dependencies; it cannot delete projects or tasks - The Planitude app in the ChatGPT directory is under review by OpenAI; meanwhile ChatGPT connects with the server address. - In Gemini, custom apps are currently available only for personal accounts in the United States (a Google limit). - Connected apps are listed in Profile → API keys → Connected apps, where you can revoke them. [Read the full guide](https://planitude.app/blog/chatgpt-claude-gemini-mcp-project-plans) · [Developer documentation](https://planitude.app/developers) ### Webhooks and REST API for your own automations 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. Apps involved: Webhooks, REST API 1. **Create an API key**: In Profile → API keys, read-only or read and write, optionally limited to one workspace and with an expiry date. 2. **Register a webhook**: On one project or on a whole workspace, choosing among 14 events: tasks created, completed or moved, dependencies, baselines, comments and more. 3. **Receive and call**: Verify the HMAC-SHA256 signature of each event and call the REST API documented in OpenAPI 3.1. **What travels where** (→ From Planitude to Your system, ← From Your system to Planitude) - → Signed events whenever something changes, from the web app, the API, MCP or an import - ↔ REST API: read and write projects, tasks, assignments and dependencies - Zapier, Make and n8n are coming soon and will use this same API and these webhooks. - Keys and connected apps cannot delete projects or tasks: deleting stays in the web app. [Developer documentation](https://planitude.app/developers) ## Frequently asked questions ### Do the integrations cost anything? 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. ### How are my accounts protected? 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. ### What does the external app see? 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. ### How do I disconnect an integration? 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. ### Who can connect a project? 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. ### Do you support Jira Data Center or Server? Not at the moment: the integration works with Jira Cloud. For other systems you can use the REST API and the webhooks. ## Guides and documentation - [The tools to connect to Planitude: a guide to integrations](https://planitude.app/blog/planitude-integrations-guide) - [Gantt and Jira: how to keep the plan and the work aligned](https://planitude.app/blog/gantt-jira-sync) - [Project notifications in Microsoft Teams and Slack](https://planitude.app/blog/teams-slack-project-notifications) - [Using ChatGPT, Claude and Gemini on your project plans with MCP](https://planitude.app/blog/chatgpt-claude-gemini-mcp-project-plans) - [API, webhooks and MCP](https://planitude.app/developers) ## Connect your first tool in two minutes Create a free account, open a project and choose Integrations from the ⋯ menu. [Create a free account](https://planitude.app/signup) *The trademarks mentioned (Jira, Azure DevOps, Slack, Microsoft Teams, Microsoft Outlook, Microsoft PowerPoint, Microsoft Project, 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.*