HumationHuman + Automation
Back to Catalog

Epa clean water act data access & compliance monitoring API integration

David AshbyDavid Ashby
117 views
2/3/2026
Exchange RateFinanceUSD BRLCurrencyAPI
Official Page

⚠️ ADVANCED USE ONLY - U.S. EPA Enforcement and Compliance History Online (ECHO) - Clean Water Act (CWA) Rest Services MCP Server (36 operations)

🚨 This workflow is for advanced users only!

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?

Join the community

This MCP server contains 36 operations which is significantly more than the recommended maximum of tools for most AI clients.

🔍 Recommended Alternative for basic use cases

Seek a simplified MCP server that utilizes the official n8n tool implementation for U.S. EPA Enforcement and Compliance History Online (ECHO) - Clean Water Act (CWA) Rest Services if available, or an MCP server with only common operations as it will be more efficient and easier to manage.

🛠️ Advanced Usage Requirements

BEFORE adding this MCP server to your client:

Disable or delete unused nodes - Review sections and disable/delete those you don't need

AFTER adding the MCP server to your client: 1.Selective tool enabling - Instead of enabling all tools (default), manually select only the specific tools you need for that Workflow's MCP client. 2. Monitor performance - Too many tools can slow down AI responses

💡 Pro Tips

Keep maximum 40 enabled tools - Most AI clients perform better with fewer tools

  • Group related operations and only enable one group at a time

  • Use the overview note to understand what each operation group does

  • Ping me on discord if your business needs this implemented professionally

⚡ Quick Setup

  1. Import this workflow into your n8n instance
  2. Credentials Add U.S. EPA Enforcement and Compliance History Online (ECHO) - Clean Water Act (CWA) Rest Services credentials
  3. Activate the workflow to start your MCP server
  4. Copy the webhook URL from the MCP trigger node
  5. Connect AI agents using the MCP URL

🔧 How it Works

This workflow converts the U.S. EPA Enforcement and Compliance History Online (ECHO) - Clean Water Act (CWA) Rest Services API into an MCP-compatible interface for AI agents.

• MCP Trigger: Serves as your server endpoint for AI agent requests • HTTP Request Nodes: Handle API calls to https://echodata.epa.gov/echo • AI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Returns responses directly to the AI agent

📋 Available Operations (36 total)

🔧 Cwa_Rest_Services.Get_Download (2 endpoints)

• GET /cwa_rest_services.get_download: Submit CWA Download Data • POST /cwa_rest_services.get_download: Clean Water Act (CWA) Download Data Service

🔧 Cwa_Rest_Services.Get_Facilities (2 endpoints)

• GET /cwa_rest_services.get_facilities: Submit CWA Facility Search • POST /cwa_rest_services.get_facilities: Clean Water Act (CWA) Facility Search Service

🔧 Cwa_Rest_Services.Get_Facility_Info (2 endpoints)

• GET /cwa_rest_services.get_facility_info: Submit CWA Facility Details • POST /cwa_rest_services.get_facility_info: Clean Water Act (CWA) Facility Enhanced Search Service

🔧 Cwa_Rest_Services.Get_Geojson (2 endpoints)

• GET /cwa_rest_services.get_geojson: Submit CWA GeoJSON Data • POST /cwa_rest_services.get_geojson: Clean Water Act (CWA) GeoJSON Service

🔧 Cwa_Rest_Services.Get_Info_Clusters (2 endpoints)

• GET /cwa_rest_services.get_info_clusters: Submit CWA Info Clusters • POST /cwa_rest_services.get_info_clusters: Clean Water Act (CWA) Info Clusters Service

🔧 Cwa_Rest_Services.Get_Map (2 endpoints)

• GET /cwa_rest_services.get_map: Submit CWA Map Data • POST /cwa_rest_services.get_map: Clean Water Act (CWA) Map Service

🔧 Cwa_Rest_Services.Get_Qid (2 endpoints)

• GET /cwa_rest_services.get_qid: Submit CWA Paginated Results • POST /cwa_rest_services.get_qid: Clean Water Act (CWA) Paginated Results Service

🔧 Cwa_Rest_Services.Metadata (2 endpoints)

• GET /cwa_rest_services.metadata: Submit CWA Metadata • POST /cwa_rest_services.metadata: Clean Water Act (CWA) Metadata Service

