Webhooks

Peoplevine Webhooks are a powerful tool to sync data to existing systems to keep their information up to date. The Webhook engine automatically pushes data to external systems as you enter it into the Peoplevine database using a standard API endpoint.

There are over 100 Peoplevine Webhooks that trigger from any component in the system, making webhooks very versatile, allowing you to create automated workflows for a myriad of tasks.

Common Webhook tasks:

  • Surveys - Conduct surveys to poll your members, gain important feedback, decide development direction, fill in missing member information, gain insight into member's interest, etc.

  • Memberships - Allow visitors sign up for, upgrade, and pay for memberships, syncing the data to your system, keeping you updated on their profile.

  • Reservations - Sync reservation data across multiple systems to make sure that inventory and availability are accurate to provide your members with a seamless experience.

  • Customers - Sync customers and their data across systems, providing up-to-date information at all touchpoints.

  • Chaining tasks - Chain different tasks together to make a workflow for complex tasks. One example of this is a new customer sign-up. You can have them purchase a membership, fill out their profile, fill out a survey about if they would like to make their first reservation now, and make a reservation after a positive response.

Webhooks can use any of the following API endpoint parameters:

  • Request Methods: POST, PUT, PATCH, GET, or DELETE

  • Auth Credentials: Include an existing authentication refer to the object by using HAPI variables such as: {@access_token@}

  • Header Objects: You can add authentication fields to the Authorization Header

  • Body: The body can be auto-generated as JSON or CSV, or you can include your own customized body by using HAPI variables

  • Content Type: Modify the content type to make sure your data inputs correctly

Example JSON payload

{
   "drink_preference": "{@field_1234_56789@}", 
   "age": "{@field_56789_1234@}"
}

Last updated