Connecting Telegram Photo Replies to Original ClickUp Task ID for Processing (Logical Issue)

I'm developing a workflow to connect ClickUp tasks with Telegram and would appreciate some expert input, as I've encountered a challenge despite reviewing the documentation and available templates.

System: callin.io cloud version

My Objective: The goal is to have a Telegram bot, operating within a specific message thread (topic) in my supergroup, perform the following actions:

1. Alert users about new or overdue tasks from ClickUp.
2. Enable users to mark tasks as “Complete” directly from Telegram.
3. Allow users to mark tasks as “Complete with Photo,” which requires them to send a photo to be attached to the ClickUp task before it's marked complete, without using an upload web form.

Progress So Far:

• Successfully retrieving tasks from ClickUp.

• Sending Telegram messages to the correct thread with task details and two inline buttons:

  • “Ready”: This button functions correctly, triggering a branch that updates the ClickUp task status to “Complete.”
  • “Photo”: This button is intended to start the photo attachment process.

The Hurdle: Linking the Photo Reply to the Correct task_id This is where I'm facing difficulties. When the “Photo” button is pressed:

1. The bot currently sends a follow-up message prompting the user to send a photo (e.g., “Please send the photo in reply to this message”).
2. The user then sends a photo in a new message, replying to the bot’s prompt.
3. My workflow receives this new message containing the photo. I can extract the photo, and I can upload a photo to ClickUp if I hardcode the task_id in the HTTP request node using the ClickUp API.

The fundamental issue is: how can I dynamically determine which task_id the incoming photo message corresponds to? The photo message from the user does not include the original task_id or the callback_data from the “Photo” button they initially interacted with. It appears I'm missing a logical step here due to my limited coding knowledge and understanding of callin.io's capabilities.

If you examine my workflow, you'll notice an Airtable experiment that didn't work out; I guess I'm truly a no-coder.

My Questions for the Community:

• Is the Airtable approach (using the bot’s PhotoRequestMessageID as a key linked to reply_to_message.message_id from the user’s photo) a sound and reliable method for managing state within callin.io cloud?

• Are there any more straightforward, “callin.io-native” methods (for the cloud version, without relying on Airtable) to achieve this temporary state linking between the button press and the subsequent photo message from the user?
  *Is it feasible to integrate an AI agent node for managing and routing task IDs without conflicts when multiple users simultaneously click the “Complete with Photo” button?

• Does anyone have an example workflow or an alternative logical strategy for this common pattern of a bot requesting input, and the user providing it in a new message, specifically for associating it back to an original item ID?

I aim to ensure this process is robust, especially when multiple users might be interacting with the bot for different tasks concurrently.

Thanks in advance for any guidance or suggestions!

Due to character limitations, my code is available on Pastebin (FULL VERSION):
https://pastebin.com/ZUeN4sBK