Webhooks

Webhooks notify external systems when supported records change in Agiled.

Create a Webhook Subscription

1. Open Settings.
2. Go to API.
3. In Webhooks, enter the target URL.
4. Add a description.
5. Select one or more events.
6. Select Create subscription.
7. Copy the webhook secret immediately.

Available Events

Supported events include:

• contact.created
• contact.updated
• account.created
• account.updated
• deal.created
• deal.updated
• ticket.created
• ticket.updated
• project.created
• project.updated
• task.created
• task.updated
• invoice.created
• invoice.updated
• invoice.paid
• payment.created
• payment.updated
• time_entry.created
• time_entry.updated

Payload Shape

Webhook payloads include:

{
  "id": "event-id",
  "event": "contact.created",
  "organization_id": "organization-id",
  "occurred_at": "2026-05-18T12:00:00.000Z",
  "data": {}
}

Delivery History

Use delivery history in Settings > API to confirm whether Agiled sent the event successfully and to review endpoint failures.

Production Receiver Checklist

Before subscribing a production endpoint:

1. Verify signatures with the raw request body.
2. Store the event or delivery ID before side effects.
3. Return 2xx only after the event is accepted.
4. Queue slow work instead of holding the webhook request open.
5. Log event type, delivery ID, target URL, and processing status.

Start with one low-volume event such as contact.created. After the receiver is stable, add higher-volume events and monitor delivery history for failures.

Event Selection

Subscribe only to events your receiver actually uses. Broad subscriptions make logs noisy, increase retry volume, and can hide failures for the events that matter. If a downstream system only needs paid invoice updates, subscribe to payment and invoice payment events instead of every finance event.

Review event selection after changing workflows, imports, or sync ownership.

Related Docs

• Verify Webhook Signatures
• Receive Webhook Events
• Webhook Endpoints