Hi all,
Can you pass action dynamics fields to custom api webhook call
For example https://HIDDEN.atlassian.net/rest/api/3/issue/{{action6.Response.key}}/transitions
Is this a valid use of dynamic fields?
🗨 Link to Slack thread
Hi all,
Can you pass action dynamics fields to custom api webhook call
For example https://HIDDEN.atlassian.net/rest/api/3/issue/{{action6.Response.key}}/transitions
Is this a valid use of dynamic fields?
I don’t think I understand the question
Hey JB, Oh sorry, I mean build custom integration webhook, specifically the destination URL using dynamic field that comes from a workflow action.
In this case, try to call an transition on a ticket, the webhook will look like this:
https://.../rest/api/3/issue/*<ticket-number>*/transition.
I create my custom integration with the payload and everything works, the problem is that the ticket number changes every time the workflow runs.
So I wanted to see if I can pass the ticket number that I got as response for Action #1
to the webhook URL on Action#2
We manage to solve this with help of the BC team. The secret sauce was you can call out the {{payload.<field>}} on the webhook URL and that "field" can be in your playload.
For example:
Webhook URL: https://api.com/v2/{{payload.servicedeskticket}}/transitions
Payload:
{"servicedeskticket":"SD-1234"}
and the url will change to
Thanks again guys!
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.