It is because you are using connect, which you need to follow connect flow
I created the workflow with an http trigger and I tried to deploy the gmail trigger using the connect SDK, it got me the response ‘Unauthorized’
Do you mind not sending the message to the channel as well as the thread every time to reply? It’s just spamming the channel and makes it more difficult to keep the channel focused.
Sure
the Playground should have the end to end working code that you can reference (image below)
Pipedream Connect document should also contains all of the answer you need.
Could you follow them through first?
I was able to connect it for the end users, thank you for helping me. @U02A06JPKEH
In development environment, are there any limitations for testing with other accounts, other than the one used in creating the workflow
There’s no limitation for testing with other accounts for development environment. You can use all feature similarly to prod.
During OAuth, do we get the account details of the connected account as a call back, or is it necessary to call the ‘https://api.pipedream.com/v1/connect/{project_id}/accounts’ this route .
I also had another doubt, do we have reference header in gmail send email action