ActBlue Default webhooks can send notifications about contributions to a number of different third-party services, as well as your own custom endpoints. For many services, you can and will use the ActBlue Default webhook, but click on the service you’re using from the list below to understand how to set up your specific webhook.

Important Information

The ActBlue Default webhook is designed so anyone can create an integration to receive notifications from ActBlue after three separate events occur: contributions, refunds, or recurring contribution cancellations. You can find the full documentation that describes how the ActBlue Default webhook works here. Our default webhook types use Basic Authentication.

What you’ll need to provide:

• Username
• Password
• A URL to send the notifications to - This needs to be a secure URL that begins with “https://”

Our ActBlue Default webhooks are also used to integrate with the following services:

• ActionKit 2.0
• CallTime
• Zapier
• Numero.ai
• NGP Digital 8
• Trilogy Hub
• and many others not on this list!

Have you built against our ActBlue Default webhook and want to be added to this list? Please email integrations@actbluetech.com.

Select "ActBlue Default" from the dropdown menu as the webhook type.

Important Information

Please check out ActionKit’s documentation before requesting a webhook.

• You will need to contact ActionKit to set up what ActionKit calls a 'stub account' to import the data. ActionKit will then provide you with credentials.
• Refunds and cancellations can use the same username, password, and endpoint you provide for the ActBlue Default webhook for contributions. Follow the same request process as ActBlue Default but select “ActBlue Default Refunds” or “ActBlue Default Cancellations” from the dropdown menu as the webhook type.

What you’ll need to provide:

• Endpoint URL - The URL will look like this: https://[your-actionkit-hostname]/webhooks/actblue/payments/?account=Default%20ActBlue
• Username
• Password - Sometimes known in ActionKit as “secret” or “API secret”

Select "ActBlue Default" from the dropdown menu as the webhook type.

What you’ll need to provide:

• Endpoint URL
• Username
• Password

Select Blue State Digital from the dropdown menu as the webhook type.

Important Information

On the Blue State Digital end of things you will need to, at a minimum, grant the following permissions in order for the data to be received on the BSD side:

• api_contribution
• methods
• add_external_contribution

These permissions are under advanced settings in BSD on the same screen where you find your user_id and api_secret. If these permissions aren't granted your data will not successfully save on the BSD side.

What you’ll need to provide:

• Host Name - This needs to be a URL, but remove the “http://”
• API ID
• API Secret - This should appear on the same screen as the api_id, and contains several numbers and letters.

Select "ActBlue Default" from the dropdown menu as the webhook type.

Important information

Need CallTime to fill this out? Please check out the Vendor form here.

What you’ll need to provide:

• Endpoint URL - the URL typically starts with: https://sls.calltime.ai/actblue-webhook
• Username
• Password

Select "ActBlue Default" from the dropdown menu as the webhook type.

Important Information

This is not an API for the compliance software of NGP. It does offer a limited integration with Digital 8's CRM. We highly recommend you send the Vendor Form found here to your NGP representative, along with your entity ID. You can find NGP Digital 8’s documentation here for more information.

What you’ll need to provide:

• Endpoint URL, username, and password: NGP will provide these for you.

Select "ActBlue Default" from the dropdown menu as the webhook type.

Important Information

We recommend you send the Vendor form found here to your Numero.ai Administrator.

What you’ll need to provide

• Endpoint URL
• Username
• Password

If you are a Salesforce user, please contact support@actblue.com for instructions on how to set up your webhook.

Important information

We strongly recommend you create a separate Salsa login to specifically use for webhooks. When using your personal Salsa login for your webhook, anytime you change your account’s password, you will need to update the webhook credentials as well.

What you’ll need to provide:

• Host Name - This is the URL you will see after signing into your Salsa account. We only need the first part of the URL, please do not include anything after “.org”
• Username - This will be the email address you use to log into Salsa. We strongly recommend you create a separate Salsa login to use for webhooks.
• Password
• Salsa Organization Number - This appears inside your Salsa instance. If you are unable to find it, please contact Salsa.

Our list of webhook types covers some common services that integrate with ActBlue webhooks. Don’t see the service you’re using? We recommend you reach out to support@actblue.com with any questions! You can also send your vendor our Vendor Form to request a webhook.

Have you built against our ActBlue Default webhook and want to be added to this list? Please email integrations@actbluetech.com.

If you're looking to use webhooks to send data to your own endpoint for a custom integration, select the ActBlue Default webhook type.