You can easily connect Simplicate to your favorite no-code automation tool using webhooks, such as Zapier, n8n, or Make. This allows you to trigger actions or processes based on events in Simplicate without any manual effort. Simplicate ensures the tool receives the right notification when something happens in Simplicate; the automation tool handles the subsequent automated steps.
For the most up-to-date list and technical details about webhooks, visit our developer page
Go to Settings → Account → Webhooks to set up webhooks. Here you'll find a list of available webhooks. Enter the trigger URL of the automation system and a name to identify the webhook.
In your webhook overview, you can see which webhooks are currently active and which events they are listening to.
Available webhooks in Simplicate
The following webhooks are available in Simplicate:
The groups and names below appear in the same order as in the webhook screen, so you can match them one-to-one.
Absence
Webhook | Notes |
Absence created | A webhook is sent for each new absence registration. An ongoing absence registration does not send a new webhook every day. |
Assignment
Webhook | Notes |
Assignment completed | Triggers when an assignment receives an assignment status that means "Done" (only when assignment statuses are enabled). For a regular status change, "Assignment updated" is sufficient. |
Assignment created |
|
Assignment deleted |
|
Assignment updated |
|
Contact Person
Webhook | Notes |
Contact person created |
|
Contact person updated |
|
Expenses
Webhook | Notes |
Expense created |
|
Expense deleted |
|
Expense updated |
|
Hours
Webhook | Notes |
Hours correction created |
|
Hours correction deleted |
|
Hours correction updated |
|
Hours created | Triggers for hours on direct (billable) and indirect (non-billable) projects, and for leave and absence registrations. |
Hours deleted |
|
Hours updated |
|
Insights
Webhook | Notes |
Insights updated | This webhook fires when the materialization of your Insights data is completed, without distinguishing between individual materializations. |
Invoice
Webhook | Notes |
Invoice approved by customer | Only available with the staffing add-on |
Invoice credited |
|
Draft invoices generated | Triggers when draft invoices are generated collectively, as soon as the run has finished and at least one draft invoice was created. A single draft invoice you create yourself does not trigger this webhook. |
Invoice emailed to customer |
|
Invoice paid |
|
Invoice payment received |
|
Invoice payment reminders paused |
|
Reminder emailed to customer |
|
Invoice resent |
|
Invoice moved to sent status | Also triggers when an invoice is printed |
Leave
Webhook | Notes |
Leave approved |
|
Leave created | 1 leave series triggers 1 event |
Leave declined |
|
Organization
Webhook | Notes |
Organization created |
|
Organization updated |
|
Person
Webhook | Notes |
Person created |
|
Person updated |
|
Project
Webhook | Notes |
Project closed | Triggers when the project status changes to "Closed". A project does not close automatically when the end date is reached. |
Project created |
|
Project deleted |
|
Project end date reached |
|
Project updated |
|
Project service
Webhook | Notes |
Project service created |
|
Project service deleted |
|
Project service updated |
|
Project service budget
Webhook | Notes |
Project service hours budget reached 100% | Triggers only the first time the budget reaches this value. If the budget is changed afterward, it does not trigger again. |
Project service hours budget reached user-defined threshold | You set the threshold yourself; the webhook triggers as soon as the hours budget reaches that value. |
Project service value budget reached user-defined threshold | You set the threshold yourself; the webhook triggers as soon as the value budget reaches that value. |
Purchase
Webhook | Notes |
Purchase created | Also triggers when a purchase invoice is created from a purchase integration (e.g. Exact or Twinfield), as soon as it appears in the project purchasing module ("to be processed" or "processed"). |
Purchase deleted |
|
Purchase updated |
|
Purchase line
Webhook | Notes |
Purchase line created | Triggers when a purchase line is added to a purchase entry/invoice, including from a purchase integration (Exact/Twinfield). |
Purchase line deleted |
|
Purchase line updated |
|
Sale
Webhook | Notes |
Sale quote approved | When a quote is digitally signed. |
Sale quote expired |
|
Sale quote sent |
|
Sale accepted | Triggers when the sale gets the status "Accepted". |
Sale created |
|
Sale declined | Triggers when the sale gets the status "Declined". |
Sale linked to project |
|
Sale progress changed |
|
Sale updated |
|
Subscription
Webhook | Notes |
Subscription created |
|
Subscription end date entered |
|
Subscription end date reached | Triggers when the subscription end date is reached |
Subscription start date reached | Triggers when the subscription start date is reached |
Subscription term changed |
|
Week
Webhook | Notes |
Week approved |
|
Week declined |
|
Week reopened | Triggers when a previously submitted week is reopened. |
Week submitted |
|
Workflow
Webhook | Notes |
Workflow created | Triggers as soon as a new workflow is created. This includes workflows Simplicate starts itself: for example on an approved quote, a leave request, a declined timesheet week, and for every project in a bulk action. |
Step-by-step guide for automation
Create a receiving address
This is a special URL from the automation tool that will receive the notification. In tools like Zapier, n8n, or Make, you can create a trigger URL or receiving address.Determine when the webhook should fire
In Simplicate, you configure when a webhook should fire based on an event.Enter the receiving address in Simplicate
In Simplicate, enter the special URL of the tool that should receive the webhook.
Choose what steps to take after receiving the webhook
Once the automation tool receives the webhook, the next steps can be executed. You configure these steps in the automation tool.Test the webhook
For example, create a test sale and check whether the automation works.


