Hey @CCM,
Just a slight syntax error, you need to use startTrigger.data
Hey @CCM,
Just a slight syntax error, you need to use startTrigger.data
Thanks man return startTrigger.data
also is null. Confused why I can see the events object in my run history under Workflow Trigger ID, but not in the startTrigger data!?
Try selecting startTrigger in one of your runs, and then the JSON data, you'll see how you can make reference to it, it actually may be startTrigger.event,
or startTrigger.value
?
Hey @CCM,
This actually may be a bug though, see this thread for updates startTrigger test parameters suddenly not working - #18 by Francisco_dos_Santos
startTrigger is still not working when the workflow is scheduled. We're having to create daily webhooks to run our workflows. Is Retool going to fix this issue?
Hey everyone. We're working on reinstating this for now. In the medium term, we plan to introduce parameterized schedules. As part of that migration, the default parameters for every schedule will be set to the test JSON. Thank you for your patience!
Thanks for the update @AbbeyHernandez!
Our workflows with startTrigger data are back up and running as of 7:00 CST last night!
This has been fixed! Let me know if you all start seeing the issue again