Skip to main content

Delete Dialogflow intents via Telegram commands

Workflow preview

Workflow preview
100%
Delete Dialogflow intents via Telegram commands preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Delete a Dialogflow Intent via Telegram ️ This workflow allows you to delete a specific Dialogflow intent simply by sending the keyword through Telegram. It’s designed for quick and safe deletion...

Best for

  • Engineering automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.telegramtrigger, n8n-nodes-base.stickynote, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.telegram, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Eddy Medina.

Original n8n.io source

1.1 Workflow description

Title
Delete Dialogflow intents via Telegram commands
Workflow name
Delete Dialogflow intents via Telegram commands

Delete a Dialogflow Intent via Telegram 🗑️

This workflow allows you to delete a specific Dialogflow intent simply by sending the keyword delete through Telegram. It’s designed for quick and safe deletions from your mobile device, without needing to access the Dialogflow console.


🔧 What does this workflow do?

  1. Listens for Telegram messages using the Telegram Trigger node.
  2. Validates the user ID through the User validation by ID node, ensuring only authorized users can trigger the deletion.
  3. Checks if the message equals delete using the Keyword validation node.
  4. If both checks pass:
    • Performs an HTTP GET request via HTTP Request GET NAME to retrieve the name of the intent (used in the confirmation message).
    • Adds a small delay using simulated delay.
    • Then executes a DELETE request to the Dialogflow API via the HTTP Request ELIMINAR node to delete the intent.
    • Sends a Telegram confirmation message through the Confirmation message node.
  5. If the user ID or keyword is invalid:
    • Responds with a custom message using either Invalid user message or Invalid keyword message.

📌 Requirements

  • A valid Google API credential (Service Account) set up in n8n.
  • Obtain your PROJECT_ID and INTENT_ID from the URL of the intent in Dialogflow:

✅ Use Cases

  • Delete test or unused intents without opening Dialogflow.
  • Automate cleanup of outdated intents.
  • Allow controlled Telegram-based access for specific users to delete intents remotely.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.2

Block 2 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - HTTP Request ELIMINAR

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 8 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - User validation by ID

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 10 - Keyword validation

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 11 - Invalid user message

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 12 - Invalid keyword message

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 13 - HTTP Request GET NAME

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 14 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - simulated delay

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 16 - Confirmation message

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 17 - HTTP Request GET

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

3. Summary Table

Workflow Delete Dialogflow intents via Telegram commands
Complexity advanced
Nodes 17
Categories Engineering, Multimodal AI
Author Eddy Medina
Published 14 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7409/7409.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Delete Dialogflow intents via Telegram commands do?

Delete a Dialogflow Intent via Telegram ️ This workflow allows you to delete a specific Dialogflow intent simply by sending the keyword through Telegram. It’s designed for quick and safe deletion...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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, Multimodal AI use case.