🔧 Rest_Lookups.Bp_Tribes (2 endpoints)

• GET /rest_lookups.bp_tribes: Submit BP Tribes Data • POST /rest_lookups.bp_tribes: ECHO BP Tribes Lookup Service

🔧 Rest_Lookups.Cwa_Parameters (2 endpoints)

• GET /rest_lookups.cwa_parameters: Submit CWA Parameters • POST /rest_lookups.cwa_parameters: ECHO CWA Parameter Lookup Service

🔧 Rest_Lookups.Cwa_Pollutants (2 endpoints)

• GET /rest_lookups.cwa_pollutants: Submit CWA Pollutants • POST /rest_lookups.cwa_pollutants: ECHO CWA Pollutants Lookup Service

🔧 Rest_Lookups.Federal_Agencies (2 endpoints)

• GET /rest_lookups.federal_agencies: Submit Federal Agencies • POST /rest_lookups.federal_agencies: ECHO Federal Agency Lookup Service

🔧 Rest_Lookups.Icis_Inspection_Types (2 endpoints)

• GET /rest_lookups.icis_inspection_types: Submit ICIS Inspection Types • POST /rest_lookups.icis_inspection_types: ECHO ICIS NPDES Inspection Types Lookup Service

🔧 Rest_Lookups.Icis_Law_Sections (2 endpoints)

• GET /rest_lookups.icis_law_sections: Submit ICIS Law Sections • POST /rest_lookups.icis_law_sections: ECHO ICIS NPDES Law Sections Lookup Service

🔧 Rest_Lookups.Naics_Codes (2 endpoints)

• GET /rest_lookups.naics_codes: Submit NAICS Codes • POST /rest_lookups.naics_codes: ECHO NAICS Codes Lookup Service

🔧 Rest_Lookups.Npdes_Parameters (2 endpoints)

• GET /rest_lookups.npdes_parameters: Submit NPDES Parameters • POST /rest_lookups.npdes_parameters: ECHO NPDES Parameters Lookup Service

🔧 Rest_Lookups.Wbd_Code_Lu (2 endpoints)

• GET /rest_lookups.wbd_code_lu: Submit WBD Codes • POST /rest_lookups.wbd_code_lu: ECHO WBD Code Lookup Service

🔧 Rest_Lookups.Wbd_Name_Lu (2 endpoints)

• GET /rest_lookups.wbd_name_lu: Submit WBD Names • POST /rest_lookups.wbd_name_lu: ECHO WBD Name Lookup Service

🤖 AI Integration

Parameter Handling: AI agents automatically provide values for: • Path parameters and identifiers • Query parameters and filters • Request body data • Headers and authentication

Response Format: Native U.S. EPA Enforcement and Compliance History Online (ECHO) - Clean Water Act (CWA) Rest Services API responses with full data structure

Error Handling: Built-in n8n HTTP request error management

💡 Usage Examples

Connect this MCP server to any AI agent or workflow:

• Claude Desktop: Add MCP server URL to configuration • Cursor: Add MCP server SSE URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

• Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n HTTP request handling and logging • Extensible: Easily modify or add custom logic

> 🆓 Free for community use! Ready to deploy in under 2 minutes.

n8n Model Context Protocol (MCP) Server Trigger Workflow

This n8n workflow demonstrates the basic setup for an n8n Model Context Protocol (MCP) Server. It acts as a listening endpoint for MCP requests, enabling integration with AI models and agents that communicate using the MCP specification.

What it does

This workflow serves as a foundational component for AI-driven automation:

  1. Listens for MCP Requests: The "MCP Server Trigger" node waits for incoming requests formatted according to the Model Context Protocol.
  2. Provides a Base Endpoint: It establishes a dedicated URL within your n8n instance where AI models or agents can send their context and receive responses.
  3. Acts as a Starting Point: While this specific workflow is minimal, it's designed to be extended. Subsequent nodes would process the incoming MCP data, interact with other services (databases, APIs, etc.), and formulate a response back to the requesting AI.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (cloud or self-hosted).
  • Understanding of Model Context Protocol (MCP): Familiarity with how AI models/agents use MCP to exchange context and data.

