Closed frankgreco closed 2 years ago
What other inputs do you see yourself using apart from Location?
Any that are custom defined. I think giving the ability for the user to use {inputs.<name>}
is flexible. Hard coding what can and can't be used in the event name seems too strict.
I agree with @frankgreco to allow any that are custom defined.
To give an example of my intended use case (which led me here), I am scheduling interviews for clients and I have a custom field Company
. It would be great if I could have the event name be: Interview with {USER} @ {inputs.Company}
(or something similar).
Thanks!
more variables added!
Describe the solution you'd like
Currently,
{USER}
is the only template variable available for usage in the Event Name field.For example, considering a required input of Location, we could have,
Coffee with {USER} at {LOCATION}
.