Webhooks are a way for Gradual to send real-time data to another system when a specific event occurs.
How Webhooks Work:
Event Triggered: Something happens in Gradual (e.g., a new user signs up or user registers for an event).
Webhook Fires: The system automatically sends an HTTP POST request with data to a pre-defined external URL.
Receiver Handles It: The receiving server (your app or service) processes the incoming data and takes action (e.g., update a database, send an email).
Example Case Uses:
User checks into an event → Add a new record to Airtable
User leaves a space → Send a notification to Slack (e.g., alert the ops team)
Gradual also supports a waitlist join webhook event. When a user joins a waitlist, the webhook sends type: userJoinedWaitlist and dateOfJoin.
Gradual also supports a community application submitted webhook event. This webhook is triggered when someone successfully submits a community membership application, allowing you to start a review workflow before approving the applicant.
The payload sends type: communityApplicationSubmitted and includes dateOfApplication, the applicant’s userEmail, and applicationQuestions, which contains each application question and the applicant’s response. Answers to single-choice and open-ended questions are returned as text, while answers to multiple-choice questions are returned as a list of the selected options.
When a new forum post is created, the webhook payload includes forumPostBody, which contains the full text of the forum post. If the post body is empty, forumPostBody will return as an empty string.
All supported webhook events and their payload fields are found here.