Help Center / API and developers /
API and third-party connections
Plutio's REST API and webhook system open your workspace to external automation platforms, so data flows between Plutio and tools like Zapier, Make (formerly Integromat), and n8n without custom development. The API covers full entity access, and webhooks trigger external actions the moment events happen inside Plutio.
The REST API
The API uses OAuth2 authentication and provides endpoints for creating, reading, updating, and deleting entities across your workspace. Projects, tasks, invoices, proposals, contracts, contacts, forms, time entries, wiki pages, and conversations are all accessible through standard HTTP methods (GET, POST, PUT, DELETE) with JSON request and response bodies. List endpoints support pagination for retrieving large data sets.
API calls vs webhook events
Use the REST API when an external tool needs to read or write Plutio data, and use webhooks when Plutio should notify another tool after something changes. A Zapier or Make scenario often uses both: a webhook starts the flow, then an API request reads more details or creates another record.
The event methods selected on an API client only control outbound webhooks. They do not limit what REST API endpoints the client can call.
Zapier
Zapier connects Plutio to thousands of other apps through triggers and actions. A Zapier trigger runs when a Plutio webhook sends data (e.g., "new invoice created"), and a Zapier action calls the Plutio API to push data back (e.g., "create a task"). Common Zaps include syncing new Plutio contacts to a CRM, posting invoice data to accounting software, and creating Plutio tasks from external form submissions.
Make and n8n
Make and n8n follow the same pattern as Zapier but offer visual workflow builders with advanced branching and logic. Webhook triggers from Plutio start a Make scenario or n8n workflow, and HTTP request steps call the Plutio API to read or write data. These platforms support filtering, error handling, and multi-step sequences, so complex automations like "when a proposal is accepted, create a project in your workspace and a channel in Slack" can run without writing code.
Common automation patterns
Here are a few examples of what you can build by connecting Plutio's API and webhooks to tools like Zapier, Make, or n8n:
- CRM sync: use a webhook to send new Plutio contacts to an external CRM like HubSpot or Salesforce.
- Accounting: when an invoice is marked as paid, push the data to Xero, QuickBooks, or FreshBooks via an automation platform.
- Task creation: form submissions on an external platform create tasks in your workspace through the API with mapped fields.
- Notifications: specific Plutio events like overdue invoices or completed tasks trigger Slack messages or email notifications through external services.
The combination of a full REST API and real-time webhooks means Plutio fits into any automation stack, with platforms like Zapier, Make, and n8n acting as the bridge between your workspace and the rest of your tools.
