- Home
- Resources
- Integrations
- OmniFocus
OmniFocus Zapier integrationAutomate OmniFocus with Zapier.
The OmniFocus Zapier integration gives you 0 triggers, 1 action and 0 searches: Create Task, which drops a new task into your OmniFocus Inbox. Every automation therefore starts in another app, and OmniFocus is only ever on the receiving end.
Verified Trustpilot reviews · AI, automation & growth agency
What the OmniFocus Zapier integration actually does
It is a one-way link into OmniFocus, the task manager for Mac, iPad and iPhone. Zapier, the automation service, watches another app you already use, and each time the event you picked shows up there, it writes a new task into your OmniFocus Inbox. Nothing flows back: Zapier cannot read, update or tick off a task once it exists.
Three things people get out of it, all built on the single Create Task action.
An inbox fed by your email. A message you star becomes a task titled with its subject, so the follow-up waits in OmniFocus instead of in a pile of unread threads.
Form replies turned into to-dos. A contact request or a survey answer lands as a task to process, with the person's name in the title, through the same Create Task step.
Meeting decisions captured once. A new row in the shared sheet where your team logs decisions becomes a Create Task run, and the decision sits in your own list.
What Zapier does not do here: nothing can start from OmniFocus, no existing task can be looked up, and every task lands in the Inbox. Filing it into the right project stays a job you do in OmniFocus (which is honestly where you would want to do it anyway).
If you are weighing other tools for the same job, the comparisons live at Make vs Zapier and n8n vs Zapier.
The Zapier words you need, in plain English
Eight words cover everything on this page. Each one is used afterwards exactly as defined here.
- Zap
- The automation you build in Zapier: one trigger that starts it, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. OmniFocus offers none on Zapier, so the trigger always comes from another app you connect.
- Action
- What the Zap does once it has started. Here the only one on offer is Create Task, which writes a task into OmniFocus for you.
- Task
- The unit Zapier bills: one action completed successfully. The monthly allowance on your plan is a count of those, nothing else.
- Polling vs instant
- Polling: Zapier checks the source app on a timer for new items. Instant: the app tells Zapier itself when the event happens, no waiting.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise. It needs a paid plan.
- Connection
- Your account of an app, linked to Zapier once and then reused by every step that uses that app, in every Zap you build.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then requires a paid plan.
What sending tasks to OmniFocus really costs
The trigger never costs anything, and neither does Zapier checking the source app for new items. What gets counted is each Create Task that goes through: one task created in OmniFocus, one task off your plan.
- Billed per run1 task for each Create Task that succeeds
- Free plan100 tasks a month, two-step Zaps only
- Reserved for paid plansNo, OmniFocus works on Free
- Integration version readOmniFocusCLIAPI@1.0.1, October 2026
A run where the OmniFocus step fails is not counted. OmniFocus is not reserved for paid plans, so it works on Free: 100 tasks a month, unlimited Zaps, and a check every 15 minutes on polling triggers. The catch is that Free stops at two steps, one trigger and one action. Add a filter and the Zap becomes multi-step, which needs a paid plan. On a paid plan, a polling trigger also checks more often, as the grid below shows.
Connect OmniFocus to Zapier in three steps
- 01
Open the connection dialog
In your Zapier account, go to the Apps page and click + Add connection. You need an OmniFocus account beforehand: Zapier links to an existing one, it does not create it for you.
- 02
Find OmniFocus and confirm
Type OmniFocus in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens on the OmniFocus side so you can sign in there.
- 03
Sign in and grant access
Log in to your OmniFocus account in that tab and grant Zapier access to it. The connection then sits on your Apps page, and every Zap that writes to OmniFocus reuses it without asking again.
Your first Zap: starred emails into the OmniFocus Inbox
GoalEvery email you star in Gmail becomes an OmniFocus task, but only when it comes from a client.
- 01
Pick the app that starts it
Start building the Zap with Gmail as the starting app and the starred-email event. OmniFocus cannot fill this slot, since it offers no trigger on Zapier.
- 02
Test the trigger
Run the test on the trigger step. Zapier brings back the three most recent items from the connected account, so you map the next steps on a real email rather than a guess.
- 03
Add the filter
Add a filter step and set the condition on the sender, with a text rule since an address is text. This makes it a multi-step Zap, so it needs a paid plan.
- 04
Add Create Task
Choose OmniFocus as the action app, pick Create Task, and map the email subject into Title. Title is the one field the action requires, so it cannot stay empty.
- 05
Test, then publish
Test the OmniFocus step and check the new task in your Inbox. If it looks right, click Publish to switch the Zap on. Only emails starred after that point get picked up.
The OmniFocus action on Zapier
OmniFocus gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Task
ActionIn Zapier“Creates a new task in your OmniFocus Inbox.”
Puts a fresh to-do straight into your OmniFocus Inbox, named with whatever you map into Title, the one field it requires. You then file it from OmniFocus as usual.
When the OmniFocus Zap breaks
Zapier attaches no help article and no rate limit to OmniFocus, so the cases below are the ones every Zap shares. For deeper diagnosis there is Zapier troubleshooting.
None of them is about OmniFocus itself. They come from the app that starts the Zap, and from the way Zapier reads it.
Nothing from before the Zap
A Zap only reacts to what happens after you switch it on. Emails starred last week stay where they are; bringing that backlog into OmniFocus is a separate job.Bulk imports can be held back
If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of creating a wall of tasks.No duplicates from polling
On a polling trigger, Zapier remembers what it has already seen, so the same item does not start the Zap twice and you do not get the same task twice.Everything lands in the Inbox
Create Task writes to the OmniFocus Inbox. If several Zaps feed it, they all end up in that one place, and sorting them into projects stays manual on your side.
Need help automating OmniFocus with Zapier?
A person reads every message.



