Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Ever wondered how much your AI Agent is costing you per run? I had no idea. You build an agent, it works great, but behind the scenes tokens are burning. And you just see the API key cost as an agg...
n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.n8n, n8n-nodes-base.splitinbatches, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.datatable
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ben van Steenbergen.
Original n8n.io sourceEver wondered how much your AI Agent is costing you per run?
I had no idea. You build an agent, it works great, but behind the scenes tokens are burning. And you just see the API-key cost as an aggregated value on Stripe, right?
One workflow costs you $0.002. Another one quietly racks up $2.00 every time it fires. Without tracking, you're flying blind.
This workflow fixes that.
Anyone running AI agents in n8n who wants to know what they actually cost before the bill surprises you.
Every hour, it scans all your tagged (triggers on worklow TAGS) AI agent workflows and extracts the exact token usage per model, calculates the estimated cost in USD, and stores a receipt in an DataTable.
execution_receipts with columns: workflowid (text), executionid (text), receipt (text), created_at (text), units (number) — or import the CSV templateagentagent via the n8n APINew models are auto-detected. To add pricing for a newly released model, add one line to the MODEL_RATES table inside the code node.
Self-hosted users may need to enable Data Tables with N8N_ENABLED_MODULES=data-table in their environment.
Like this workflow? Let me know! Follow me on LinkedIn for more n8n automation and AI agent builds.
Cheers, Ben
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Track AI agent token costs and store receipts with the n8n API and Data Tables |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Engineering, AI Summarization |
| Author | Ben van Steenbergen |
| Published | 20 Apr 2026 |
Use the JSON export at /data/workflows/15177/15177.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Ever wondered how much your AI Agent is costing you per run? I had no idea. You build an agent, it works great, but behind the scenes tokens are burning. And you just see the API key cost as an agg...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, AI Summarization use case.