This topic was automatically generated from Slack. You can find the original thread here.
team, help me out pls…
at the time of creating webhook trigger with custom response, it provides one https url which is going to be used to trigger the workflow.
my question is- Is their any way we can have api key, dataset key of the created url, which will make the particular url more secure, so that just one url must not enough to trigger the workflow. added snapshot below for webhook API
Hi , the closest thing I can think of is applying Filters to stop your workflow early when the request does not have the information you required (.e.g. the header Authorization does not have the value you required).
On another note, it would be great if you could create a ticket, stating your specific suggestion
Thanks I have added Authorization in header, api_key(randomly generated),dataset_key(randomly generated) and written 3 steps in workflow for checking one by one.(optimise- all can be clubbed in 1 step using customised code step)
3 major problem here
i) eating up time of the workflow
ii) In Filter, it stops the execution with
"$.respond() not called for invocation" ---> there has to be a way to customise the response if filter steps doesn't get executed.
iii) sharing webhook endpoint would be difficult