Connect n8n to Clarion — push metrics and react to events

There is no Clarion community node for n8n. You don’t need one: n8n’s HTTP Request and Webhook nodes cover everything Clarion’s API does, and they give you more control than a packaged node would — including the ability to verify webhook signatures.

Push a number into a metric

A push URL is a private URL tied to one metric. Posting a number to it records that number.

1. In Clarion, open the metric’s Edit Metric dialog and choose Create push URL. Copy the URL; it’s shown only once.
2. In n8n, add an HTTP Request node after the node that produces your number.
3. Set Method to POST and URL to the push URL.
4. Turn on Send Body, choose JSON, and add a field named value with an expression for the number, such as {{ $json.total }}.

Put it on a Schedule Trigger and you have a scorecard line that keeps itself up to date. Re-running in the same period replaces the value rather than adding a duplicate, and a date field records a past period instead. The node’s output shows what was stored:

{ "metric": "Weekly Revenue", "value": 1234, "period": "2026-09-28" }

More in Metric push URLs.

Write several metrics at once

When one workflow computes a whole scorecard, use the ingest endpoint with an API key that has the metrics:write scope. In the HTTP Request node:

• URL: https://api.onclarion.com/v1/companies/YOUR_COMPANY_ID/metrics/ingest
• Header: x-api-key set to the key (store it as an n8n credential, not in the node)
• Body (JSON): an entries array, each with metric (name) or metricId, and value

The response lists every entry with a status of ok, unknown_metric, ambiguous_metric or invalid_value, so an IF node can alert you when a name stops matching. See Ingest metric values with the API.

Read data out of Clarion

The same API serves read-only lists of metrics, milestones and action items to a key with the matching read scope. That’s useful for a weekly digest workflow that posts open action items to chat. See Read data with the API.

Run a workflow when Clarion changes

1. Add a Webhook node, set the method to POST, and copy its production URL.
2. In Clarion, go to Settings → Integrations → Webhooks, paste the URL, tick the events you want, and press Add Webhook. Copy the signing secret it shows.
3. Press Test in Clarion to send a webhook.test event and confirm the workflow fires.

Events include milestone.completed, action_item.created, action_item.completed, challenge.created, challenge.resolved and metric.ingested.

Clarion signs each request with an X-Clarion-Signature-V2 header. To check it in n8n, enable the Webhook node’s raw body option and recompute the HMAC in a Code node — this needs Node’s crypto module, which some n8n installations have to allow explicitly. Verify webhook signatures has the exact algorithm. If you can’t verify, at least keep the webhook URL private and deduplicate on the X-Clarion-Delivery header, because a retry reuses it.

For the bigger picture, read React to changes with webhooks.