← Blog
make integromat automation June 11, 2026 5 min read

How to Track AI API Costs in Make (Integromat) Scenarios

Analytics dashboard with charts representing Make automation cost tracking

TL;DR: Make's HTTP module lets you call any URL. Replace your OpenAI endpoint with https://tokonomics.ca/proxy/openai/chat/completions and your API key with a Tokonomics key. Every AI call gets tracked — cost per scenario, per model, per day. Setup takes 3 minutes.


Why Make Users Need Cost Tracking

Make (formerly Integromat) is one of the most popular no-code automation platforms, and AI modules are everywhere — content generation, lead scoring, document processing, customer support.

The problem: Make shows you operations count, not AI cost. You know your scenario ran 5,000 times. You don't know those runs cost $420 in GPT-4o tokens — or that one scenario with a 4,000-token system prompt accounts for 70% of your total AI spend.

Without per-scenario cost visibility, you're flying blind. Most Make users discover their AI costs when the OpenAI invoice arrives — and by then, the money is already gone.


The Integration: HTTP Module → Tokonomics Proxy

Instead of using Make's built-in OpenAI module (which doesn't support custom base URLs), use the HTTP module to call the Tokonomics proxy. The proxy forwards your request to OpenAI, records the tokens and cost, and returns the response unchanged.

Before:  Make → api.openai.com → response
After:   Make → tokonomics.ca/proxy/openai → api.openai.com → response

Your scenario logic stays the same. The AI response is identical. But now every call is tracked with cost, tokens, model, and latency.


Step-by-Step Setup

1. Create an HTTP Module

In your Make scenario:

  1. Add a new module → search for HTTP → select Make a request
  2. Set URL to: https://tokonomics.ca/proxy/openai/chat/completions
  3. Set Method to POST

2. Configure Headers

Add these headers:

Header Value
Authorization Bearer mk_your_tokonomics_key
Content-Type application/json
X-Feature-Name your-scenario-name (optional, for cost attribution)

3. Set the Request Body

Select Body type: Raw, Content type: JSON

{
  "model": "gpt-4o-mini",
  "messages": [
    {
      "role": "system",
      "content": "You are a helpful assistant."
    },
    {
      "role": "user",
      "content": "{{1.input_text}}"
    }
  ],
  "max_tokens": 500
}

Replace {{1.input_text}} with the actual Make variable from a previous module.

4. Parse the Response

Select Parse response: Yes

The response JSON includes choices[0].message.content — map this to the next module in your scenario.


Using Claude (Anthropic) in Make

For Claude models, use the same HTTP module pattern:

{
  "model": "claude-sonnet-4-6",
  "max_tokens": 1024,
  "messages": [
    {
      "role": "user",
      "content": "{{1.input_text}}"
    }
  ]
}

The same works for DeepSeek (/proxy/deepseek/chat/completions), Gemini, Mistral, and all supported providers.


Per-Scenario Cost Attribution

The key to useful cost tracking is tagging each scenario. Add the X-Feature-Name header with the scenario name:

X-Feature-Name: lead-enrichment

For agencies managing multiple clients in Make:

X-Metering-Tags: {"scenario":"lead-enrichment","client":"acme-corp","env":"production"}

These headers are stripped before reaching OpenAI. In the Tokonomics dashboard, you can filter and group costs by scenario name, client, or any custom tag.

This is how agencies answer the question: "How much did client X's AI automations cost this month?"


What You See After Connecting

Your Tokonomics dashboard shows:

For a detailed guide on setting up alerts, see how to configure budget alerts.


Cost Optimization Tips for Make Users

Once you have visibility, here are the most common savings:

1. Switch to cheaper models where possible

Most classification, extraction, and simple summarization tasks work fine with GPT-4o-mini ($0.15/1M input) instead of GPT-4o ($2.50/1M input). That's a 94% cost reduction for the same accuracy on simple tasks.

Use the cheapest LLM for each use case guide to match tasks to models.

2. Trim your system prompts

Every token in your system prompt is billed on every call. A 3,000-token system prompt costs $0.0075 per GPT-4o call. At 5,000 calls/month, that's $37.50 just for the system prompt. Cut it to 1,000 tokens and save $25/month from one scenario.

3. Set max_tokens appropriately

If your scenario only needs a one-sentence answer, set max_tokens: 100 instead of the default 4,096. You pay for output tokens — limiting them caps your cost per call.

4. Watch for zombie scenarios

Scenarios that are "paused" in your mind but still active in Make. Check for scenarios running on a schedule that no longer serve a purpose.


Make Operations vs AI Cost

Make charges per operation. A single AI call is one operation. But the Make cost and the AI cost are completely different:

Make cost AI cost
1 GPT-4o call 1 operation (~$0.003) ~$0.01-0.05 per call
1,000 calls/month $3 in Make ops $10-50 in AI tokens

For most users, AI tokens cost 3-15x more than Make operations. Yet Make shows operations, not token cost. That's the gap Tokonomics fills.


Frequently Asked Questions

Why not use Make's built-in OpenAI module?

Make's OpenAI module doesn't support custom base URLs. The HTTP module does, which is what makes the proxy integration possible. The HTTP module also gives you more control over headers (for tagging) and request structure.

Does the proxy slow down my scenarios?

The proxy adds approximately 30ms per call (benchmark data). For AI calls that take 500ms-3,000ms, this is invisible. Your scenarios won't notice the difference.

Can I track costs across Make + other platforms?

Yes. If you also use n8n, Zapier, or custom code, all calls through the Tokonomics proxy appear in the same dashboard. One unified view of AI costs across all platforms.


Get Started

  1. Create a free Tokonomics account (100 calls/month free)
  2. Copy your API key
  3. Replace Make's OpenAI module with an HTTP module pointing to the proxy
  4. Add X-Feature-Name headers for per-scenario tracking
  5. Check your dashboard — your AI costs are now visible

All sources retrieved June 2026. Pricing: GPT-4o at $2.50/1M input tokens (OpenAI Pricing), GPT-4o-mini at $0.15/1M input tokens.

About the author
Founder & CTO at Tokonomics. Built the proxy after a $47,000 LLM invoice blindsided his team. Tracks LLM pricing weekly across 9 providers.
Connect on LinkedIn →
← Back to Blog