Hi,
i tried to use a variable for the request path in the http request trigger but this seems not to work. Would it be possible in a future version?
Thanks
Sascha
Use of variables on http request trigger
Moderator: Martin
Re: Use of variables on http request trigger
Hi,
The action HTTP Request should already support variables in the path field.
A variable should also be highlighted in blue in the URL field. Something like this should work:
http://host/xyz{triggertime,dateformat,yyyyMMdd}
Regards,
Martin
The action HTTP Request should already support variables in the path field.
A variable should also be highlighted in blue in the URL field. Something like this should work:
http://host/xyz{triggertime,dateformat,yyyyMMdd}
Regards,
Martin
Re: Use of variables on http request trigger
Yes but i want to use variables in the request trigger but in the action
Re: Use of variables on http request trigger
Ahh, you really mean the trigger
Supporting variables in triggers is usually quite complicated (or impossible in some cases) but it should be possible to add variable support in this particular case.
How would you want to use the variable exactly? Can you give an example flow or a use case so I better understand your requirements?
Supporting variables in triggers is usually quite complicated (or impossible in some cases) but it should be possible to add variable support in this particular case.
How would you want to use the variable exactly? Can you give an example flow or a use case so I better understand your requirements?
Re: Use of variables on http request trigger
Hi. I have two flows with a http request trigger listening on the same sub path /am/Spotify and a third flow doing some httpmanipulation by rewriting links using the same path. I want to make this more comfortable by adding the path as variable and use this instead of some kind of "hard coding".