Alync + Zapier
Until the native Alync app lands in the Zapier directory, Webhooks by Zapier (available on paid Zapier plans) covers both directions.
1. Trigger Zaps from Alync events
- Create a Zap with trigger Webhooks by Zapier → Catch Hook and copy the hook URL.
- Register it with Alync:
curl -X POST https://api.alync.co/v1/notifications/channels \ -H "X-API-Key: $ALYNC_KEY" -H "Content-Type: application/json" \ -d '{ "type": "webhook", "name": "Zapier", "destination": "https://hooks.zapier.com/hooks/catch/123456/abcdef/", "events": ["lead_promoted"] }' - Run an Alync sourcing batch (or wait for auto-run) so Zapier catches a sample payload, then map fields in the next steps.
2. Pull full lead details into the Zap
Add an action Webhooks by Zapier → GET:
URL: https://api.alync.co/v1/campaigns/{{campaign_id}}/leads
Headers: X-API-Key | alync_live_...Then continue into any app — create CRM contacts, Sheets rows, Slack messages, or outreach sequences.
3. Drive Alync from other apps
Use Webhooks by Zapier → POST as an action, e.g. create a campaign whenever a Typeform lands:
URL: https://api.alync.co/v1/campaigns
Payload: {"name": "{{answer_company}}", "offering": "{{answer_offering}}"}
Headers: X-API-Key | alync_live_...
Content-Type | application/jsonNotes
- Zapier catch hooks can’t verify HMAC signatures natively — treat the hook URL as a secret, or add a Code step that validates
X-Alync-Signature(scheme in the webhook docs). - Sourcing/enrich endpoints answer
202immediately; results arrive via the trigger events, so structure Zaps around events rather than waiting. - A native Zapier app with polished triggers is on the roadmap — these hooks will keep working after it ships.
Last updated July 10, 2026 · Alync (alync.co)