Email capture: OmniFocus 2 PRO with outlook 2016

Automation OmniFocus Automation
#1

Hello, i have OF2 PRO and Outlook 2016, how can i put an email in the OF2 inbox!? pls help!

#2

Hi,

You can use the mail drop: You can find your unique email address here: https://manage.sync.omnigroup.com.

2 Likes
#3

Ok, that works but im looking something different, like an script, or something where i can drop the email to OF2, or just “mark” the email to convert it to a OF2 task.

#4

There are a couple of scripts out there. You just need to google Outlook to Omnifocus 2.

http://www.carlbruiners.com/2015/04/omnifocus-2-and-outlook-applescript/

http://veritrope.com/code/outlook-2011-to-omnifocus/

Most of them start with 2011. The big issue is that the latest release of outlook removed the script window so you’ll need to use something like FastScripts to trigger the script.

#5

Has there been any new developments with this? I tried a couple of these scripts with Outlook 2016 and they don’t seem to work. Anyone else find another strategy/tool?

#7

I haven’t seen anything. I use maildrop if anything. I wish Omnifocus had some better integrations.

#8

I’m pretty sure my Outlook => OmniFocus AppleScript still works; The only caveat is that, since Microsoft removed Outlook’s dedicated AppleScript menu, you’ll need to trigger it via the System AppleScript menu or a third-part “launcher” app (like FastScripts, Alfred, etc.)

One example: My pal Sven at Simplicity Bliss rolled his own Alfred workflow, which he reports is working fine. :-)

I’ll update my script’s page when time allows to reflect the 2016 reality of scripting with Office.

Warmest Wishes,
Justin

1 Like
#9

+1 for the Alfred workflow. It works nicely.

#10

Hi Justin, I just “upgraded” to Outlook 16.6 (the High Sierra version) and the script stopped working. Actually, it works 1-2 times, then does do anything unless you reboot the computer. Your script is the heart of my business workflow, I hope you can find an easy fix!

#11

@sbennett3705 - I noticed that it stopped working as well with the recent update to Outlook 2016 as well. I’m digging through the script to see what I can find so it will be a race between Justin or myself to get it updated.
;-)

#12

Microsoft suport is also looking into this. It appears Outlook 16 breaks all script, even the old ones supplied with Outlook 2011. In the meantime, I downgraded to 15.33 and am out of the Insider program.

I would guess it’s a matter of time before MS walks away from scripting, Apple is already doing so. It seems the preferred approach is an Office 365 plug in (like Evernote uses).

Thanks for any and all help!

#13

I wish Omni would write a proper Outlook add-in.

3 Likes
#14

So maybe I’m bagging my head against an immovable wall if the fault is in the app and not in the script itself.

#15

Hey OmniPeeps — I’m not going to be able to test this until I can update my system to the broken version (which is going to be a bit as I’m in the middle of a few projects), but maybe someone could try making the code adjustment below and report back here with results.

Change:

set theProps to (properties of selectedItem)

to:

try
        set theProps to (properties of selectedItem)
on error
        set theProps to selectedItem
end try

In terms of AppleScript in Office products, a member of their team told me a long time ago that they’re backing away from supporting it… getting rid of the menu bar was, in my view, the first step. I’d certainly love if they’d reconsider and, if you feel the same, I think you should bug them about it. :-D

1 Like
#16

Thanks for the heads up on some of the changes. If MS is slowly backing away from Applescript, hopefully there’s another avenue coming with JXA or an Outlook plugin from Omni ( hint, hint ;-) )

#17

@Veritrope I tried your suggested fix with the latest Outlook (macOS) 15.38 and it works like a charm. Much appreciated!

1 Like
#19

Microsoft support acknowledged the fact that scripts were not running under Outlook 16, the tech said they reported it as a “bug”. Let’s hope they actually follow up.

#20

Thank you so much. I replaced the line with the try-statement, and it works. High Sierra, OmniFocus 2 Pro, Outlook 2016. I also use Sven Fechners Alfred-workflow to activate the script: https://simplicitybliss.com/outlook2016-to-omnifocus-e7dd369080d9 (and actually use Keyboard Maestro to activate the workflow and change to OmniFocus and enter a : to the end of the newly added inbox item, since I like to have : to indicate there is something in the note field.

Before this modification that Veritrope/Justin posted, the script didn´t work. Now it works for me and I am productiva again. Thanks Justin!

1 Like
#21

OK—I’ve updated the code on the script’s page and just sent out a tweet for more testers. Hopefully, everyone else has the same positive experience as @svendah and @patrickkamin! :-P

#22

Just an FYI - The script I have working still has the set theProps function to the original one line @Veritrope described above. I think the change made in @Veritrope script from referring to Outlook as application "Microsoft Outlook" to application id "com.microsoft.Outlook" was what fixed it for me.

Thanks again for keeping this script up to date @Veritrope!