Make

Make (formerly Integromat) connects AdvocateLoop to your other apps. There’s no dedicated AdvocateLoop module yet, but Make’s built-in HTTP and webhook modules cover both directions.

You’ll need your API Key and Brand ID from Settings → API Keys — see Find your API Key & Brand ID.

Send events into AdvocateLoop

Use the HTTP module to record an event (a conversion, refund, or claim) from a Make scenario.

1. Add an HTTP → Make a request module after your trigger.
2. Configure it:
   • URL: https://api.advocateloop.com/api/v1/track/conversion (or /track/refund, /track/claim)
   • Method: POST
   • Headers: Content-Type: application/json, X-API-Key: <your key>, X-Brand-ID: <your brand ID>
   • Body type: Raw → JSON
   • Request content: your JSON body, mapping Make variables into the fields
3. Run once to test — a successful call returns success: true.

For the full list of events and their fields, see the REST API.

Start a scenario from an AdvocateLoop event

To run a Make scenario when something happens in AdvocateLoop (a conversion, claim, or refund), use a webhook:

1. In Make, add a Webhooks → Custom webhook trigger and copy the URL it generates.
2. In AdvocateLoop, add an outbound webhook pointing at that URL — see Webhooks.
3. Trigger a test event; Make captures the payload so you can map its fields into the rest of your scenario.

Example scenarios

• New conversion → Google Sheets — append a row for reporting.
• New refund → CRM — update the customer’s record.
• Order paid in another system → AdvocateLoop — an HTTP module records the conversion.

Related

• Zapier — the same idea, using Zapier
• REST API — the events and their fields
• Webhooks — receive events from AdvocateLoop