Jump to content


  • Content Count

  • Joined

  • Last visited

  1. When an object in a workflow outputs valid configuration JSON, this will be applied similarly to the JSON Config object in the workflow editor. Unfortunately, this seems to apply to all objects, including keyword inputs and the like, meaning that if valid configuration JSON is typed into any workflow keyword input, the workflow will not work as expected. This can be easily reproduced by creating a workflow similar to the one shown below and typing the following text into Alfred: To break the intended functionality: test { "alfredworkflow" : {} } To actually manipulate the work
  2. This is pretty self-explanatory. My suggestion is that a new trigger object is added for workflows which triggers at the specified time, perhaps with a day/date component as well, and passes the date through to the workflow.
  3. Since updating to v3.0.1 [671], whenever I use the eject keyword, one of the options that displays is "Macintosh HD". If I attempt to eject it, it displays this error message: This is reproducible on both of my computers (running 10.11.4 and 10.11.5).
  • Create New...