Integrations
Automation integrations
The universal escape hatch — webhook, Zapier, CSV.
No integration marketplace covers every tool a campaign runs, and any vendor who claims otherwise is describing a roadmap, not a product. This category is how Ballot Signal reaches everything else: a signed universal webhook, a Zapier app, generic automation platforms, and a plain CSV export you own outright.
CSV export
The exit door. A vendor who makes export hard is telling you something about the relationship — we make it a button.
Slack
Puts a warm supporter in front of a human in seconds — the difference between a record and a phone call.
Universal webhook
The honest answer to 'do you integrate with X?' when X is not on this list — and the reason our coverage claim does not depend on a marketplace review queue.
Zapier
The fastest route to broad coverage: one app, thousands of destinations, without waiting on every vendor's roadmap.
Make
Visual automation with far more logic per scenario than Zapier — useful when routing rules get complicated.
n8n
Self-hostable, so supporter records never leave infrastructure you control — the answer for the most privacy-conservative organizations.
Common field mapping
Supporter record → JSON payload (HMAC-signed) or flat CSV row, with every consent field included by default so the receiving system inherits the evidence.
See the full supporter record →Other categories
CRM & voter contact
Your campaign's system of record — where every supporter eventually lands.
Fundraising & payments
Match giving history to the visitor who never filled out the form.
Email & SMS
The channels that live or die on a defensible consent record.
Website builders & CMS
Where the tag goes. One snippet, or a native plugin.
Consent & privacy
Signals we consume, never signals we override.
Voter data
Honest about what we do not have yet.
Ads & analytics
Server-side conversion signal — for consented supporters only.
Automation: questions
How is the webhook secured?
Every POST carries an HMAC-SHA256 signature over the raw request body in a signature header, plus a timestamp header to defeat replay. Verify both before you trust a payload. Sample verification code for Node, Python, and PHP is in the docs.
What happens if our endpoint goes down?
We retry with exponential backoff and surface failures in the dashboard. Nothing is silently dropped; a delivery that exhausts its retries stays queryable and re-sendable.
Can we just export everything and leave?
Yes. CSV export is available on every plan, includes the full consent record, and is not gated behind a support ticket. Your supporter data is yours.
See what your own website already knows.
Book a 20-minute walkthrough. We will look at your site's current consent posture first — that part is useful whether or not you buy anything.