Connect Make (Integromat) to Clarion with push URLs and webhooks

Make (formerly Integromat) doesn’t list Clarion as an app, and Clarion doesn’t ship one. Instead, Make’s general-purpose HTTP module and Webhooks trigger work with Clarion’s API as it is. Most teams use Make for the first job below: moving a number from the system that has it into the weekly scorecard.

Push a value into one metric

Each Clarion metric can have a push URL — a private URL that writes to that metric and nothing else.

1. In Clarion, open the metric’s Edit Metric dialog and choose Create push URL. Copy the URL now; Clarion shows it once.
2. In your scenario, add HTTP → Make a request after the module that produces the number.
3. Set Method to POST and URL to the push URL.
4. Set Body type to Raw with content type JSON, and the request content to:

{ "value": {{1.total}} }

Replace {{1.total}} with the mapped value from your earlier module. A form body with a value field also works.

Schedule the scenario and it records the number for the metric’s current day, week or month, replacing any earlier value for that period. Add "date": "2026-09-01" to write a past period instead, and "notes" to store a short note with the value. Text like "1,234" is accepted; "$12k" is refused with a 400, never coerced.

Details: Metric push URLs.

Update several metrics per run

If a scenario aggregates several numbers — revenue, orders, refunds — send them together. Create an API key with the metrics:write scope, then call POST https://api.onclarion.com/v1/companies/{companyId}/metrics/ingest from the HTTP module with an x-api-key header and an entries array. Each entry names a metric (or gives its metricId) and a value. Entries succeed or fail individually, and the response says which. See Ingest metric values with the API.

Start a scenario from Clarion

1. Create a scenario that starts with Webhooks → Custom webhook and copy its address.
2. In Clarion, open Settings → Integrations → Webhooks, paste the address, choose events, and press Add Webhook.
3. Press Test next to the webhook so Make can learn the payload structure from a webhook.test delivery.

Useful events include milestone.completed (announce a finished milestone), action_item.created, challenge.created and challenge.resolved. Each payload carries event, id, createdAt and a data object.

Clarion signs every delivery, but Make’s custom webhook can’t check an HMAC signature. Treat the webhook address as a secret, and for anything sensitive receive the webhook on your own endpoint, verify the signature, and pass it on.

Finance teams use exactly this pattern to keep cash and revenue lines current — see Automate financial metrics.