How Can I Correctly Propagate External User IDs in Pipedream Connect Workflow's Event.Context?

Help
41

what do you think is the possible cause?

42

Can you look for the webhook linked with the trigger?

43

Not sure

44
45

Check out the logs tab too

46

I’m already on it but nothing to see

47

Yeah exactly weird it seems like it’s not even running

48

Is the external user ID account yours?

49

Can you create a normal trigger (without connect)?

50

yes

51

Nice, please do that and let me know the source ID

52

you mean in pipedream UI?

53

Yep

54
55

Oh that one has events

56

Hmm

57

What is the full payload you’re sending to the Connect API / SDK?

58

Without sensitive info

59 
    const response = await [axios.post](http://axios.post)(`https://api.pipedream.com/v1/connect/${process.env.PIPEDREAM_PROJECT_ID}/triggers/deploy`, {
      id: componentId,
      "external_user_id": userId,
      "configured_props": configuredProps,
      "workflow_id ": workflow.workflow_id
    },
      {
        headers: {
          Authorization: `Bearer ${accessToken}`,
          "x-pd-environment": process.env.PIPEDREAM_PROJECT_ENVIRONMENT,
          "x-pd-external-user-id": userId,
          "Content-Type": "application/json"
        },
      }
    )
60

i think there is some issue with trigger’s deployment because the one we deployed earlier is not listed here

image.png
image.png1685×304 28.8 KB