Why am I encountering an expired token issue when setting up the PipeDream connect following the official documentation?

Bugs
21

Ah… seems you are right! But I remember specifying the environment. Let me check my command again.

Here is command I used to generate:

22 
curl -X POST https://api.pipedream.com/v1/connect/proj_oLsDBz7/tokens \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJFZERTQSJ9.eyJqdGkiOiI3NzEzODYyYi0zY2I1LTQzNTEtOWU3Yy05NDczZTUzMzBlYjEiLCJpc3MiOiJodHRwczovL2FwaS5waXBlZHJlYW0uY29tIiwiZXhwIjoxNzMxNDI3NjM3LCJuYmYiOjE3MzE0MjQwMzcsImlhdCI6MTczMTQyNDAzNywiYXVkIjpbImFwaSIsImNhdGNoZXIiXSwic3ViIjoib19iTEk4YnlLIn0.TcFNCt7VMrQ16cIj3NkaQIiYIOwE4EUZXjfpqKo3kgWy48tK2yXLfQtwxRctenHMLhNAMYQW4t1Rx_aqcMFNBw" \
  -d '{
    "external_user_id": "your-external-user-id",
    "project_environment": "development"
  }'

I do call it explicity here.

23

I have set my project environment to development.

24

And here is the response to that :

{"token":"ctok_dbd980017e89b0643616732424b01294","expires_at":"2024-11-12T19:10:38.442+00:00","connect_link_url":"https://pipedream.com/_static/connect.html?token=ctok_dbd980017e89b0643616732424b01294\u0026connectLink=true"}(venv

When I open that, in my browser. It says expired.

25

“project_environment”: “development”
is this not enough when I do the curl request to set the project environment? Maybe I am missing something.

26

I’ll be able to troubleshoot further when I’m at my computer, will let you know asap

27

can you try passing the param as environment_name instead of project_environment?

28

Thanks. Appreciate it. If you need any other info, let me know.

29

that works!!!

30

Thank you.

31

glad to hear, sorry about that, we recently changed the param name so need to clean that up everywhere

32

Nice, thanks Dylan. Sorry for the trouble, Adithyan!

33

Coolio. No worries. It was frustating few hours. But appreciate the quick response once I posted it.

34

Maybe a naive question, but since we are here… would appreicate your response…

Basically, I want to send this connect URL to my clients and then use it in my Pipedream workflows (So that they can login to their accounts).

For now, I just want to stick with the Pipedream OAuth clients to avoid any other setup. Is there any disadvantage to directly doing this within the development envionrment and then using this in my workflows?

Is there any need to go to production if I only stick with Pipedream’s OAuth clients within the Pipedream workflow.

35

It is for podcasters - posting youtube videos. So I am going to use the youtube_data_api app.

36

I think there might be a slight misunderstanding of the core functionality for Connect — in that example, are you envisioning being able to select your clients’ connected accounts from the builder directly, when you go to configure the YouTube step for example? Or will you be triggering these workflows programmatically from your application and passing in their respective user IDs at runtime?

37

Or will you be triggering these workflows programmatically from your application and passing in their respective user IDs at runtime?
This.

38

I want to send them a link once where they can connect their YouTube account (like I can do to my personal account right now).

39

And then I will store this.

40

And programatically post on their behalf.