Documentation
Webhooks: events, signatures and retries
Event catalog, HMAC-SHA256 signature verification and delivery with retries.
Automation and developers
Signed webhooks on every change to the plan
Receive a signed HTTPS event as soon as a task is created, completed or moved, in one project or across the whole workspace.
- Available
- Free, included in every account
What it does
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.
Where it helps
- Connect Planitude to an internal system, an ERP or a data warehouse.
- Trigger an automation as soon as a task is completed or moved.
- Create projects and tasks from another tool, without copying them by hand.
From Planitude to Your system
- Every change, from the web app, the API, MCP or an import → Signed events, From Planitude to Your system
Both ways
- Projects, tasks, assignments and dependencies ↔ Read and write via the REST API, Both ways
Setup
Connect it in three steps
Create an API key
In Profile → API keys, read-only or read and write, optionally limited to one workspace and with an expiry date.
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.
Receive and call
Verify the HMAC-SHA256 signature of each event and call the REST API documented in OpenAPI 3.1.
Requirements
- Plan
- Free. Every integration is included in every Planitude account.
- Who can connect it
- Every user, with their own API key. Project webhooks: owner or editor; workspace webhooks: owner or administrator.
- What you need
- A public HTTPS endpoint to receive webhooks; for the API, a key created in Profile → API keys.
Good to know
- 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.
Guides and documentation
Documentation
REST API: quickstart and reference
API key authentication, rate limits, pagination and the OpenAPI 3.1 reference.
Guide
The tools to connect to Planitude: a guide to integrations
Planitude integrations: Jira, Azure DevOps, Slack, Teams, calendars, ChatGPT, Claude and Gemini via MCP, API and webhooks, .mpp and .xer files. Which to choose.
Frequently asked questions about Webhooks
How do I check that a webhook really comes from Planitude?
Every request carries a header with a timestamp and the HMAC-SHA256 signature of the body: recompute it with the webhook secret and reject requests that are too old. The developer documentation has ready-made examples.
Can an API integration delete projects?
No. API keys and connected apps can read and, with write access, create and update, but deleting projects and tasks stays in the web app.
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 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.
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.