Webhooks can be used by software engineers to integrate ControlShift with third-party systems. They allow engineers to build software that is triggered by events that take place within ControlShift and automatically send ControlShift data to external systems when certain actions are taken. This can include things like: automatically sending data to a CRM when a new event RSVP is created, updating your mailing tool when an unsubscribe request is submitted, or notifying a task board when a petition is edited and in need of moderation.
Within the platform, most actions taken by supporters have a corresponding webhook. You can view a full list of available webhooks and the data included in their payloads on our developer site.
To begin using these webhooks, go to the admin homepage > Settings > Integrations > Webhooks > Add (or Manage).
From here you can configure a new webhook endpoint. Please note: each Webhook Endpoint URL receives the full payload of webhooks that occur within ControlShift.
We recommend using a tool like Pipedream to help debug and develop your webhook integration. Pipedream allows engineers to see all of the webhooks generated by the application and sent to an endpoint.
ControlShift also supports bulk data webhooks that are designed to help you keep an external reporting or analytics database server up-to-date with information from ControlShift's internal tables. You can learn more about these bulk data options on our developer site.
This service was built in a database agnostic way, but it is possible to build a ControlShift > Amazon Redshift data pipeline using the ControlShift to Redshift Pipeline technique described on our developer site.