Zapier

Connect Evident to 6,000+ apps using webhooks and the REST API — no Zapier app required.

On this page

There is no published Evident app in the Zapier directory yet. You do not need one — Zapier’s built-in Webhooks by Zapier and Code by Zapier cover everything, and have done since day one.

Trigger: Catch Hook

  1. In Zapier, create a Zap with Webhooks by Zapier → Catch Raw Hook as the trigger. Use Raw, not the parsed version — you need the exact bytes to verify the signature.
  2. Copy the URL Zapier gives you.
  3. In Evident, register it as an outbound webhook and subscribe to the events you want. Webhooks are registered through the API today — see Outbound webhooks for the one request it takes.

Twelve events are available across reviews, orders, gallery submissions and redemptions. See Outbound webhooks.

Verify the signature

Add a Code by Zapier step immediately after the trigger:

const crypto = require('crypto');

const expected = crypto
  .createHmac('sha256', inputData.secret)
  .update(inputData.rawBody)
  .digest('hex');

if (expected !== inputData.signature) {
  throw new Error('Bad signature');
}

output = [JSON.parse(inputData.rawBody)];

Pass the raw body, the x-evident-signature header and your webhook secret in as input fields. The endpoint is public by necessity, and the signature is the only thing separating a real event from someone who guessed the URL.

Action: Webhooks by Zapier

To write back to Evident, use Webhooks by Zapier → Custom Request against https://api.evidentugc.com/api/v1, with headers:

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

Both are required on every call. See Using the API.

MCP

Where Zapier offers MCP server connections, point one at:

https://mcp.evidentugc.com/mcp

with an Evident API key as the bearer token. That gives an AI step all twenty-two Evident tools at once instead of individual HTTP actions.

Zaps worth building

  • Review below 3 stars → Slack. Ten minutes to build, and the single most useful thing most stores automate.
  • One-star review → helpdesk ticket. Many are support issues in the wrong place.
  • New photo review → content board. So your social team sees UGC as it arrives.
  • redemption.created with fulfillment_status: unsupported → alert. The platform could not issue the discount; a human must.
  • Weekly schedule → review analytics → email digest.

Reliability

Evident’s webhook delivery is fire-and-forget with a 15-second timeout and no automatic retry. Zapier’s Catch Hook responds fast on its own, which suits this well.

Deduplicate on event_id — it is stable across attempts, unlike x-evident-webhook-id, which is per HTTP attempt.

For anything you cannot afford to miss, add a scheduled Zap that reconciles against Evident’s event log rather than relying on delivery alone.

Something missing or out of date? Email support@evidentugc.com — docs corrections go straight to the team that builds the feature.