Webhooks & Integrations Overview
Solidarity Tech supports several ways to connect with external services. This guide shows which tool to use for each case and where to set it up.
Overview
There are four main integration paths:
| What you want to do | Tool to use | Plan required |
|---|---|---|
| Push data from other apps into Solidarity Tech (no code) | Zapier Integration | Standard |
| Push data in or pull data out programmatically | REST API | Professional |
| Automatically send supporter data to an external URL when something happens | Automation Webhook Action | Standard |
| Receive ActBlue donations in real time | ActBlue Integration | Standard |
Sending Data Into Solidarity Tech
Zapier (No Code)
The Solidarity Tech Zapier app creates or updates people in your database from other apps. Its only action is Create or Update Person, which can also log donations. The app has no triggers. Go to Settings → Integrations → Zapier and copy Your API Key for Zapier. It is not one of the keys on the API settings page. You need the Manage All Third-Party Integrations permission for the root organization. For setup and the supported fields, see Zapier Integration.
REST API (For Developers)
The REST API at https://api.solidarity.tech/v1/ gives programmatic access to people, events, RSVPs, donations, automations, and more.
- Go to Settings → Integrations → API in the Solidarity Tech dashboard. You need the Manage All Third-Party Integrations permission for the root organization.
- Click New API key, give it a name, and select the organization scope
- Include the key in your requests as
Authorization: Bearer YOUR_API_KEY
API keys can be scoped to sub-organizations to restrict data access. Full API documentation is available at solidarity.tech/reference.
ActBlue (Donation Webhooks)
ActBlue can push donation data into Solidarity Tech in real time. The ActBlue link under Integrations in Settings shows only when your organization's primary country is the US. For the full setup guide, see ActBlue Integration.
Sending Data Out of Solidarity Tech
Automation Webhook Action
The automation webhook action sends supporter data to an external URL when a person reaches that step in an automation. Use it to send data to services such as a Zapier Catch Hook, Google Sheets, CRMs, or Slack. Go to Automations, create or edit an automation, and add a Webhook action step. The step has four fields: URL, Method (GET, POST, or PATCH), Headers, and Body.
Merge tags work in the URL, in custom header values, and in Body field values. When the step runs, each merge tag becomes the person's data. With POST or PATCH, the Body fields go out as one JSON object. A form answer reaches the webhook only when the form saves it to a person field or a custom property. For example tags, see the Webhook action reference and Merge Tags.
Use Add header to send an API key, for example in an Authorization header. Header values are never shown again after you save. Do not put an API key in the URL, which anyone who opens the step can see.
Webhook failures are not currently visible in the dashboard. If you suspect a webhook is not firing, check the receiving service's logs for incoming requests.
Zapier vs. API vs. Automation Webhook
| Zapier | REST API | Automation Webhook | |
|---|---|---|---|
| Direction | Into Solidarity Tech | Both directions | Out of Solidarity Tech |
| Requires coding | No | Yes | No |
| Trigger | External event (in connected app) | Your code calls the API | Automation trigger (form submission, RSVP, tag added, etc.) |
| Data format | Zapier maps fields in their UI | JSON over HTTP | Liquid merge tags in the URL, headers, and JSON body (POST and PATCH) |
| Plan required | Standard | Professional | Standard (requires Automations feature) |
| Use when | You want to push data in from another app without writing code | You need full programmatic access or are building a custom integration | You want to notify an external service when something happens in Solidarity Tech |
Updated 9 days ago