Skip to main content
Webhooks let you subscribe to events happening in a software system and automatically receive a delivery of data to your server whenever those events occur. Webhooks are used to receive data as it happens, as opposed to polling an API (calling an API intermittently) to see if data is available. With webhooks, you only need to express interest in an event once when creating the webhook. Webhooks are used in a wide range of scenarios, including:
  • Send an invoice when a deal is closed (e.g. by connecting with Stripe, Xero or QuickBooks)
  • Send a contract signature request when a deal is closed (e.g. by connecting with PandaDoc)
  • Add new contacts to a newsletter (e.g. by connecting with Mailchimp or Beehiiv)
  • Create a new project to manage client onboarding when a deal is won (e.g. by connecting with Asana or Monday)
  • Synchronize data with an external system of record (e.g your own app)

About webhooks on folk

When you create a webhook, you specify a URL and subscribe to events that occur on folk. When an event that your webhook is subscribed to occurs, folk will send an HTTP request with data about the event to the URL that you specified. If your server is set up to listen for webhook deliveries at that URL, it can take action when it receives one. For example, you could subscribe your webhook to events that occur when a person’s pipeline status is updated. Your server could respond by sending an email or calling APIs on another platform. folk’s webhook system adheres to the standard webhooks specification: if you are already familiar with the standard and worked with other systems implementing it, it’s going to be easy to get started. For more information about creating webhooks, see Creating webhooks. For more information about the types of events you can subscribe to, see Events and payloads. For more information about configuring your server to take an action in response to a payload delivery, see Handling webhook deliveries.
I