This article provides a complete, practical walkthrough of the Send n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Simple setup in 5-15 minutes. One‑time purchase: €9.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Leveraging n8n, Telegram, and Google Perspective API to Combat Toxicity in Real-Time
   
   Meta Description:  
   Discover how a simple n8n workflow utilizes Telegram and Google Perspective API to detect and respond to toxic language in real-time, helping create a safer online space.
   
   Keywords:  
   n8n workflow, Telegram bot, toxic language detection, Google Perspective API, automated moderation, profanity filter, chat moderation bot, no-code automation, real-time content analysis
   
   Third-party APIs Used:
   
   1. Telegram API (via n8n): For interacting with Telegram messages and responding to users.
   2. Google Perspective API: For analyzing the text content and detecting profanity/toxic language.
   
   Article:
   
   In an age where online communities are growing rapidly, maintaining a safe and respectful environment is more crucial than ever. Whether you manage a group chat or run a public telegram channel, toxic language can diminish user experience, encourage harmful behavior, and even violate platform policies. Thankfully, with modern automation tools like n8n, enforcing chat moderation has become significantly easier — even for non-developers.
   
   In this article, we’ll explore a powerful yet simple n8n workflow that detects toxic language in incoming Telegram messages using the Google Perspective API. If a message crosses a predefined toxicity threshold, the bot responds instantly, helping to discourage inappropriate behavior and maintain community standards.
   
   Understanding the Workflow
   
   At its core, the workflow is a combination of a Telegram Trigger, the Google Perspective API for content analysis, and conditional logic to take action based on the toxicity level of a message.
   
   Let's break down how the workflow operates:
   
   1. Telegram Trigger Node  
   This node listens for incoming messages in a Telegram chat using a configured bot via the Telegram API. Each message received becomes an input for subsequent analysis.
   
   2. Google Perspective API Integration  
   Once a message is received, it is sent to the Google Perspective API using OAuth2 credentials. Perspective API’s core function is analyzing the “toxicity” of a given text, which in this case is configured to focus specifically on "profanity" as the attribute of concern.
   
   3. Setting Conditions for Action  
   Using an IF node in n8n, the workflow compares the profanity score from Perspective API against a preset threshold. In this workflow, if the “PROFANITY” attribute’s summaryScore.value exceeds 0.7, the message is considered too toxic.
   
   4. Automated Response  
   If the message is indeed flagged as profane, the bot automatically posts a reply to the sender with a stern warning: “I don't tolerate toxic language!” This message is sent via the Telegram API and is configured to respond directly to the offending message using its message ID.
   
   What Makes This Workflow Powerful?
   
   - Real-Time Moderation  
   The use of Telegram's webhook system allows this workflow to operate in real-time, responding instantly to toxic content and reinforcing community behavior standards.
   
   - No-Code Setup  
   n8n allows users to create this logic visually without writing complex code. This makes it ideal for community managers, educators, and small businesses with no developer resources.
   
   - Scalable and Customizable  
   The Google Perspective API supports a variety of other attributes such as “threat,” “insult,” and “identity attack,” which can easily be incorporated into this workflow to create more nuanced moderation logic.
   
   - Privacy and Control  
   Since you host n8n on your own infrastructure (or services like n8n.cloud), you retain full control over the data flow and privacy levels in your automation logic.
   
   Security and Ethical Considerations
   
   While AI-powered moderation systems are highly beneficial, it’s important to use them responsibly. Automated bans or message deletions can be controversial, especially when AI occasionally misinterprets the context of a message. In this example, the workflow limits its actions to a warning message, striking a good balance between moderation and respectful dialogue.
   
   For critical applications, human-in-the-loop (HITL) moderation systems may be more appropriate. This can also be enhanced in future versions of the automation by logging flagged messages for admin review.
   
   Getting Started
   
   To replicate or modify this workflow yourself, you’ll need:
   - A Telegram bot token (created via BotFather on Telegram).
   - An account and API key for Google’s Perspective API (with credentials added to n8n).
   - Access to an n8n instance (either self-hosted or cloud-based).
   - Basic understanding of n8n’s nodes and how to work with expressions.
   
   From there, you can build your own community-specific moderation bot — adjusting thresholds, expanding attribute checks, or integrating database logging.
   
   Conclusion
   
   This n8n workflow is a powerful example of how low-code automation platforms can be used creatively to solve real-world problems. By integrating Telegram and Google Perspective's AI-driven content analysis, even basic users can manage online toxicity efficiently and in real time.
   
   Whether you’re moderating a gaming chat, educational group, or internal team dialogue, this workflow empowers you to promote healthier communication standards — at the click of a button.
   
   Ready to build your own moderation bot? n8n and these powerful APIs are right at your fingertips.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.