Notifications
Clear all
Topic starter
telegram21-bot-blueprint.json (796.8 KB)
Hi there,
I’m encountering a challenge and feel I lack the necessary knowledge and skills to proceed. Any assistance would be greatly appreciated.
My objective is to develop a Telegram chatbot for a "marathon" event. The workflow is as follows: users initiate a chat with the bot (/start), subscribe, and then the bot sends daily objectives and images over a specified number of days, collecting user responses.
I have successfully built the automation up to the point where the bot is ready to send objectives. However, I'm struggling with how to transition from collecting user information (like IDs and names) to a prepared table containing tasks and images.
Posted : 30/01/2024 5:49 am
Perhaps this needs to be accomplished in a separate scenario?
Posted : 31/01/2024 7:25 pm
While it's theoretically possible to implement this in callin.io, a complex setup like this might become costly due to the number of operations per scenario. This limitation might hinder scaling for numerous users interacting with the bot concurrently. I'd suggest considering a service like https://buildship.com .
Detailed Explanation:
Disclaimer: This is a simplified estimation. You may require additional modules for tasks such as downloading/sharing/converting/processing images and files, parsing/converting text and responses (instead of saving raw values), and integrating with external services not depicted here.
-
You would require a minimum of four scenarios.
-
Each time you "wait" for a response, a new scenario is necessary to initiate with a Webhook trigger.
-
Operation calculation per user:
4 + 6 + (7 x 21) = approximately 157 -
If you are on a paid plan with 10,000 operations per month, this complex setup would only support around 60 users without purchasing additional operations. This also assumes you have no other scenarios running and considers the disclaimer.
-
Typically, when setting up a complex scenario like this, the goal is long-term automation designed to run indefinitely. Therefore, you should anticipate potential edge cases that might necessitate additional modules.
Disclaimer: This is a simplified estimation. You may require additional modules for tasks such as downloading/sharing/converting/processing images and files, parsing/converting text and responses (instead of saving raw values), and integrating with external services not depicted here.
Edit: You might need an extra module per scenario if you intend to "respond" to the user confirming their input has been recorded. Consider how adding just one module impacts the operation count calculation:
5 + 6 + (9 x 21) = approximately 200
This would support approximately 50 users.
Posted : 01/02/2024 2:02 am