Zapier Coming soon

A native Lojiq app on Zapier is in progress. You do not have to wait for it: the public API and webhooks already work with Webhooks by Zapier, which is how the native app will work underneath anyway.

What the native app will offer#

Connecting will mean pasting an API key with the scopes those triggers and actions need. Nothing in the native app will do anything you cannot already do with the recipe below.

Works today: Webhooks by Zapier#

Trigger a Zap from a Lojiq event#

1. Create a Zap with the trigger Webhooks by Zapier → Catch Hook#

   Copy the hook URL Zapier shows you (https://hooks.zapier.com/hooks/catch/…).

2. Subscribe that URL in Lojiq#

   bashCopy

   curl -s -X POST "https://api.lojiq.ai/v1/webhooks" \
     -H "Authorization: Bearer $LOJIQ_KEY" -H "Content-Type: application/json" \
     -d '{"name":"zapier-new-leads","target_url":"https://hooks.zapier.com/hooks/catch/123456/abcdef/",
          "event_types":["lead.created","call.transcript_ready","appointment.booked"]}'
   

3. Send a test event#

   Create a lead (POST /leads with a new number) and click Test trigger in Zapier. The sample arrives as { id, type, organization_id, occurred_at, data }; map data.lead_id and friends into the following steps.

Zapier catch hooks answer 200 instantly, so retries and the 10-second rule are never a concern. Zapier cannot verify the HMAC signature; if that matters to you, put a small verifying proxy in front, or accept that the hook URL itself is the secret (keep it private).

Push a lead into Lojiq from any app#

1. Add the action Webhooks by Zapier → Custom Request#

2. Configure it#

   Method	POST
   URL	https://api.lojiq.ai/v1/leads
   Headers	Authorization: Bearer lojiq_live_… Content-Type: application/json
   Data	{"phone_number":"{{Phone}}","first_name":"{{First}}","last_name":"{{Last}}","email_address":"{{Email}}","consent_source":"{{Form name}}","consented_at":"{{Submitted at}}","campaign_id":"0d2f…"}

   Make sure the phone field is E.164 before it reaches Lojiq (a Formatter → Numbers → Format Phone Number step with E.164 output does it). Re-running the Zap never creates a duplicate.

Make, n8n, Pipedream#

Exactly the same two patterns: an inbound-webhook trigger node subscribed via POST /webhooks, and an HTTP-request node calling POST /leads. n8n and Pipedream can also run the signature check from the Webhooks guide in a code step.