Make

Make connects to Evident with its built-in modules. There is no Make app to install.

Trigger: Custom webhook

1. Add a Webhooks → Custom webhook module and copy the URL.
2. In Evident, go to Settings → Webhooks, add it, and subscribe to the events you want.
3. Run the scenario once so Make can learn the payload structure.

Thirteen events cover reviews, orders, gallery submissions and redemptions. See Outbound webhooks.

Verify x-evident-signature — an HMAC-SHA256 of the raw body, hex-encoded, keyed with your webhook secret — before acting on anything. Make’s webhook module can expose headers; compare against a hash computed from the raw body, not from a re-serialized object.

HTTP modules

To read or write, use HTTP → Make a request against https://api.evidentugc.com/api/v1 with:

Authorization: Bearer evnt_YOUR_API_KEY
x-store-env-id: YOUR_STORE_ENV_ID

Make’s Parse JSON module handles responses cleanly, and its iterator works well over the array responses from list endpoints.

MCP

Where Make offers an MCP connection, point it at:

https://mcp.evidentugc.com/mcp

with an Evident API key as the bearer token — twenty-two tools available to an AI module without wiring individual calls.

Where Make is better than the alternatives

Error handlers. Attach one to any module and you get retries, fallback routes and a break directive with its own backoff. Since Evident’s own webhook delivery does not retry, moving the retry burden into Make is a genuine improvement rather than belt-and-braces.

Routers. One webhook subscribed to several events, split by event into branches, is tidier than several near-identical scenarios.

Data stores. Use one to record event_id values you have processed, and deduplicate against it. event_id is stable across attempts; x-evident-webhook-id changes per attempt, so dedupe on the former.

Scenarios worth building

• Review router. One webhook, split by rating: below 3 to Slack and a helpdesk ticket, 4 and above to a content queue if it has photos.
• Unsupported redemption. redemption.created with fulfillment_status: unsupported means the platform could not issue the discount — route it to whoever will.
• Nightly reconciliation. Scheduled scenario pulling Evident’s event log with a cursor, so anything undelivered is still processed. Store the cursor in a data store.
• Weekly digest. Analytics endpoints → formatted email.

Notes

• Rate limits are 10/second, 50/10 seconds, 200/minute per caller. Add a delay module in a loop rather than hammering.
• Use the batch endpoints for bulk writes — up to 250 items per call.
• One API key per scenario set, scoped to what it needs.