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:

HRM: leave / absence

Webhook	Notes
Leave created	1 leave series triggers 1 event
Leave approved
Leave declined
Absence created	A webhook is sent for each new absence registration. An ongoing absence registration does not send a new webhook every day.

Sales

Webhook	Notes / trigger
Sale created
Sale updated
Sale progress changed
Sale linked to project
Sale quote approved	When a quote is digitally signed.
Sale quote sent
Sale quote expired

Projects

Webhook	Notes
Project created
Project updated
Project deleted
Project end date reached
Project (re)opened	Triggers when the project status changes to "Active", not when first created.
Project closed	Triggers when the project status changes to "Closed". A project does not close automatically when the end date is reached.

Purchasing

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 updated
Purchase deleted
Purchase line created	Triggers when a purchase line is added to a purchase entry/invoice, including from a purchase integration (Exact/Twinfield).
Purchase line updated
Purchase line deleted

Services

Webhook	Notes
Project service created
Project service updated
Project service deleted
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
Project service value budget reached user-defined threshold
Subscription created
Subscription term changed
Subscription end date entered
Subscription start date reached	Triggers when the subscription start date is reached
Subscription end date reached	Triggers when the subscription end date is reached

Capacity Planning / Assignments

Webhook	Notes
Assignment created
Assignment updated
Assignment deleted
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.

Hours

Webhook	Notes
Hours created	Triggers for hours on direct (billable) and indirect (non-billable) projects, and for leave and absence registrations.
Hours updated
Hours deleted
Hours correction created
Hours correction updated
Hours correction deleted

Expenses

Webhook	Notes
Expense created
Expense updated
Expense deleted

Timesheets

Webhook	Notes
Week submitted
Week approved
Week declined
Week reopened	Triggers when a previously submitted week is reopened.

Invoices

Webhook	Notes
Invoice emailed to customer
Invoice moved to sent status	Also triggers when an invoice is printed
Invoice resent
Invoice paid
Invoice payment received
Reminder emailed to customer
Invoice credited
Invoice payment reminders paused
Invoice approved by customer	Only available with the staffing add-on

Insights

Webhook	Notes
Insights updated	This webhook fires when the materialization of your Insights data is completed, without distinguishing between individual materializations.

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.

Webhooks