ActBlue

Connect ActBlue donations directly to your Solidarity Tech account. When a donation is made through ActBlue, it will automatically sync to your Solidarity Tech system in real-time, creating or updating contact records and logging donations.

What Gets Synced

When someone makes a donation through ActBlue, the following information is automatically synced to Solidarity Tech:

Contact Information

• First name and last name
• Email address
• Phone number
• Full mailing address (street, city, state, zip, country)
• Employer and occupation (stored as custom properties)

Donation Details

• Donation amount
• ActBlue order number (external donation ID)
• Payment date
• Full webhook payload (stored for reference)
• Marked as external donation with source "ActBlue"

Setup Instructions

1. Access ActBlue Settings

Navigate to Settings → Zapier in your Solidarity Tech dashboard. You'll see a notice about the ActBlue integration. Click the link to access the ActBlue settings page.

Alternatively, you can access it directly at /settings/actblue in your dashboard.

2. Copy Your Credentials

Your ActBlue webhook credentials are automatically generated when you first visit the settings page:

• Webhook URL: A unique URL for your organization (format: https://www.solidarity.tech/webhooks/actblue/your-org-slug-id)
• Username: Based on your organization name and ID
• Password: A 24-character randomly generated password

Use the Copy buttons next to each field to copy the credentials to your clipboard.

3. Request Webhook in ActBlue

1. Log in to your ActBlue dashboard
2. Navigate to Integrations → Webhooks → Request a Webhook
3. Select webhook type: ActBlue Default (for contributions)
4. Paste the Webhook URL, Username, and Password from Solidarity Tech
5. Submit your webhook request

📘

Note: ActBlue manually reviews all webhook requests. It may take 1-2 business days for your webhook to be approved.

4. Set Up Refund Webhook (Optional)

To receive refund notifications, repeat the process:

1. Request another webhook in ActBlue
2. Select webhook type: ActBlue Default Refunds
3. Use the same Webhook URL, Username, and Password
4. Submit for approval

Supported Webhook Types

The ActBlue integration supports the following webhook types:

• ActBlue Default: Contribution webhooks (donations)
• ActBlue Default Refunds: Refund notifications

ℹ️

Note: ActBlue Default Cancellations are not currently supported.

How It Works

New Contacts

When ActBlue sends a webhook for a donation from someone not in your database:

1. A new contact is created with all available information
2. The contact's signup source is marked as "ActBlue"
3. An external donation charge is created and linked to the contact
4. The donation appears in your Finances section as an external donation

Existing Contacts

When a donation comes from someone already in your database (matched by email or phone):

1. The contact's information is updated with any new data from ActBlue
2. A new external donation charge is added to their record
3. Their employer/occupation custom properties are updated if provided

Data Deduplication

The system automatically prevents duplicate donations by checking:

• External donation ID (ActBlue order number)
• Donation amount
• Donation date

If a matching donation already exists, it will be skipped rather than creating a duplicate.

Managing External Donations

External donations from ActBlue can be viewed in Finances → Payments. They are marked with an "External" badge.

Viewing Donation Details

Each external donation record shows:

• Donation amount and date
• Donor information
• ActBlue order number (external ID)
• Source (ActBlue)
• Link to the donor's contact record

Deleting External Donations

If you need to remove an external donation (e.g., due to a data import error):

1. Navigate to the donation record in Finances → Payments
2. Click the Delete button
3. Confirm the deletion in the modal dialog

⚠️

Warning: Deleting a donation is permanent and cannot be undone. The associated activity will also be removed from the contact's timeline.

Regenerating Credentials

If you need to regenerate your webhook password:

1. Go to Settings → Zapier and click the ActBlue integration link
2. Click the Regenerate button next to the password field
3. Confirm the action
4. Copy the new password immediately
5. Update the password in your ActBlue dashboard webhooks

⚠️

Warning: Regenerating the password will immediately invalidate your existing webhook. Update ActBlue as soon as possible to avoid missing donations.

Webhook Security

Your ActBlue webhook is secured through HTTP Basic Authentication:

• ActBlue sends the username and password with each webhook request
• Solidarity Tech validates the credentials before processing the webhook
• Invalid credentials result in a 401 Unauthorized response
• Each organization has unique credentials
• 
  

Troubleshooting

Webhook Not Receiving Donations

1. Check ActBlue approval status: Verify your webhook was approved in the ActBlue dashboard
2. Verify credentials: Ensure the username and password in ActBlue match your Solidarity Tech settings
3. Check webhook URL: Confirm you're using the correct webhook URL from Solidarity Tech
4. Test with ActBlue: Some ActBlue webhook configurations allow test webhooks

Duplicate Donations

If you're seeing duplicate donations:

1. Check if you have multiple webhooks configured in ActBlue pointing to the same Solidarity Tech account
2. Review the external donation IDs to identify the source
3. Delete duplicate donations manually from the Finances section

Missing Donor Information

ActBlue sends whatever information donors provide. If fields are missing:

• The donation will still be recorded with available information
• You can manually update contact information in Solidarity Tech
• Employer and occupation are optional fields and may not always be present

Contact Not Being Created

If donations are coming through but contacts aren't being created:

1. Verify the contact doesn't already exist with a different email/phone
2. Check that the chapter assignment settings are configured
3. Review the logs for any validation errors