{'os': [{'ts': 1745001736662, 'k': 'error', 'err': {'name': 'TypeError', 'message': "Cannot read properties of undefined (reading 'oauth_access_token')", 'stack': "TypeError: Cannot read properties of undefined (reading 'oauth_access_token')\n at Object.drive (file:///tmp/__pdg__/dist/code/e4207de98c73060cf90653524592081661abecd9e78d47c101ab55bdc7e8c265/node_modules/.pnpm/@pipedream+google_drive@0.9.1/node_modules/@pipedream/google_drive/google_drive.app.mjs:299:34)\n at Object.getFile (file:///tmp/__pdg__/dist/code/e4207de98c73060cf90653524592081661abecd9e78d47c101ab55bdc7e8c265/node_modules/.pnpm/@pipedream+google_drive@0.9.1/node_modules/@pipedream/google_drive/google_drive.app.mjs:809:26)\n at Object.run (file:///tmp/__pdg__/dist/code/e4207de98c73060cf90653524592081661abecd9e78d47c101ab55bdc7e8c265/code/actions/add-single-row/add-single-row.mjs:131:57)\n at file:///var/task/component_maker.mjs:151:42\n at captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:11)\n at run (file:///var/task/component_maker.mjs:141:26)\n at MessagePort.<anonymous> (file:///var/task/component_maker.mjs:177:15)"}}]}
Can you try passing the authProvisionId under googleSheets instead of snake case? You always want to use the app prop name that’s returned in the component definition.
in this case is the file in the /tmp/ directory accessible in any way from pipedream or is it still sitting on the E2B side?
Yea, /tmp is accessible to other actions within Pipedream’s execution environment — would you want access to it outside of action executions? We’re chatting about some related features here, so would love to know about your use case for working w/ local files via the Connect API.
I also was wondering if we can make custom actions for an app and make it available to the connect api?
Not currently, but we’ve talked about this in the past — would these be totally bespoke actions that you wouldn’t want to publish to the Pipedream public registry? Or do you just want the flexibility of not being constrained by what we have available? Or something else?
Yea, /tmp is accessible to other actions within Pipedream’s execution environment — would you want access to it outside of action executions? We’re chatting about some related features here, so would love to know about your use case for working w/ local files via the Connect API.
Yes, i would prefer a way to access the files, either downloading it to somewhere or ideally, have it available as a public accessible URL
Not currently, but we’ve talked about this in the past — would these be totally bespoke actions that you wouldn’t want to publish to the Pipedream public registry? Or do you just want the flexibility of not being constrained by what we have available? Or something else?
I think it would be the latter (having flexibility). I have some semrush integrations that I want to expose to my end users via the connect api and i saw that pipedream have a semrush auth set up but do not have components available so if we can do that, that would be great
FYI we were just discussing this work today and we have a proposal that I’d love your feedback on — we’re thinking about adding an arg to the runAction method, something like saveToPdFileStore (or something better named than that), which would essentially sync the /tmp in that external user’s execution environment with the File Store within your Pipedream project.
• So when you pass true for that new arg, we’d save any files that are saved to /tmp to your project’s File Store and return a presigned URL in the response (maybe as a new element in the exports array).
• Does that generally sound like it’d work for you? So for any triggers or actions that return a reference to an ID, I believe we typically have corresponding actions to download those files (and if we’re missing any we’ll add them).