Challenges Implementing A Reliable Queueing Mechanism

Why Am I Here ?

I’m building a Telegram virtual assistant using n8n to automate responses to user queries. The bot should handle both text and audio messages, leveraging AI for intelligent responses.

Current Progress…

Workflow Foundation: I’ve set up the basic n8n workflow with a Telegram Trigger node, Switch node (to separate text and audio), Edit Fields node, AI Agent node, and Telegram Output node.

Audio Transcription: Integrated OpenAI’s transcription tool to convert audio messages to text before sending them to the AI Agent.

AI Integration: Connected the AI Agent node to Anthropic and Google for generating responses.

Challenges…

Queueing Mechanism: I’m facing challenges implementing a reliable queueing mechanism to handle user messages sequentially. I have two options:

  1. Code Node Approach: Using code nodes for queueing leads to “Unknown error” messages that need debugging.

  2. Redis Approach: Implementing Redis requires assistance with installation, configuration, and integration with n8n.

Seeking Assistance On !

I’m looking for a JavaScript developer or someone with Redis expertise to help me:

Option 1 (Code Node)…

  • Debug and resolve the “Unknown error” messages in the code nodes.
  • Ensure smooth data flow through the workflow using the code-based queueing mechanism.

Option 2 (Redis)…

  • Install and configure Redis on my server or guide me through using a managed Redis service.
  • Integrate Redis with n8n, including setting up the necessary nodes and configuring them correctly.
  • Migrate the existing queueing logic to utilize Redis for improved reliability and performance.

I am also open to other suggestions…