Make runs visual automations that move data between apps on a schedule or trigger. Connecting Make to clariBI turns the run history of those automations into something you can measure: how often scenarios run, how often they fail, and how many operations they burn.
Why connect Make
Automation health lives inside Make, so a quietly failing scenario or a runaway operations bill is easy to miss until something downstream breaks.
With Make connected, you can ask "Which scenarios failed most this week?", "How many operations did we consume per scenario this month?", or "Which automations have not run since the last app update?" and the AI engine reads it live.
How the connection works
clariBI talks to Make through its hosted MCP server at https://mcp.make.com. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Make
U->>C: Click Authorize with Make
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Make tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Make cannot modify data on the vendor side.
The exact tool inventory depends on the Make features your account has access to. After connecting, try a few natural-language questions to see what Make data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Make, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Make
U->>C: Ask a question about automation run and usage data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Make card.
- Click Authorize with Make.
- Sign in to Make in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI connects through Make's OAuth flow and inherits the connected user's organization and team access. The catalog exposes read tools only (reading scenarios, run history, and usage); clariBI never runs, edits, or stops a scenario. Disconnect anytime from Settings → Integrations in clariBI.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "No scenarios returned" | The connected user is scoped to a different Make organization or team. | Confirm the organization and team in Make and that your user can see the scenarios. |
| "Operation counts look low" | Make reports usage per billing period; an early-in-cycle window shows little. | Widen the window to a full billing period for a representative figure. |