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

But you’re saying that the trigger successfully deploys and ~emits~ receives events, it just doesn’t actually trigger the workflow?

right there are 2 cases one with the workflow_id , with this the trigger emits events but it do not trigger the workflow.

And in the other case, with webhook_url , the trigger still emit events, it also trigger the workflow, but workflow requires external_user_id , and in the context its always null

Okay got it, thanks. Let me keep digging for a minute.

I see a few dcids in this thread, can you give me one that is failing to trigger the workflow?

sure, here it is Pipedream - Connect APIs, AI, databases and more

Is that supposed to emit to this workflow?

nope this one Pipedream - Connect APIs, AI, databases and more

I see events that triggered that workflow, did those come from the above trigger? (I realize there’s no external_user_id)

Correct, this is the actual problem

Wait, so the trigger is triggering the workflow?

these events are emitted when i deployed the trigger with webhook_url

Hi! were you able to find anything?

Yes, it’s a bug in our SDK :face_palm::skin-tone-2:

Working on addressing it, sorry about that!

Okay, thanks for letting me know.

FYI we’re tracking this bug here: [BUG] workflow_id is missing from supported args for /triggers/deploy endpoints in the OpenAPI spec and Connect SDKs · Issue #18636 · PipedreamHQ/pipedream · GitHub