Telegram Button Inline Wait and Two different paths workflow connect in the same IF

[Felipe_Marques]

Hi Guys,

I Have two questions here:

1. Is there a better solution for getting information from a node in a workflow into another workflow? In the first workflow, I’m collecting files and making a user decision via an inline button, but there’s no waiting to capture this decision, so I need to create another workflow to capture this trigger. So I saved some information from the first workflow in FireStorage to capture in the second workflow, but I didn’t find it very elegant and efficient. Have you ever experienced this?

2. In the second workflow I have two options for calling Open Ai. The options are branched in the flow through the first if, but regardless of the result of one of the two paths, the subsequent flow is the same. However, when I connect the two outputs in the second if, it creates a dependency on having both results and does not continue. What should I do to make it continue with only one of the outputs?

Please share your workflow

[Ventsislav_Minev]

Hey @Felipe_Marques,

For 1 you can wait with the Send and wait for Response option

For Telegram you can choose different confirmation options and wait times.
From what I read it is supposed to pause the workflow and resume in on response in a resource efficient way.

Screenshots

For 2. You can either duplicate all the nodes after your AI Agents OR
you can call the rest of the logic after your AI agents as a sub-workflow

[Felipe_Marques]

Hi Ventsislav_Minev,

Thank you for the tips, they were valuable to me and expanded me possibilities in the future. Regarding the option of Telegram to wait for a response, it is really very interesting but it leaves the chat flow for a webapp, it is a good option, but I see that it would be better within the Telegram journey, I searched a little more on how to do this on the internet and found a cool solution, let me share it with you:

First, it is important to say that you cannot have two Telegram trigger nodes, the Telegram API has a limitation for this, so we need to keep only one and use a switch to understand what was captured by Telegram: a message or callback (for example) and after that follow a route and to get data from another route you can store outputs from it in a bank and retrieve them in the other route with some common index (in my case the Telegram chat_id), I think it is also possible to save it in memory, but since I need to have some data stored in the bank, I preferred to continue like this (although I think it is not so elegant).