External_user_id is null when a workflow is triggered from an external app event

Dev
1

I have created a workflow with an HTTP webhook to mimic the asana-new-task event, so when a new task is created in Asana, the workflow is triggered and additional actions can be performed for that particular external user

I have created the trigger via pd.deployTrigger including the externalUserId. The trigger has been successfully created and I can see it in the list of triggers for that external user via https://api.pipedream.com/v1/connect/{my project}/deployed-triggers

Furthermore, when the user creates a task in Asana, the WF gets triggered and all parameters are passed as expected … but the external_user_id, which comes null in the event.context

Any ideas what I might be missing?

2

I’m actually facing the same issue. I deployed my trigger with externalUserId included, and I can see the trigger correctly listed under that external user. The workflow fires as expected when a new attachment with email is received in my gmail, and the payload parameters are all there but event.context.external_user_id is always coming through as null.

Would be great to know if there’s a step we’re missing, or if this might be a bug.

3

Hi Sheraz,

I got my issue solved a while back. At that time (not sure if things have changed since then) the problem was the the external id was not passed if you were calling the trigger using the webhookUrl. As soon as I started using the workflow_id, it all worked for me

I haven’t used Pipedream in a little while, but I hope this helps,
Miguel