Setup/Usage

  1. Import the Workflow:
    • Copy the JSON content of this workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots (...) in the top right corner and select "Import from JSON".
    • Paste the JSON content and click "Import".
  2. Activate the Workflow:
    • After importing, ensure the workflow is active by toggling the "Active" switch in the top right corner.
  3. Identify the Trigger URL:
    • Once active, the "MCP Server Trigger" node will display a webhook URL. This is the endpoint your AI models or agents will use to send MCP requests.
  4. Extend the Workflow:
    • To make this workflow functional for a specific use case, you will need to add more nodes after the "MCP Server Trigger". These nodes would typically:
      • Parse the incoming MCP data.
      • Perform actions based on the context (e.g., query a database, call an external API, generate text with an LLM).
      • Format a response back in the MCP format.
      • Use the "Respond to Webhook" node to send the response back to the AI agent.

Related Templates

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113

Track daily moods with AI analysis & reports using GPT-4o, Data Tables & Gmail

Track your daily mood in one tap and receive automated AI summaries of your emotional trends every week and month. Perfect for self-reflection, wellness tracking, or personal analytics. This workflow logs moods sent through a webhook (/mood) into Data Tables, analyzes them weekly and monthly with OpenAI (GPT-4o), and emails you clear summaries and actionable recommendations via Gmail. ⚙️ How It Works Webhook – Mood → Collects new entries (🙂, 😐, or 😩) plus an optional note. Set Mood Data → Adds date, hour, and note fields automatically. Insert Mood Row → Stores each record in a Data Table. Weekly Schedule (Sunday 20:00) → Aggregates the last 7 days and sends a summarized report. Monthly Schedule (Day 1 at 08:00) → Aggregates the last 30 days for a deeper AI analysis. OpenAI Analysis → Generates insights, patterns, and 3 actionable recommendations. Gmail → Sends the full report (chart + AI text) to your inbox. 📊 Example Auto-Email Weekly Mood Summary (last 7 days) 🙂 5 ██████████ 😐 2 ████ 😩 0 Average: 1.7 (Positive 🙂) AI Insights: You’re trending upward this week — notes show that exercise days improved mood. Try keeping short walks mid-week to stabilize energy. 🧩 Requirements n8n Data Tables enabled OpenAI credential (GPT-4o or GPT-4 Turbo) Gmail OAuth2 credential to send summaries 🔧 Setup Instructions Connect your credentials: Add your own OpenAI and Gmail OAuth2 credentials. Set your Data Table ID: Open the Insert Mood Row node and enter your own Data Table ID. Without this, new moods won’t be stored. Replace the email placeholder: In the Gmail nodes, replace your.email@example.com with your actual address. Deploy and run: Send a test POST request to /mood (e.g. { "mood": "🙂", "note": "productive day" }) to log your first entry. ⚠️ Before activating the workflow, ensure you have configured the Data Table ID in the “Insert Mood Row” node. 🧠 AI Analysis Interprets mood patterns using GPT-4o. Highlights trends, potential triggers, and suggests 3 specific actions. Runs automatically every week and month. 🔒 Security No personal data is exposed outside your n8n instance. Always remove or anonymize credential references before sharing publicly. 💡 Ideal For Personal mood journaling and AI feedback Therapists tracking client progress Productivity or self-quantification projects 🗒️ Sticky Notes Guide 🟡 Mood Logging Webhook POST /mood receives mood + optional note. ⚠️ Configure your own Data Table ID in the “Insert Mood Row” node before running. 🟢 Weekly Summary Runs every Sunday 20:00 → aggregates last 7 days → generates AI insights + emails report. 🔵 Monthly Summary Runs on Day 1 at 08:00 → aggregates last 30 days → creates monthly reflection. 🟣 AI Analysis Uses OpenAI GPT-4o to interpret trends and recommend actions. 🟠 Email Delivery Sends formatted summaries to your inbox automatically.

Jose CastilloBy Jose Castillo
105

Create, update, and get a person from Copper

This workflow allows you to create, update, and get a person from Copper. Copper node: This node will create a new person in Copper. Copper1 node: This node will update the information of the person that we created using the previous node. Copper2 node: This node will retrieve the information of the person that we created earlier.

Harshil AgrawalBy Harshil Agrawal
603