Maybe this gives you a lead to the solution.
I do not any longer use OmniFocus actively (I am on Things now)
But I clearly remember, that the naming in OmniFocus had some quirks for me.
I found that post with the following excerpt, following this the target parameter should start with /task and not with /folder.
Paste has a few extra parameters that can direct the data to a specific spot:
target (can be inbox or projects for top-level items; use target=/task/task-id (for a specific action), target=/task/project-name (for a specific project), or target=/folder/folder-name (for a specific folder))
index (positive integers count forward from beginning, while negative numbers count back from the end of list)
content (TaskPaper string, the content to paste; without this parameter, OmniFocus captures text from the system clipboard)
If simply activating omnifocus:///paste without any of the above, the clipboard will be parsed and added to your Inbox.
Thanks. I copiedit from above an did not check it for validity.
One option to get a specific place in omnifocus is to press them share button and use the generated url. But the project name will be an id like:
omnifocus:///task/m5Cb2dBpxQF,pzJId3i8Jm1,k3AIKQqfzUa,o2OHS4y_qAT,dPo3VCL4MKy
So is it your data, or is it your action that is to blame?
Try removing the target part of the URL and see if you can create a task.
If the task is created, you know it is the target that is wrong. Probably some misspelling, or using the wrong character case, of your path is wrong (e.g. do you have a top level called ‘task’ in which ‘Home’ sits?)
If it fails, then that would suggest that there is something in your data that the URL execution is balking at. I would check that you have enabled the option to URL encode tags in the action step, and if you have, perhaps post some example of failing content and a link to your action (you can share it without making it public on the action directory); then we can analyse what is actually going on.
that is strange. OmniFocus documentation (see the quote in my post) says that it should be prefixed with /task and /project
but @sylumer has a working omnifocus so I think the blog quote my pe misleading.
@zeltak have you posted a question on the Omnifocus Community or to Omnifocus themselves. the price of the app should give them time to a better documentation as I found on the web.
as opposed to just quietly send it to the actual folder in the background
now im really confused …
i did that (omnifocus://x-callback-url/add?name=[[title]]¬e=[[body]]) but then issuing the action just pops up an empty Omnifocus window with non of the draft actual text
Presumably because you don’t have those projects and I do. I wouldn’t expect it to work for you as is. It was just to show you the structure was the same and that it worked.
If you want to save it automatically, add the auto save parameter as true to the end of your URL.
&autosave=true
It is never going to do it quietly in the background. That isn’t how URL schemes work, That’s why to do stuff in the background, developers have to develop special actions for Shortcuts to use where it does not end up having to jump back to the app to execute.
Because it is an x-callback-url call though, you should just get app switching and end up back where you started, in Drafts.