Connect Zapier to Clarion with push URLs and webhooks

Clarion has no native Zapier app, so you won’t find it in Zapier’s app directory. What it has is a small set of plain HTTP endpoints, and Zapier’s built-in Webhooks by Zapier steps can call them. That covers the two jobs most teams want: getting numbers into the scorecard, and kicking off a zap when something happens in Clarion.

Send a number into a metric

The simplest route is a push URL: a private URL that belongs to one metric and records whatever number you post to it. No API key, no metric name, no headers.

1. In Clarion, open the metric’s Edit Metric dialog and choose Create push URL under Push URL. Copy the URL — it’s shown once.
2. In your zap, after whatever trigger produces the number (a new Stripe charge total, a form count, a row in a spreadsheet), add Webhooks by Zapier → POST.
3. Set the URL to your push URL, the payload type to JSON or form, and add one data field: value, mapped to the number.

That’s all. Each run records the value for the metric’s current period — today, this week or this month, depending on the metric — and replaces any earlier value for that period, so a zap that runs every hour just keeps the number current. Add a date field if a run should record a past period instead.

Values like 1,234 are accepted. Values like $12k are refused rather than guessed at, so check the step’s response if a number doesn’t appear.

Full details: Metric push URLs.

Write a whole scorecard in one step

If one zap produces several numbers, use the ingest API instead. Create an API key with the metrics:write scope, then use Webhooks by Zapier → Custom Request to POST https://api.onclarion.com/v1/companies/{companyId}/metrics/ingest with an x-api-key header and a JSON body listing each metric by name or id. Each entry succeeds or fails on its own, and the response says which. See Ingest metric values with the API.

Start a zap from Clarion

Clarion can POST to any https URL when something happens. Create a zap with the Webhooks by Zapier → Catch Hook trigger, copy its URL, and add it in Clarion under Settings → Integrations → Webhooks, choosing the events you want:

• milestone.completed
• action_item.created and action_item.completed
• challenge.created and challenge.resolved
• metric.ingested

Each delivery carries the event name and a small data object — the item’s id and title, for example — that later steps can use.

Every delivery is signed, but Zapier’s catch hook can’t check an HMAC signature. Keep the catch-hook URL private. If a zap does something sensitive, send the webhook to your own endpoint, verify the signature there, and forward it from there.

Which to choose

Use a push URL when a zap produces one number for one metric. Use the ingest API when it produces several, or when you’d rather keep one credential for many metrics. Use webhooks when Clarion should be the trigger. The developer guide to pushing metrics walks through the trade-offs.