Skip to main content

What is a Webhook in Event Temple?

A Webhook in Event Temple is an automated method for sending real-time information to another system whenever a specific event occurs.

Updated yesterday

It allows Event Temple to communicate instantly with external applications — for example, when a booking becomes definite or an event is updated.

When the chosen event happens, Event Temple sends a POST request containing the data to a designated Target URL, which is typically an endpoint provided by another platform or service you use.


How to Create a New Webhook

To set up a new webhook:

  1. Go to Settings → Integrations → Webhooks.

  2. Click New Webhook.

  3. Select an Event from the list.

  4. Enter the Target URL — this is where Event Temple will send data when the event occurs.

  5. (Optional) Add a Secret Token for extra security.

  6. Click Create to save the webhook.


Event Options

When creating a new webhook, you can select from several available event triggers, including:

  • leads.definite – Fires when a lead becomes definite.

  • event.created – Fires when a new event is created.

  • event.updated – Fires when an existing event is updated.

  • event.deleted – Fires when an event is deleted.

  • document.signed – Fires when a document is signed.

  • document.shared – Fires when a document is shared.

Each of these events allows Event Temple to push relevant data to your external system automatically, ensuring both platforms remain synchronized.


Notes

  • Webhooks require a valid and active Target URL from the receiving system.

  • The Secret Token helps authenticate requests using SHA-1 encryption.

  • Webhooks are generally configured by technical users or administrators familiar with APIs.


Summary:
Webhooks in Event Temple are a powerful automation feature that send real-time updates to other systems whenever specific actions — like creating or updating an event — occur. They help streamline data flow and improve integration between Event Temple and your external tools.

Did this answer your question?