Alync + Make

1. Trigger scenarios from Alync events

1. In Make, add Webhooks → Custom webhook and copy the generated URL.
2. Register it as an Alync channel:

   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": "Make scenario",
       "destination": "https://hook.eu2.make.com/xxxxxxxxxxxx",
       "events": ["lead_promoted", "enrichment_finished"]
     }'

3. Run the scenario once so Make learns the payload structure (send a test batch from Alync, or wait for the first real event).

2. Call the Alync API from Make

Add an HTTP → Make a request module:

URL:      https://api.alync.co/v1/campaigns/{{campaign_id}}/leads
Method:   GET
Headers:  X-API-Key: alync_live_...   (store it in a Make connection/keychain)

Parse the response with a JSON module, iterate leads with an Iterator, and map into your CRM, Sheets, or outreach tool modules.

Verifying deliveries

Make’s webhook module doesn’t verify signatures natively. Either restrict processing to payload shapes you expect and treat the webhook URL as a secret, or front it with a small function (Cloudflare Worker) that checks X-Alync-Signature — scheme in the webhook docs.

Scenario ideas

• lead_promoted → fetch leads → add rows to Google Sheets → notify Slack.
• Schedule module (daily) → POST /v1/campaigns/:id/run-batch → let the webhook branch handle results.
• enrichment_finished → fetch leads with verified emails → create HubSpot contacts.