Resources · Zapier integration

Out of Office Assistant for Jira Zapier integrationAutomate Out of Office Assistant for Jira with Zapier.

The Out of Office Assistant for Jira Zapier integration gives you 0 triggers, 2 actions and 0 searches. A Zap (an automation you build on Zapier) starts in another app and sets or removes your Jira absence for you, without opening Jira.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Out of Office Assistant for Jira Zapier integration does

Out of Office Assistant lives inside Jira Cloud: when you are away, it tells colleagues who assign you issues, and it can hand those issues to a coverer. The Zapier integration lets another tool switch that absence on or off, so you no longer set it by hand in Jira.

Three results people build with it. Holidays that reach Jira on their own: a leave entry in a calendar or an HR tool runs Add or Update Absence, so the out-of-office rule exists before you leave. Cover that follows the plan: the same action can name one or more coverers, so issues assigned during your absence go to someone who is actually there. A clean return: Delete Absence removes the rule when a trip is cancelled, which tells Jira you are back.

Now the limits. The app has no trigger, so nothing in Out of Office Assistant can start a Zap: not a new rule, not a return, not a reassigned issue. It has no search step either, so a Zap cannot list or look up the absences that already exist. To delete one, the Zap must already carry its exact start and end dates.

Every Zap therefore starts in another app, and that app decides how quickly your Jira absence appears. If you are still weighing platforms, n8n vs Zapier and Zapier review are worth a read before you build.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English. The rest of the page uses them without explaining them again.

Zap
The automation itself: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. Out of Office Assistant has none, so yours always comes from another app.
Action
What the Zap does once it has started: here, adding, updating or deleting an absence rule in Jira for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by its own app the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, like an event marked as leave.
Search step
A step that looks up something already stored in an app for later steps. This app offers no search step.
Connection
Your Jira account with Out of Office Assistant linked to Zapier once, then reused by every step that uses it.
Cost

What an Out of Office Assistant Zap really costs

Out of Office Assistant for Jira is not reserved for paid plans: it works on the free plan.

  • TriggerNever billed
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • App triggersNone, start from another app

The trigger never costs a task, wherever it comes from, and looking for new data is free too. Each action that succeeds counts once; an action that fails is not counted. Setting one absence therefore costs one task. The free plan offers 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger and one action. A filter that keeps only leave events, or a second action, makes it a multi-step Zap that needs a paid plan. Timing comes from the starting app: a polling trigger follows the grid below, an instant one fires straight away on any plan.

Connect

Connect Out of Office Assistant for Jira in three steps

  1. 01

    Open your connections

    In your Zapier account, open the Apps page and click + Add connection. You need an account on the app first, plus access to anything you do not own yourself but want the Zap to change.

  2. 02

    Find the app

    Type Out of Office Assistant in the search box of the dialog, pick the Jira one, then click Add connection. A new tab opens on the app side so you can sign in.

  3. 03

    Grant access

    Sign in in that tab and allow Zapier to reach the account. The connection then shows on your Apps page, and both actions can select it in any Zap without asking again.

First Zap

Your first Out of Office Assistant Zap, step by step

GoalCreate a Jira absence each time a leave event lands in your work calendar.

  1. 01

    Pick the starting app

    Create a Zap and choose the app and event that start it, here a new event in your calendar. Out of Office Assistant cannot be this first step, as it has no trigger.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you build the next steps on a real event, dates included.

  3. 03

    Keep only leave

    From the plus icon, add Filter and set the value to check, the rule and the value to compare with. The filter makes this a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the absence

    Add Out of Office Assistant for Jira with Add or Update Absence, select your connection and map the event dates into the rule. Name a coverer if someone takes over.

  5. 05

    Test, then publish

    Test each step once and check in Jira that the rule looks right. Then click Publish to switch the Zap on for the next leave event.

Actions

The Out of Office Assistant for Jira actions

Out of Office Assistant for Jira gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Delete Absence

Action

In Zapier“Deletes a Jira Out of Office Rule, meaning that this user returned to office.”

Removes an existing out-of-office rule, which tells Jira that the person is back at work. You point to the rule through its start date and end date.

When to use it
a consultant cancels a trip in the team planner and wants colleagues to stop getting away notices.
Watch out
both dates are required and must match the existing rule, so keep them in the app that starts the Zap.
2

Add or Update Absence

Action

In Zapier“Adds a Jira Out of Office Rule, defining when the current user is out of office and (optional) auto assign one or more coverers.”

