Zapier
Connect Hober to 7,000+ apps. The Zapier app authenticates with a server key (hober_srv_…, from Settings → API Keys → Server keys) and, for the Upsert Subscriber action, your publishable SDK key.
Triggers
| Trigger | Fires when | Payload |
|---|---|---|
| New Subscriber | A net-new subscriber is created (updates don't re-fire) | subscriber id, external id, email, attributes |
| Campaign Finished | A campaign reaches a terminal state | job id, status, delivered/failed/total counts |
Both are instant (REST hooks) — no polling delay.
Actions
| Action | What it does |
|---|---|
| Track Event | Records a behavioral event for a subscriber by external id — feeds segments, journey triggers, and {{ event.* }} personalization |
| Upsert Subscriber | Creates or updates a subscriber (external id, email, attributes) |
Typical zaps
- Typeform submission → Upsert Subscriber + Track Event (
form_submitted) → a Hober journey takes over the follow-up. - Calendly booking → Track Event (
appointment_booked) → WhatsApp/SMS reminder journey. - New Subscriber → add a row to the client's Google Sheet / CRM.
- Campaign Finished → log campaign stats to a reporting sheet.
The REST-hook surface behind the app is public (POST/DELETE /v1/hooks, server-key authenticated) — anything Zapier can do, your own automation can too.