Help Center / API and developers /
Webhook integration
Outbound webhooks send real-time data to external services whenever events happen in your workspace. When an invoice is created, a form submission comes in, or a task is updated, Plutio sends a JSON payload to your specified URL. Webhooks connect Plutio with Zapier, Make (Integromat), custom APIs, or any service that accepts HTTP POST requests.
How to add a webhook
- Go to Settings > Integrations.
- Find the Webhooks section and click to add a new webhook.
- Enter the target URL. The URL is the endpoint on your external service that will receive the data (e.g., a Zapier webhook URL or your own API endpoint).
- Select which events trigger the webhook. Events follow a generic pattern:
{entity}.create,{entity}.edit, and{entity}.removefor supported entities such as invoices, tasks, projects, contacts, proposals, contracts, and forms. Each webhook can listen to one or more specific event types. - Save the webhook.
Event methods
Webhook methods decide which events are delivered to the webhook URL. Events use the pattern {entity}.create, {entity}.edit, and {entity}.remove for supported entities. If a method is not selected on the API client, Plutio does not queue webhook deliveries for that event.
Event methods do not create read-only API access. They only filter outbound webhook deliveries.
Payload format
The webhook payload is a JSON object containing the full entity data for the event that triggered the request. An "invoice paid" webhook, for example, includes the invoice amount, client, status, and payment information. The payload structure matches the entity's REST API format, so the same fields available through the API are included in the webhook body.
Adding multiple webhooks
You can add as many webhooks as you need. Each webhook has its own URL and event selection, so different services can receive different event types. For example, one webhook might send invoice events to your accounting tool while another sends form submissions to a CRM.
Retry logic
When a webhook delivery fails (the receiving server returns an error or doesn't respond), Plutio retries the request up to ten times with exponential backoff delays ranging from five minutes to forty-eight hours. Retries give the receiving service time to recover from temporary outages, so transient failures don't result in missed events.
