Native Telegram Bot Trigger and Conditional Workflow Branching

Proposed Features:

1. Native Telegram Bot Trigger Node:

   • A dedicated "Telegram Trigger" node within AgenticFlow.

   • Functionality:

     • Allow users to securely input their Telegram Bot Token directly into the node configuration.

     • The node would then natively listen for incoming messages or specific commands sent to the configured Telegram bot.

     • It should be able to extract data from the Telegram message (e.g., message text, user ID, command parameters) and pass this data as outputs to subsequent nodes in the AgenticFlow workflow.

2. Conditional Branching based on Telegram Input / Conditional Node:

   • To make the Telegram integration more powerful, AF workflow should have the ability to implement conditional logic or branching within AgenticFlow, ideally triggered by the content of the Telegram message or command.
     Requested here for Conditional Node / Control Flow Node:

     https://agenticflow.featurebase.app/p/control-flow-sequential-conditional-loops

   • Functionality:

     • Command-Based Branching: Allow different AgenticFlow paths or even entirely different sub-workflows to be triggered based on the specific command received by the Telegram bot (e.g., /order_status triggers one set of actions, /new_ticket triggers another).

     • Conditional Node: Introduce a "Conditional" or "Router" node that can evaluate the incoming data (e.g., from the Telegram Trigger) and direct the flow down different branches based on defined rules (e.g., if message contains "urgent", go to path A; if message contains "info", go to path B).

     • This would allow a single Telegram bot trigger to intelligently route to various processes within AgenticFlow.

Use Case Example: A user interacts with a Telegram bot:

• If they send /check_invoice <invoice_id>, the native Telegram Trigger captures this. A Conditional node then routes this to an "Invoice Lookup" series of steps in AgenticFlow.

• If they send /submit_feedback <feedback_text>, the same Telegram Trigger captures it, but the Conditional node routes it to a "Feedback Processing" series of steps.

Benefits:

• Simplified Integration: Greatly reduces the effort and technical expertise needed to connect Telegram bots to AgenticFlow.

• No-Code/Low-Code: Aligns with the ease-of-use philosophy of visual automation builders.

• More Powerful & Flexible Automations: Enables sophisticated workflows that can react dynamically to different user inputs from Telegram.