Back to Catalog

Calculate Embodied Carbon (CO2) for Revit/IFC Models using AI Classification

Artem BoikoArtem Boiko
332 views
2/3/2026
Official Page

Estimate embodied carbon (CO2e) for grouped BIM/CAD elements. The workflow accepts an existing XLSX (grouped element data) or, if missing, can trigger a local RvtExporter.exe to generate one. It detects category fields, filters out non-building elements, infers aggregation rules with AI, computes CO2 using densities & emission factors, and exports a multi-sheet Excel plus a clean HTML report.

What it does

  • Reads or builds XLSX (from your model via RvtExporter.exe when needed).
  • Finds category/volumetric fields; separates building vs. annotation elements.
  • Uses AI to infer aggregation rules (sum/mean/first) per header.
  • Groups rows by your group_by field and aggregates totals.
  • Prepares enhanced prompts and calls your LLM to classify materials and estimate CO2 (A1-A3 minimum).
  • Computes project totals and generates a multi-sheet XLSX + HTML report with charts and hotspots.

Prerequisites

  • LLM credentials for one provider (e.g., OpenAI, Anthropic, Gemini, Grok/OpenRouter). Enable one chat node and connect credentials.
  • Windows host only if you want to auto-extract from .rvt/.ifc via RvtExporter.exe. If you already have an XLSX, Windows is not required.
  • Optional: mapping/classifier files (XLSX/CSV/PDF) to improve material classification.

How to use

  1. Import this JSON into n8n.
  2. Open the Setup/Parameters node(s) and set:
    • project_file — path to your .rvt/.ifc or to an existing grouped *_rvt.xlsx
    • path_to_converterC:\\DDC_Converter_Revit\\datadrivenlibs\\RvtExporter.exe (optional)
    • group_by — e.g., Type Name / Category / IfcType
    • sheet_name — default Summary (if reading from XLSX)
  3. Enable one LLM node and attach credentials; keep others disabled.
  4. Execute (Manual Trigger). The workflow detects/builds the XLSX, analyzes, classifies, estimates CO2, then writes Excel and opens the HTML report.

Outputs

  • Excel (CO2_Analysis_Report_YYYY-MM-DD.xlsx, ~8 sheets): Executive Summary, All Elements, Material Summary, Category Analysis, Impact Analysis, Top 20 Hotspots, Data Quality, Recommendations.
  • HTML: executive report with key KPIs and charts.
  • Per-group fields include: Material (EU/DE/US), Quantity & Unit, Density, Mass, CO2 Factor, Total CO2 (kg/tonnes), CO2 %, Confidence, Assumptions.

Notes & tips

  • Input quantities (volumes/areas) are already aggregated per group — do not multiply by element count.
  • Use -no-collada upstream if you only need XLSX in extraction.
  • Prefer ASCII-safe paths and ensure write permissions to output folder.

Categories

Data Extraction · Files & Storage · ETL · CAD/BIM · Carbon/ESG

Tags

cad-bim, co2, carbon, embodied-carbon, lca, revit, ifc, xlsx, html-report, llm

Author

DataDrivenConstruction.io info@datadrivenconstruction.io

Consulting and Training

We work with leading construction, engineering, consulting agencies and technology firms around the world to help them implement open data principles, automate CAD/BIM processing and build robust ETL pipelines.

If you would like to test this solution with your own data, or are interested in adapting the workflow to real project tasks, feel free to contact us.

Docs & Issues:
Full Readme on GitHub

# n8n Workflow: AI-Powered Carbon Footprint Calculation for Revit Models

This n8n workflow demonstrates a robust process for calculating the embodied carbon (CO2) for Revit models, leveraging AI classification, data processing, and local file operations. It's designed to automate the extraction, classification, and calculation of carbon data from a spreadsheet, providing a structured output.

## What it does

This workflow automates the following steps:

