Jump to content

Problem when using "call external trigger" in Direct mode when multiple trigger keywords defined e.g. `foo||bar` and Inbound mode==Keyword


Recommended Posts

Let me know if this isn't clear, and I can upload a test workflow

 

But, if you have let's say a Script filter, with trigger keyword foo||bar and then you define its inbound configuration mode to be "Keyword", when calling that function using Call External Trigger, the input will be populated with the literal text `foo||bar` which naturally does not work. It should ideally reuse the trigger word that originally started the workflow. If that's not possible, then at least just the first keyword should be chosen, rather than the literal a||b.

 

image.png.b77b9ade6817dc030e1c9cd326a18304.png

 

image.png.8595b5f5a56a418c22cd3023d9174cd8.png

 

image.thumb.png.0b8bb86651043e2223c64915a4013bd0.png

Link to comment

Reusing the original keyword isn’t really feasible because there might not be one. After all, that is called like an External Trigger so the call can come from anywhere, even from inside the house; er, I mean, from outside of Alfred. But the point is certainly valid and stripping to the first keyword makes sense. Good catch. Tracking this internally.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...