I’ve tried using a Run Code node and that didn’t work. Gummie suggested that to handle credentials properly I should use a custom node, so I have switched to that.
Unfortunately, the code is:
a) not renaming the file
b) returning the file ID despite the Output on the custom node being set to statusMessage (text).
Hey @AangelHD! 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.
We’ve limited support at the moment for troubleshooting custom nodes since they’re fully personalized to each user—but I can definitely point you in the right direction.
Two key things to keep in mind:
I’d recommend using the AI built into the custom node builder or your preferred AI model to generate the code, instead of using Gummie. Gummie is specifically designed for workflow help (we’re expanding that soon), so you might run into odd cases like it trying to import gumloop—which isn’t a real module and isn’t needed here.
Custom nodes don’t have access to our OAuth credentials. You’ll need to include your API key directly in the code. Since custom nodes are private to the owner, your keys will remain secure.
That said, Google Drive’s API does require OAuth 2.0 for operations that:
Access user-specific data
Modify resources (like files or folders)
Create or delete resources
Because of that, this kind of integration may be out of scope for a custom node at the moment—you can’t establish an OAuth connection there just yet. But I can definitely add renaming of drive files to our roadmap.
Sorry, I’m calling the code generator Gummie here. It was the code generator in the custom node that gave me the code that is attempting to obtain credentials from the gumloop object.
The problem with the code generator is that it’s not iterative…it seems to start from scratch every time one types into the prompt box.
Regarding putting keys in the code, I’ll try that.
It might still make sense to add environment secrets that are referenced via {{ var }} to the system. That way all the keys are in the same place and are protected from view within the code.
