n8n

n8n can reach Evident three ways, and a useful workflow often uses two of them.

MCP

Point n8n’s MCP client node at:

https://mcp.evidentugc.com/mcp

Authenticate with an Evident API key as the bearer token. This gives an n8n AI agent node all twenty-two Evident tools without you wiring individual HTTP calls.

REST API

For deterministic workflows, the HTTP Request node against https://api.evidentugc.com/api/v1 is simpler and easier to debug than an agent.

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

Both headers are required. See Using the API.

Webhooks in

The best trigger. Register an n8n webhook URL under Settings → Webhooks in Evident and subscribe to the events you want.

Verify the signature in your workflow before acting: x-evident-signature is an HMAC-SHA256 of the raw body, hex-encoded, keyed with your webhook secret. See Outbound webhooks.

Workflows worth building

Negative review to Slack. Subscribe to review.created, filter to rating ≤ 2, post to a channel with the product name and a link. This is the highest-value automation most stores build, it takes ten minutes, and it needs no AI at all.

One-star review to a helpdesk ticket. Same trigger, into Zendesk, Freshdesk or Linear. A meaningful share of one-star reviews are support tickets in the wrong place.

Unsupported redemption alert. redemption.created carries a fulfillment_status. When it arrives as unsupported, the platform could not issue the discount and a human must. Route those somewhere visible.

Weekly digest. Schedule trigger → review analytics → format → email or Slack. Rating movement, new review count, moderation backlog.

Photo review to a content queue. review.created with images → copy to a content review board, so your social team sees UGC as it lands.

Reply drafting. Schedule → search unanswered negative reviews → AI agent drafts → post drafts to Slack for approval. Draft, do not auto-post.

Reliability

Webhook delivery from Evident is fire-and-forget with a 15-second timeout and no automatic retry. So:

• Return 200 immediately and do the work on a second branch.
• Deduplicate on event_id, which is stable across attempts.
• Reconcile on a schedule against the event log, which replays events reconstructed from the underlying rows — including ones that were never delivered.

A nightly reconciliation workflow removes an entire class of silent gaps.

Notes

• One API key per workflow set, scoped to what it needs. read alone covers most reporting.
• Rate limits are 10/second, 50/10 seconds, 200/minute per caller. Use the batch endpoints rather than looping.
• Self-hosted and cloud n8n both work; there is nothing to install on the Evident side.