Creates or changes the out-of-office rule of the connected user, with the dates of the absence and, if you want, one or more coverers who receive the issues assigned meanwhile.

When to use it
a support lead books leave in the HR tool and wants Jira to warn colleagues and route new issues to a backup.
Watch out
one setting decides whether Jira Service Management customers also see the away status, so choose it on purpose.
When it breaks

When an Out of Office Assistant Zap breaks

Zapier attaches no help article to this app and lists no limit of its own, so the traps below are the general ones. They are still what trips up most first builds.

Each case can be spotted before it costs tasks or leaves a wrong absence in Jira. Go through them before you publish, and keep Zapier troubleshooting close for the day a Zap stops.

  • Leave booked earlier is ignored

    A Zap only reacts to what happens after you switch it on. Absences planned before that never reach Jira; adding them is a separate job.

  • A bulk import of events

    If the starting app suddenly returns a huge batch, after a calendar import for instance, Zapier's flood protection can hold the Zap back.

  • The same event, twice

    When the starting trigger polls, Zapier remembers what it has already seen, so one leave event does not create the same absence twice.

  • A filter on the free plan

    The free plan builds two-step Zaps only. A filter that keeps leave events, or a second action, makes the Zap multi-step and it needs a paid plan.
Need help

Need help automating Out of Office Assistant for Jira with Zapier?

A person reads every message.

FAQ

Out of Office Assistant for Jira Zapier integration: FAQ

01Is the Out of Office Assistant for Jira Zapier integration free?
Yes, on the Zapier side it runs on the free plan, because Zapier does not reserve this app for paid plans. The free plan gives 100 tasks a month and unlimited Zaps. The catch is the shape: each Zap stops at two steps, one trigger from another app and one action. A Zap that creates an absence from a new calendar event fits. Add a filter that keeps only leave events and it becomes a multi-step Zap, which needs a paid plan. Count the steps your idea needs before you rely on the free tier.
02How many tasks does an absence Zap use?
One task per action that succeeds, and nothing for the trigger. Add or Update Absence counts once each time it sets a rule, and Delete Absence counts once each time it removes one. A failed action is not counted against your plan. The trigger, which comes from another app, never costs a task, and neither does the wait for new events. So a Zap that books a single absence per leave request uses one task per request, which leaves plenty of room in the 100 tasks of the free plan.
03Does the Jira absence appear in real time?
It depends on the app that starts the Zap, since Out of Office Assistant has no trigger. If that app reports its events instantly, the Zap starts straight away on any plan. If its trigger polls, Zapier checks on a timer set by your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. The action then runs in the same go. For an absence booked days ahead, a few minutes rarely matter; for a same-day sick leave, an instant trigger app is the better pick.
04What does it take to connect Out of Office Assistant to Zapier?
An account on the app, inside your Jira Cloud site, and access to anything you do not own but want the Zap to change. Then three moves: open the Apps page of your Zapier account and click + Add connection, search for the app and click Add connection, then sign in in the tab that opens and grant Zapier access. The connection is reused by both actions in every Zap. Since the rule belongs to the connected user, connect the account whose absences the Zap should manage.
05Why does Delete Absence not find the rule?
Because it identifies the rule only by its Start Date and End Date, and both are required. If the dates the Zap sends differ from the ones stored in the rule, there is nothing to delete. With no search step in this app, a Zap cannot look up the existing absences first. The safe pattern is to keep the dates where the leave was booked, in the calendar or HR tool, and send exactly those values when the leave is cancelled. Test the step once on a dummy absence before you publish.
06What if the Out of Office operation you need is missing?
Then this integration cannot do it, because Zapier only offers what the app exposes: Add or Update Absence and Delete Absence. There is no trigger for a rule created or ended in Jira, no search step to list absences, and nothing to change the coverers of an issue already assigned. Write down the exact gap before you hunt for a workaround. Sometimes the starting app can hold the missing piece, such as the record of booked dates; otherwise, check whether another automation platform covers the need.
07Zapier, Make or n8n for Out of Office Assistant?
That depends on your criteria rather than on a single winner. On Zapier, this app offers two actions and no trigger, and it runs on the free plan while each Zap stays at two steps. If one calendar event to one absence is all you need, Zapier is the short road. If you need a filter, several steps or a lot of absences to manage, compare what each platform charges for those runs on your own numbers, and check which operations of this app each tool actually exposes.
Same platform

Other docs you might need on this stack.

Browse all integrations