Using Webhooks

Webhooks allow Quenza to automatically send information to another application when something happens in your workspace.

This makes it possible to connect Quenza with other tools you use in your practice, such as automation platforms, CRM systems, or email marketing software.

For example, when a new client signs up, Quenza can automatically notify another system so that the client is added to your mailing list, CRM, or another platform you use.

Webhooks are typically set up by someone with technical knowledge, but once configured they run automatically in the background.

What is a webhook?

A webhook is an automatic notification sent from Quenza to another system when a specific event occurs.

Instead of another tool constantly checking Quenza for updates, Quenza sends a message instantly when something happens.

For example, when a new client is created in your workspace, Quenza can automatically send that information to another system.

Examples of how webhooks can be used

Webhooks allow you to automate workflows between Quenza and other tools.

Some examples include:

Add new clients to your mailing list

When a client is created in Quenza, automatically add them to your email platform such as Mailchimp or ConvertKit.

Sync clients to your CRM

Automatically send new client data from Quenza to a CRM system where you manage your contacts.

Trigger automations in Zapier or Make

Send client information to automation platforms like Zapier or Make to trigger workflows such as sending welcome emails, creating tasks, or updating spreadsheets.

Connect Quenza to custom systems

Developers can use webhooks to integrate Quenza with internal systems, custom dashboards, or other software used in your organization.

Creating a webhook

To create a webhook in Quenza:

1. Go to Developer Tools
2. Click Webhooks
3. Click + Webhook

You will see the Add webhook screen where you can configure the webhook.

Configuring the webhook

Fill in the following fields:

Title

Enter a name for your webhook.

This helps you recognize it later.

Example:

Production webhook

URL

Enter the endpoint URL that will receive the webhook data.

This URL is usually provided by the system you want to connect to (for example Zapier, Make, or a custom integration).

Example:

https://example.com/webhooks

The URL must be a valid HTTPS address.

Events

Choose which events should trigger the webhook.

Currently available:

• Client Created

When enabled, Quenza will send a webhook notification whenever a new client is created in your workspace.

Authentication (optional)

If the receiving system requires authentication, you can add HTTP Basic Authentication.

Fields:

• Username
• Password

These credentials will be sent with every webhook request.

Custom Headers (optional)

Some integrations require additional headers such as API keys.

Click Add header and enter:

• Header name
• Header value

These headers will be included in every webhook request.

Status

Toggle Enabled to activate the webhook.

If disabled, the webhook will be saved but no events will be sent.

Saving the webhook

Once all required fields are completed, click Add webhook

The webhook will appear in your list of webhooks and will start sending notifications when the selected events occur.

Webhook limits

By default, you can create up to 3 webhook endpoints per workspace. If you need more, please contact Quenza Support.

Do I need a developer?

In most cases, yes.

Webhooks require a receiving URL that can process the data sent by Quenza. This is typically provided by:

• a developer
• an automation platform like Zapier or Make
• another software integration

If you are unsure how to configure a webhook, we recommend contacting the developer or service provider of the system you want to connect with.