Yes, @gillenb. If you have this email parameter in your action, you can route this parameter to...

  • 1 July 2020
  • 9 replies
  • 13 views

Badge +1

Yes, @gillenb. If you have this email parameter in your action, you can route this parameter to the url by using {{payload.user_email}} you are sending in the webhook like this: https://screenshots.bettercloud.com/o0uvXmZl. So when you save this action and use it in workflows, the user_email value you pass in that field should be appended to the when the action is executed.



🗨 Link to Slack thread

9 replies

Badge +1

Ah gotcha. What’s the instance ID on that workflow? Feel free to shoot me a slack DM

Badge +1

Should mean that the workflow succeeded, meaning all the actions associated with it passed. For the third party API, I would assume that means returning a 200. Can you tell if the action was successful? If that’s the case there could just be an issue with those dynamic fields being passed in the workflow results email.

Badge +1

Yes, you can use that in the url to do that manipulation of the input!

Badge +1

Amazing! Thanks @justin.little. I’m gonna try that out now

Badge +1

Gotcha. Unfortunately I don’t have logs on the other side. The action was to query for those fields, so I can’t really tell what’s going on in this case

Badge +1

Oh thats 💰 Thanks! So the “input” field of the custom workflow action will be the user email from the when event. And then I can reference that value in the custom integration via {{payload.user_email}}

Badge +1

So this is odd. I get a SUCCESS message on the workflow, but all the return values are blank in the email report:

Badge +1

Thanks will do!

Badge +1

What does the “SUCCESS” message mean? Is that a 200 response from the 3rd party API?

Reply