What is your goal?
I need to give people a 2. chance to upload a better image via unique link sent by email. (eg. time limited or hidden fields in Tally form)
What is the problem?
Tried to fix the “retry upload” with a “retry scenario” with “retry form” in Tally and a HTTP module. (intended to handle the new upload and via custom webhook return to my primary scenario for processing) Now ChatGPT tells me that only one “input” is allowed per scenario and
What have you tried so far?
Gemini, Copilot and GPT pulled me through 3 days of ‘dead end plans’: Tools, Get a record/delete a record, Data store, keys. Token in hidden Tally fields.
Screenshots: scenario setup, module configuration, errors
Scenarios in make can have only 1 trigger. However if you do 3 scenarios:
-1 main scenario that starts with a webhook
-2 secondary scenarios that are your triggers:
*First one with tally form, and sends the information to the main scenario with a HTTP POST to the webhook
*Second one with the other tool and also send the information to the main scenario with another HTTP POST
1 Like
Hah old school Make tricks 
I still catch my self using an HTTP module to call a webhook instead of the new Call a Scenario modules.
4 Likes
Don’t be afraid to build a deeply layered orchestration of scenario’s. It is a common pattern in developing to adhere to the DRY principle.
As Stoyan said, there is a Call a Scenario module nowadays, which wasn’t there until not long ago. Then we had to use the HTTP/webhook method of calling subscenario’s.. 
I advice to use the call a scenario method now, this makes logging and troubleshooting so much easier.
Cheers,
Henk
4 Likes
Thanks for your replies
I get the idea with a webhook as a multi input handler, good suggestion 
I am going to read up on the “call scenario” function to start with.
Thanks guys
Martin
3 Likes
