Make + clariBI
Connect Make through clariBI's MCP catalog. Read-only OAuth, and automation run history turned into reliability and operations-usage dashboards.
Native Make connector via the MCP catalog.
Connect with OAuth, keep the access read-only, and ask questions across Make and your other tools in plain English. The setup is the same one-click flow as Google Analytics, Stripe, Meta Ads, or Jira.
What is Make?
Make is a visual automation platform. You build scenarios that connect apps and move data, and Make runs them on triggers or schedules, recording every execution.
clariBI reaches your Make organization through its hosted MCP server: scenarios, run history with success and error outcomes, and operation usage. Reads inherit the connected user's access, and clariBI never runs or edits a scenario.
Learn more at make.com
Connect Make in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source → MCP Servers tab. Find Make in the catalog and click Connect.
Authorize with Make (OAuth)
A Make sign-in opens in your browser. Approve the read access. clariBI uses Dynamic Client Registration, so there is no Make app to set up, and credentials are Fernet-encrypted at rest.
Ask questions, get dashboards
clariBI surfaces run volume, error rates, and operation usage. Ask "Which scenarios failed most this week?" and the AI engine queries Make alongside the systems those automations feed.
What you can analyze
Out of the box with the Make MCP connector:
- Scenario run volume and success rate over time
- Error rate and failure reasons by scenario
- Operation consumption per scenario and per period
- Scenarios that have stopped running or stalled
- Run duration trends for slow scenarios
- Cross-source: a failing scenario → missing rows in the system it feeds
Make is one of 90+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
clariBI discovers Make's tool surface at connection time and exposes the read-only tools to the planner. Write or configuration tools are filtered out by the catalog's read-only heuristic, so the connector stays analytical.
When you connect, clariBI lists the tools your Make MCP server advertises and keeps the read-only ones: reading scenarios, run history, and usage.
Anything that would change Make is excluded at the catalog layer and never reachable through clariBI.
See the live tool list once connected, or read the setup guide →
Cross-source questions Make makes possible
Make data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Make × downstream system
"Did last week's scenario failures cause gaps in our CRM sync?"
Planner: read failed runs for the CRM-sync scenario from Make, then check the CRM for records missing in those windows.
Make × billing
"Which scenarios drive most of our operations bill?"
Planner: read operation counts per scenario from Make and rank them against the plan's included operations.
Make connector FAQ
Do I need to register an app with Make?
No. clariBI uses Dynamic Client Registration (RFC 7591), so Make issues the connection credentials at connect time. You do not manage any keys in clariBI.
Can clariBI run or change my scenarios?
No. The catalog exposes read tools only, and the read-only heuristic filters out anything that writes. clariBI reads scenarios, runs, and usage; it never runs, edits, or stops them.
Which clariBI plan includes the Make connector?
MCP integrations are available on the Trial, Starter, Professional, and Enterprise plans. You can connect Make during the free 14-day trial.
Start your free trial and connect Make in a minute
OAuth in, read-only, dashboards in seconds.
Start free trial