I want to update variables in a specific Google Slide page and am having some issues.
Since I need to update a Slides file specific to the workflow, I want to pass in the link to that Slides file as an input.
Whenever i try and do this the node returns an error, but it works fine if i use the exact same link directly in the ‘link’ field (I did this as a test) - you can see it here.
Hey @samhbarton! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @samhbarton – Thanks for sharing this. I can see how this can be confusing. The way the ‘Link’ option works in the ‘Google Slides Writer’ is similar to how Google Sheet nodes function. The node requires you to select a file or manually add a link first so it can read its schema and output the available variables.
When you pass a link dynamically, the link or file isn’t “read” beforehand, so the node isn’t able to output the variables. For dynamic input, you need to define the link in the node manually first, and then you can pass the link dynamically.
The limitation here is that you can’t pass dynamic links where the variables in the slides are different, since for any new file you’d have to add it manually first. At the moment, this is a limitation of the node based on how it works.
OK thanks for the update @Wasay-Gumloop . So i guess at the moment there’s no way to accept a dynamic link where the variables are always the same across files?
So the file will be different each run, but the variables are identical each time
Actually its the opposite - You can pass in a dynamic file link as long as the variables stay the same on each file, if that changes then that would break the schema.
So what I did was manually add a link and then specify the variables used and then remove the link and tried to dynamically pass the link in. And it wouldn’t let me put the link in.
Appreciate the access and the video @samhbarton – Currently, I’m only seeing {{stratobservations) not appearing on the node. This is because its missing the two curly brackets at the end, it should be {{stratobservations}} – let me know if that works and if there’s another variable I missed.
Valid placeholders can contain letters, numbers, underscores, spaces, dots, and hyphens (e.g., {{first_name}}, {{company.name}}, {{sales-report}}, {{Total Amount}}). They must not include forward slashes (/), square brackets (), or colons (:). If you want to keep the literal text, escape it with a leading backslash, e.g. {{not a placeholder}}.
Hey @samhbarton – Sorry for the slow response here. This is happening because of the & sign in the variable name. I can check if that is expected behavior and if you do need to include that in the variable name we can add support for it.
In the meantime, removing that should resolve the issue:
