Creating a resume URL for an approval step in advance?
In our usecase, we need to generate a callback URL, send it to an external service (so that it can use the callback URL as a webhook), and then use it in the approval step so that it waits for the trigger.
My naive assumption was that it's possible to have 2 steps: the first one with a call to getResumeURLS() and then, in the second, pass it to the Approval node.
It turned out, however, that the endpoint path is generated relative to the node and job that call the method.
Is there a way to somehow expose a callback URL for approval, known in advance?
Thanks!
10 Replies
It's not possible currently
is it not possible to do it all in one step?
also you can resume a flow without the resume url if you have sufficient privileges (owner of folder OR admin/superadmin)
You would just need the flow id
Thanks for replying.
So probably we will just slightly customize the Approval node so that it also sends the generated callback URL to the external service.
As for your last point about resuming without a resume URL, can you please elaborate a bit?
To clarify, we send "resume_url" to this external service and then the service should call the URL when it has finished data. processing.
If you can do it in a single step, that's the expected design
Got it, thank you!
Hi Ruben! 🙂
Thanks again for providing us with a license key
We are getting familarized with the EE version
One question though is why we don't have the Non-Prod instance flag in our instance settings
Even though, as you can see in the image, it's already the EE image and I'm a superuser
can you refresh the page just in case
ah you didn't put the license key in the UI
you have to put the license key in the UI to see it
This flag appears if I just start typing anything in that text field
But we applied our license key as a k8s secret via helm
So as not to insert the key in the UI, or should we?
is that important to you to have it as a k8s secret?
That is convenient because that aligns with all other secrets
Is there any issue with that? I mean, is it preferred to set the key in the UI instead?