Integration · Data, exports and APIs
Sociana + Webhooks
Sociana webhooks send an event, such as a scan or a submission, to a URL the client controls. That is how a lead captured at a stall reaches a CRM without a native connector. Webhooks are set up with the Sociana team; Sociana does not publish a public API, a Zapier app or native CRM sync.
Live
What it does inside Sociana
A webhook is a message from Sociana to your own endpoint when something happens. Typical events: a participant registers, a stall scan is logged, a submission is approved. The receiver can be a small script, an iPaaS tool you already run, or your CRM's inbound endpoint. This is the honest answer to HubSpot, Salesforce and Zoho questions today: export to any CRM via Sheets or webhooks, with no native sync.
What the organiser configures
- Which events trigger a webhook
- The destination URL and any authentication header
- Fields included in the payload
- Retry expectations agreed with the team
- Which occasions or groups are in scope
Data that flows, and where it is stored
| Data | From | To | Stored |
|---|---|---|---|
| Event payload (for example visitor name, stall, time, notes) | Sociana | Your HTTPS endpoint | Your system; Sociana keeps the originating record |
| Acknowledgement or error response | Your endpoint | Sociana | Retry and failure handling agreed at set-up; log retention on request |
Data protection (DPDP)
The organiser is the Data Fiduciary and Sociana acts as processor. Ask us for the hosting region and retention period that apply to your occasion; the sub-processor list is on the Sub-processors and integrations page. We do not state a region or retention period on this page.
Security notes
- Payloads carry personal data; use HTTPS and an authenticated endpoint.
- The receiving system is outside Sociana's control.
- Ask us about signing and secret rotation.
Set-up checklist
- Build or choose an HTTPS endpoint that can accept a POST and return quickly.
- List the events and fields you need and share them with the Sociana team.
- Agree an authentication header or signed secret.
- Run test events and confirm your system handles duplicates.
- Monitor the first live scans and agree who is called on a failure.
Limits, stated plainly
- There is no public, versioned API.
- No Zapier or Make app; use your own receiver.
- No native HubSpot, Salesforce or Zoho sync.
- Delivery guarantees and retry rules are agreed per occasion.
Not offered yet
- Public API
- Zapier or Make app
- Native CRM sync
At a glance
- Provider
- Webhooks
- Status
- Live
- Set up by
- The Sociana delivery team, with your accounts
Questions people ask
Can we push leads into Salesforce or HubSpot?
Yes through a webhook or Sheets export that you connect to your CRM. There is no native Salesforce or HubSpot sync, so a small amount of integration work sits on your side.
Is there a public API?
No. Webhooks and Sheets are the supported routes, set up with the delivery team.
Do webhooks retry?
Retry behaviour is agreed per occasion rather than published as a guarantee. Ask for the agreed rule in writing before event day.
Need this connected for your event?
Tell us which tools your team already uses. We will show you where the data lands and who sees it.