How to Track AI API Costs in Pipedream Workflows

TL;DR: In Pipedream's Node.js or Python steps, change the OpenAI baseURL to https://tokonomics.ca/proxy/openai and swap your API key for a Tokonomics key. Every AI call is metered. Setup: 2 lines of code.

Why Pipedream AI Workflows Need Cost Tracking

Pipedream is a developer-first automation platform — you write real code (Node.js or Python) in each step. This means you have full control over your OpenAI integration, but also full responsibility for tracking what it costs.

Pipedream's dashboard shows executions and credits. It does not show that your "enrich-lead" workflow consumed $180 in GPT-4o tokens last month, or that your system prompt is 3,000 tokens of mostly unnecessary instructions.

For developers running AI workflows at scale, the AI token cost often exceeds the Pipedream subscription cost by 5-10x. Yet there's no built-in way to see it.

Setup: 2 Lines of Code

Since Pipedream runs real code, the integration is the simplest of any automation platform. In a Node.js step:

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: "mk_your_tokonomics_key",
  baseURL: "https://tokonomics.ca/proxy/openai"
});

const response = await client.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [
    { role: "user", content: steps.trigger.event.body.text }
  ]
});

return response.choices[0].message.content;

The only changes from a normal OpenAI call: apiKey and baseURL. Everything else — the SDK, the methods, the response format — is identical.

Python Step

from openai import OpenAI

client = OpenAI(
    api_key="mk_your_tokonomics_key",
    base_url="https://tokonomics.ca/proxy/openai"
)

response = client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[
        {"role": "user", "content": steps["trigger"]["event"]["body"]["text"]}
    ]
)

return {"result": response.choices[0].message.content}

Adding Cost Tags

Pass custom headers for per-workflow cost attribution:

const response = await client.chat.completions.create({
  model: "gpt-4o-mini",
  messages: [{ role: "user", content: inputText }]
}, {
  headers: {
    "X-Feature-Name": "lead-enrichment",
    "X-Metering-Tags": JSON.stringify({
      workflow: "lead-enrichment",
      source: steps.trigger.event.source || "unknown",
      env: "production"
    })
  }
});

These headers are stripped before reaching OpenAI. In the Tokonomics dashboard, you can group costs by workflow, source, or any custom dimension.

Using Anthropic / Claude

const response = await fetch("https://tokonomics.ca/proxy/anthropic/messages", {
  method: "POST",
  headers: {
    "Authorization": `Bearer mk_your_tokonomics_key`,
    "Content-Type": "application/json",
    "X-Feature-Name": "document-analysis"
  },
  body: JSON.stringify({
    model: "claude-sonnet-4-6",
    max_tokens: 1024,
    messages: [{ role: "user", content: steps.trigger.event.body.text }]
  })
});

return await response.json();

Same pattern for DeepSeek (/proxy/deepseek/chat/completions), Gemini, Mistral, and all supported providers.

Pipedream Environment Variables

Store your Tokonomics key securely in Pipedream's environment variables:

1. Go to Settings → Environment Variables
2. Add TOKONOMICS_API_KEY = mk_your_key
3. Reference it in steps:

const client = new OpenAI({
  apiKey: process.env.TOKONOMICS_API_KEY,
  baseURL: "https://tokonomics.ca/proxy/openai"
});

This keeps your key out of the workflow code and makes it easy to rotate.

What You See in the Dashboard

After connecting:

• Cost per workflow (via X-Feature-Name tags)
• Model breakdown — which workflows use expensive vs cheap models
• Daily spend trend — is cost growing with usage?
• Token efficiency — input/output ratio per workflow
• Budget alerts — Slack, email, or webhook at configurable thresholds

Common Pipedream AI Patterns and Their Costs

The entity extraction and agent patterns are 10-50x more expensive than simple classification. Without cost tracking, you'd never know which workflow to optimize first.

Frequently Asked Questions

Can I use Pipedream's built-in OpenAI integration with the proxy?

Pipedream's pre-built OpenAI actions don't support custom base URLs. Use a Code step (Node.js or Python) instead — you get full control over the SDK configuration, and the setup is just 2 extra lines.

Does this work with Pipedream's free tier?

Yes. Pipedream's free tier includes 100 daily invocations. On the Tokonomics side, the Free plan includes 100 API calls/month.

What about streaming responses in Pipedream?

For webhook-triggered workflows, streaming usually isn't needed — you process the full response and pass it to the next step. But if you need streaming (e.g., SSE to a client), the Tokonomics proxy supports it fully.

Can I track Pipedream + other platforms in one dashboard?

Yes. All calls through the proxy — from Pipedream, n8n, Zapier, or custom code — appear in the same dashboard.

Get Started

1. Create a free Tokonomics account
2. Add your API key to Pipedream environment variables
3. Change baseURL in your OpenAI step — 2 lines of code
4. Add X-Feature-Name for per-workflow tracking
5. Check the dashboard after the first run

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.