Integration

Webhooks

About Webhooks

By enabling webhooks, you can configure Fienta to send data to third-party systems whenever one of the following events occurs:

  • When someone buys a ticket or registers for a free event.

  • When registration form data is submitted or updated after the initial purchase.

  • When a ticket is validated and marked as used using our mobile app, web interface, or API.

What can webhooks do for you?

For example, you can use automation platforms such as Make.com to create workflows that run after each ticket purchase. These workflows can:

  • Add the buyer to the list of meeting attendees in Zoom.

  • Add the purchase as a new row in a Google spreadsheet.

  • Send you a notification in Skype, Slack, or Facebook Messenger.

  • If the buyer subscribed to a newsletter, add them to your list in Mailchimp or Smaily.

After validating a ticket, you might want to:

  • Send your visitor a follow-up email with a feedback form, a few days after their visit.

  • Use Google Cloud Print to print a name tag or show a personal welcome message during conference check-in.

How to turn it on

You will find webhooks under Settings > Integration when logged in to Fienta.

How to test webhooks

Fienta provides dedicated test buttons to help you verify that your webhooks work correctly. The buttons become visible after you enable a webhook on the Settings → Integration page.

On the event’s Advanced settings page, you can send webhooks for the entire event. This is useful when you want to test the data connection or send all existing event data through the webhooks.

On an individual purchase page, you can send webhooks for that specific purchase. This is helpful when you want to check the data of a particular purchase and confirm that the webhook reaches the correct destination with the correct payload.

After clicking the test button, Fienta displays the webhook URL, the number of records added to the queue, and a sample payload. This allows you to quickly verify that the integration behaves as expected before using it in production.

You can also use a temporary test endpoint that receives the request and shows its contents. Services such as Webhook.site and Beeceptor work well for this purpose. Create a test URL there, enter it as the webhook address in Fienta, and run the test using the corresponding button. This lets you immediately see what payload is sent to the external system.

Documentation

Visit our API documentation for a description and sample data posted by the webhooks.