1.  **Manual Trigger**: Initiates the workflow upon a manual click, allowing for on-demand execution.
2.  **Read Binary File**: Reads a binary file, likely a spreadsheet containing Revit model data or material lists.
3.  **Spreadsheet File Conversion**: Converts the binary file into a structured spreadsheet format for easier processing.
4.  **Loop Over Items**: Iterates through each item (row) in the processed spreadsheet data.
5.  **AI Agent (Classification)**: For each item, an AI agent (configured to use either OpenAI, Anthropic, or xAI Grok Chat Models) is employed. This agent is likely responsible for classifying materials or components within the Revit model data to determine their carbon impact.
    *   **Anthropic Chat Model**: An alternative AI model for classification.
    *   **OpenAI Chat Model**: Another alternative AI model for classification.
    *   **xAI Grok Chat Model**: A third alternative AI model for classification.
6.  **Edit Fields (Set)**: Modifies or adds new fields to the data, potentially enriching it with AI classification results or preparing it for carbon calculation.
7.  **If Condition**: Evaluates a condition based on the processed data (e.g., checking if the AI classification was successful or if specific data points exist).
8.  **Execute Command (True Branch)**: If the condition is true, a shell command is executed. This could be for running a local script to perform carbon calculations, interact with a local database, or trigger another system.
9.  **Code (False Branch)**: If the condition is false, a custom JavaScript code snippet is executed. This might handle error logging, default values, or alternative processing.
10. **Merge**: Combines the data streams from both the "If" node's true and false branches, ensuring all processed items are rejoined.
11. **Write Binary File**: Writes the final processed data (potentially including calculated carbon footprints) back to a binary file, likely a new spreadsheet or a report.

## Prerequisites/Requirements

To use this workflow, you will need:

*   **n8n Instance**: A running n8n instance.
*   **AI Service Credentials**:
    *   An **OpenAI API Key** (if using the OpenAI Chat Model or OpenAI Agent).
    *   An **Anthropic API Key** (if using the Anthropic Chat Model).
    *   An **xAI Grok API Key** (if using the xAI Grok Chat Model).
*   **Local System Access**: The n8n instance needs permissions to execute shell commands (`Execute Command` node) and read/write binary files (`Read Binary File`, `Write Binary File` nodes) on the host system.
*   **Input Spreadsheet**: A spreadsheet file containing the Revit model data (e.g., material lists, quantities, component types) that needs to be processed.
*   **Carbon Calculation Logic/Script**: Any external scripts or tools that the `Execute Command` node will call to perform the actual embodied carbon calculations based on the AI-classified data.

## Setup/Usage

1.  **Import the workflow**: Download the JSON provided and import it into your n8n instance.
2.  **Configure Credentials**:
    *   For the `AI Agent`, `Anthropic Chat Model`, `OpenAI Chat Model`, and `xAI Grok Chat Model` nodes, configure your respective API credentials.
3.  **Specify File Paths**:
    *   In the `Read Binary File` node, specify the full path to your input Revit model data spreadsheet.
    *   In the `Write Binary File` node, specify the desired output path and filename for the processed carbon footprint report.
4.  **Customize AI Agent**: Adjust the prompt and configuration of the `AI Agent` node to accurately classify your Revit model components based on your specific data and desired carbon categories. You may choose between OpenAI, Anthropic, or xAI Grok models within the AI Agent configuration.
5.  **Customize `Execute Command`**: If you have a custom script for carbon calculation, update the `Execute Command` node with the appropriate command and arguments to run your script, passing the necessary data from the workflow.
6.  **Review `Code` Node**: If the "If" condition leads to the `Code` node, ensure its JavaScript logic aligns with your error handling or alternative processing requirements.
7.  **Execute Workflow**: Click "Execute Workflow" in the `Manual Trigger` node to run the process.

This workflow provides a powerful framework for integrating AI classification into environmental impact assessments for architectural and construction projects, streamlining the calculation of embodied carbon for Revit models.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942