π₯ Token Estim8r -sub workflow to track AI model token usage and cost with JinaAI

Save Your Tokens from Evil King Browser
> Image Generated with ideoGener8r n8n workflow template
π Estimate token usage and AI model cost from any workflow in n8n
πββοΈ Who is this for?
This workflow is ideal for AI engineers, automation specialists, and business analysts who use OpenAI, Anthropic, or other token-based large language models (LLMs) in their n8n workflows and want to track their usage and accuratley estimate associated costs.
Whether you're prototyping workflows or deploying in production, this tool gives you insight into how many tokens you're using and what that translates to in actual dollars.
π What problem is this workflow solving?
n8n users running AI-based workflows often struggle to track how many tokens were used per execution and how much those tokens cost. Without visibility into usage, itβs easy to lose track of API spending.
This workflow solves that problem by:
- Logging token counts and costs to Google Sheets
- Supporting prompt and completion token counts
- Providing live pricing (optional, via Jina AI API)
βοΈ What this workflow does
This template allows you to analyze the token usage and cost of any workflow in n8n. It uses an Execute Workflow node to call the Token Estim8r utility, which:
- Estimates prompt and completion tokens
- Retrieves model pricing (either statically or live via Jina API)
- Calculates the total cost
- Logs the data to a connected Google Sheet with timestamp and model info
π οΈ Setup Instructions
-
Create Google Sheet: Copy and paste the CSV template below into a
.csvfile and upload to Google Sheets:timestamp, Total Tokens, Prompt Tokens, Completion Tokens, Models Used, Tools Used, Total Cost, Json Array -
Set up pricing (optional): In the
Get AI Pricingnode, add your Jina API Auth Header if you want live pricing. -
Select the correct Google Sheet: Ensure your workflow is pointing to the imported sheet.
-
Attach to your target workflow: Add an
Execute Workflownode to the end of your target workflow. -
Point to this Token Estim8r: Choose this template as the executed workflow and send
{{ $execution.id }}as the input. -
Run and view results: Trigger the target workflow and see your token usage and cost data populate in the sheet.
π§ How to customize this workflow to your needs
- Change the logging destination: Instead of Google Sheets, connect to Airtable, Notion, or a database.
- Support multiple models: Extend the price-mapping logic to cover your own model providers.
- Add Slack alerts: Send a notification if a workflow exceeds a token or cost threshold.
- Aggregate costs: Create a weekly summary workflow that totals cost by workflow or model.
> This utility workflow works across all n8n deployment types and uses only built-in nodes.
n8n Sub-Workflow: AI Model Token Usage and Cost Tracker (Jina AI)
This n8n sub-workflow is designed to track and log AI model token usage and associated costs, specifically for Jina AI models, into a Google Sheet. It acts as a backend service that can be called by other workflows whenever an AI model interaction occurs.
Description
This workflow simplifies the process of monitoring AI model consumption by receiving token usage data, calculating the cost based on a predefined rate, and then appending this information to a designated Google Sheet. This allows for easy tracking and analysis of AI service expenditures.
What it does
- Receives Data: It starts by listening for execution requests from another workflow, expecting input data containing details about AI model usage (e.g., model name, input tokens, output tokens, timestamp).
- Calculates Cost: A Code node processes the received token counts (input and output) and, based on hardcoded rates for Jina AI models, calculates the total cost of the AI interaction.
- Prepares Data for Google Sheets: An "Edit Fields (Set)" node structures the data into a format suitable for appending to a Google Sheet, including the model name, input tokens, output tokens, total tokens, and calculated cost.
- Logs to Google Sheets: Finally, it appends the prepared token usage and cost data as a new row to a specified Google Sheet.
Prerequisites/Requirements
- n8n Instance: A running n8n instance to host and execute the workflow.
- Google Account: A Google account with access to Google Sheets.
- Google Sheets Credential: An n8n Google Sheets credential configured to allow writing to your desired spreadsheet.
- Jina AI Model Usage: This workflow is specifically designed to track usage from Jina AI models, with hardcoded token pricing. If you use other models or providers, you will need to adjust the pricing logic in the "Code" node.
Setup/Usage
- Import the Workflow: Import this JSON definition into your n8n instance as a new workflow.
- Configure Google Sheets Node:
- Select your Google Sheets credential.
- Specify the Spreadsheet ID of the Google Sheet where you want to log the data.
- Specify the Sheet Name (e.g., "Sheet1").
- Ensure the first row of your Google Sheet contains headers matching the keys output by the "Edit Fields (Set)" node (e.g.,
model,inputTokens,outputTokens,totalTokens,cost).
- Review and Adjust Code Node (Optional):
- The "Code" node contains the pricing logic for Jina AI models. If Jina AI changes its pricing, or if you wish to track other models, you will need to update the
modelPricesobject within this node.
- The "Code" node contains the pricing logic for Jina AI models. If Jina AI changes its pricing, or if you wish to track other models, you will need to update the
- Activate the Workflow: Set the workflow to "Active" to enable it to receive calls.
- Call from Another Workflow: This workflow is designed to be called as a sub-workflow using an "Execute Workflow" node from another n8n workflow. The calling workflow should pass an item with the following structure:
(The{ "model": "jina-embeddings-v2-base-en", "inputTokens": 100, "outputTokens": 0, "timestamp": "2023-10-27T10:00:00Z" }timestampis optional as the workflow adds its own, but can be overridden.)
This setup allows you to centralize your AI token usage tracking across various n8n workflows that interact with Jina AI models.
Related Templates
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch π LinkedIn β Wessel Bulte
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack
AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. ποΈπ€π Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (β€3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | π Professional Services Need help with implementation or customization? Our team offers: π― Custom workflow development π’ Enterprise deployment support π Team training sessions π§ Ongoing maintenance π Custom reporting & dashboards π Additional API integrations Discover more workflows β Get in touch with us