Alync + n8n
Two building blocks: an n8n Webhook node that receives Alync events, and HTTP Request nodes that call the Alync API. No custom node required.
1. Trigger a workflow when leads are promoted
- In n8n, add a Webhook node (method POST) and copy its production 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": "n8n leads workflow", "destination": "https://your-n8n.example.com/webhook/abc123", "events": ["lead_promoted"] }' - Save the returned
signing_secretas an n8n credential and verify theX-Alync-Signatureheader in a Code node (see webhook docs for the snippet) before trusting the payload.
2. Fetch the full lead objects
The lead_promoted payload carries campaign_id and lead_ids. Add an HTTP Request node:
Method: GET
URL: https://api.alync.co/v1/campaigns/{{ $json.campaign_id }}/leads
Header: X-API-Key = {{ $credentials.alyncApiKey }}Then filter to lead_ids and fan out — push to your CRM, a Google Sheet, Slack, or an outreach tool.
3. Drive Alync from n8n
Any endpoint works from an HTTP Request node. Common ones:
POST /v1/campaigns— create a campaign from a form submission.POST /v1/campaigns/:id/run-batch— run sourcing on a schedule (n8n Cron node) instead of Alync auto-run.POST /v1/campaigns/:id/enrich— enrich after each promotion event.
Recommended pattern
Webhook → verify signature → fetch leads → enrich → wait for enrichment_finished → sync to CRM. Use two workflows joined by the two events rather than polling — it’s free and instant.
Last updated July 10, 2026 · Alync (alync.co)