Resources · Zapier integration

Oyster Zapier integrationAutomate Oyster with Zapier.

The Oyster Zapier integration gives you 5 triggers, 6 actions and 2 searches. All five triggers poll, so timing follows your plan. The actions approve or decline expenses and create, update or delete payroll changes, which makes this an HR workflow tool, not just a notifier.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Oyster Zapier integration is good for

The Oyster Zapier integration connects your HR platform to the tools your managers and finance team already use. Oyster reports new hires, expenses, payroll runs and time off requests, and Zapier can act back on Oyster: approve or decline an expense, log a new one, or adjust a payroll change. All without code.

Three outcomes it is built for, each on real operations:

Time off that the team actually sees. New Time Off Request picks up each request and posts it where the team plans its weeks, so nobody discovers an absence on the day.

Expenses handled by rule. New Expense spots each new claim, a filter checks your condition, and Approve an Expense or Decline Expense settles it. Finance only looks at what falls outside the rule.

Payroll adjustments fed from another tool. A bonus or allowance agreed elsewhere becomes a Create Payroll Change on the right engagement, and Find Payroll Changes lets a later Zap check what is already there.

What Zapier does not do here: none of the five triggers is instant, so nothing reaches Zapier the second it happens in Oyster. Zapier checks on a timer set by your plan. And payroll changes can be created, updated or deleted, but updating only touches the amount and the currency.

Oyster has no page in our n8n or Make catalogs yet. For the tool choice, see Make vs Zapier or n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight terms, one line each. They are used as-is through the rest of the page.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event that starts the Zap, such as a new expense in Oyster. Once the Zap is on, Zapier watches for it.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, like approving an expense.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer; an instant one is reported by the app at once. All five Oyster triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Connection
Your Oyster account linked to Zapier once, then reused by every step that talks to Oyster.
Cost

What an Oyster Zap really costs

Oyster is not a premium app: it runs on the free plan, within its limits.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger checks0 tasks
  • Oyster triggers5, all polling

Checking for new hires, expenses or payroll runs never costs a task, however often Zapier looks. Each action that succeeds counts as one, and a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap. A filter, a search or a second action makes it a multi-step Zap, which needs a paid plan. Since every Oyster trigger polls, your plan also sets how often Zapier checks.

Connect

Connect Oyster to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. You need an Oyster account, plus access to any engagement, expense or payroll record you do not own yourself.

  2. 02

    Pick Oyster

    Search for Oyster by name in the dialog, select it, then click Add connection. A new tab opens on the Oyster sign-in screen, next to your Zapier window.

  3. 03

    Sign in and allow access

    Log in to Oyster in that tab and grant Zapier access to the account. The connection is saved in your list, and every Oyster step you add later reuses it.

First Zap

Your first Zap: approve routine expenses by rule

GoalEvery new Oyster expense that meets your condition is approved without a manual click.

  1. 01

    Set the trigger

    Start a new Zap, pick Oyster as the app and New Expense as the event, then select your Oyster connection from the list below.

  2. 02

    Test with real expenses

    Run the trigger test. Zapier brings back the three most recent expenses of the account, so pick one and build the next steps on it.

  3. 03

    Add your rule

    Click the plus icon, choose Filter, then set the field to look at, the rule and the value. Use a number rule on amounts: a text rule on a number never passes.

  4. 04

    Approve the expense

    Add Oyster again, choose Approve an Expense, and fill the required Expense ID with the value brought back by the trigger step.

  5. 05

    Test, then publish

    Test the action and check the expense status in Oyster. Then click Publish. With the filter, this Zap is multi-step and needs a paid plan.

Triggers

The 5 Oyster triggers

5 events start a Zap when something happens in Oyster. Zapier checks for them at the interval your plan allows.

1

Engaged Engagement

Polling trigger

In Zapier“Triggers when an engagement is hired”

Starts your Zap when an engagement is hired in Oyster, which marks the point where a candidate becomes a teammate. It is the natural start for onboarding work outside Oyster.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
IT needs to prepare accounts and the manager needs a heads-up once a hire is confirmed in Oyster.
Watch out
it differs from New Engagement, which fires earlier when the engagement is added; pick the one that matches the step you care about.
2

New Engagement

Polling trigger

In Zapier“Triggers when a new engagement is added”

Fires each time a new engagement is added to Oyster, before the hire is final, so your pipeline tools hear about it early.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your recruiting tracker or headcount sheet should list every engagement in progress, not only the signed ones.
Watch out
engagements that already existed when you published the Zap are never picked up, so seed your sheet separately.
3

New Expense

Polling trigger

In Zapier“Triggers when a new expense is added”

Picks up every expense added in Oyster, which makes it the entry point for any approval, accounting or reporting flow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you want claims logged in your finance tool, or routine ones approved by rule with Approve an Expense.
Watch out
a Zap that starts here and ends on Create Expense writes where its own trigger watches and can set itself off again and again.
4

New Payroll

Polling trigger

In Zapier“Triggers when a completed payroll has been run”

Triggers only once a payroll run is completed in Oyster, so what reaches your other tools is a finished run.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
accounting should get a record of each finished run, or the team should be told that pay has gone out.
Watch out
on the free plan the check can lag the run by up to 15 minutes, which matters if someone waits on the message.
5

New Time Off Request

Polling trigger

In Zapier“Triggers when a new time off request is made”

Catches each new time off request made in Oyster and hands it to whatever comes next, from a shared calendar to a team channel.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
managers plan in a calendar or a chat tool and should see requests there instead of in Oyster.
Watch out
it reports the request when it is made, which is not the same as an approval; treat it as a heads-up.
Actions

The 6 Oyster actions

Oyster gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Approve an Expense

Action

In Zapier“Approves an Expense.”

Marks an existing expense as approved, the same decision a manager would take in Oyster.

When to use it
claims under a threshold, or from a given category, can go through by rule after a filter.
Watch out
the Expense ID is required, so this step almost always follows New Expense or another step that carries the ID.
2

Decline Expense

Action

In Zapier“Declines an Expense.”

Rejects an existing expense in Oyster, the counterpart of the approval action.

When to use it
a claim breaks a rule you can check automatically, such as a category your policy excludes.
Watch out
it also needs the Expense ID, and a decline is a decision people notice, so test the filter on real claims first.
3

Delete Payroll Change

Action

In Zapier“Deletes a payroll change by id”

Removes a payroll change from Oyster, using its id to target the right one.

When to use it
an adjustment was cancelled at the source and must not reach the next payroll run.
Watch out
it acts on whatever id it receives, so pair it with Find Payroll Changes to be sure the Zap targets the right line.
4

Create Expense

Action

In Zapier“Create a new expense.”

Logs a new expense in Oyster for a given engagement, receipt included, so claims captured elsewhere end up in the HR platform.

When to use it
receipts arrive through a form or a finance tool and should not be typed in twice.
Watch out
eight fields are required, from Engagement ID and Category to Receipt URL, amount and currency code, the last being the Approve expense choice, which defaults to false.
5

Create Payroll Change

Action

In Zapier“Creates a new payroll change”

Adds a payroll change to an engagement for a given month and year, with its amount and currency.

When to use it
a bonus or an allowance is agreed in another tool and should reach payroll without retyping.
Watch out
Engagement ID, Type, Month, Year, amount and currency code are all required, so the earlier steps must carry each of them.
6

Update Payroll Change

Action

In Zapier“Updates the amount and currency of a payroll change”

Changes the amount and currency of a payroll change that already exists, and nothing else.

When to use it
a figure was corrected in the source tool and payroll should follow.
Watch out
Payroll change ID, Amount and Currency code are required; to change the type or month, delete and create again.
Searches

The 2 Oyster searches

2 search steps look for data that already exists in Oyster, so a later step can use it.

A search step finds something that already exists in Oyster and hands it to the steps that follow. In the editor, Oyster's searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not a clean single match.

1

Find Operation

Search

In Zapier“Looks up the status of a given operation.”

Looks up the status of a given operation in Oyster, so a later step knows whether something you started has gone through.

When to use it
a Zap needs to check the outcome of an earlier request before telling anyone it is done.
Watch out
the Operation key is required, so an earlier step in the Zap has to carry it.
2

Find Payroll Changes

Search

In Zapier“Finds a payroll change based on a time interval and engagement. The query is paginated.”

Finds payroll changes for an engagement over a time interval, returned page by page.

When to use it
before creating or deleting an adjustment, check what that engagement already has for the period.
Watch out
several results are common here, so set the multiple-results option on purpose rather than keeping the first by habit.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Oyster offers no such variant on Zapier, so you will not see it on these two searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When an Oyster Zap breaks

Zapier attaches no help article to Oyster and lists no limit specific to it. The failures people meet come from Zapier's own rules and from the required fields.

Six cases cover what goes wrong most often. When the cause is still unclear, our Zapier troubleshooting page goes further.

  • Past expenses never show up

    A Zap only reacts to what happens after it is switched on. Expenses, engagements and requests created earlier are not picked up; moving that history is a separate job.

  • An expense Zap loops on itself

    Starting on New Expense and ending on Create Expense writes where the trigger watches. The Zap sets itself off again and burns through tasks.

  • A bulk import gets held back

    Importing many expenses or engagements at once can trip Zapier's flood protection, which holds the trigger back instead of running every item.

  • The same expense never runs twice

    Zapier remembers what a polling trigger has already seen, so an edited expense does not start the Zap again. Only new items do.

  • An action stops on a missing ID

    Approve, decline and the payroll actions all need an ID. If no earlier step carries it, Zapier cannot run the step and the record stays as it was.

  • The Zap feels slow on Free

    All five Oyster triggers poll. On the free plan Zapier checks every 15 minutes, so a request can wait that long before anything happens.
Need help

Need help automating Oyster with Zapier?

A person reads every message.

FAQ

Oyster Zapier integration: FAQ

01Is the Oyster Zapier integration free?
Yes, within the free plan's limits. Oyster is not a premium app, so it works on the free Zapier plan, which gives 100 tasks a month and unlimited Zaps. Each Zap is limited to two steps, though: one trigger and one action. Posting each time off request to a channel fits. Approving expenses by rule needs a filter, and checking payroll changes needs a search, and either one turns the Zap into a multi-step Zap that requires a paid plan.
02How many tasks does an Oyster Zap use?
One per successful action. Watching Oyster for new expenses, hires or payroll runs costs nothing, however often Zapier checks. A Zap that approves an expense uses one task per approval; a Zap that creates an expense and then posts a message uses two. An action that fails is not counted against your plan. A few apps and actions take more than one task, so look at the other steps if the count rises faster than expected.
03Do Oyster triggers work in real time?
No. All five Oyster triggers are polling triggers: Zapier asks Oyster for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans the frequency can be adjusted and a check can be run by hand from the editor. The type comes from Oyster's side and cannot be switched to instant from the editor.
04What do you need to connect Oyster to Zapier?
An Oyster account, plus access to any engagement, expense or payroll record you do not own but want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for Oyster and click Add connection. Sign in to Oyster in the tab that opens and grant access. The connection is then reused by every Oyster step. For the creation actions, the person must already exist as an engagement, since an Engagement ID is required.
05Why does Create Expense fail in an Oyster Zap?
Usually because one of its required fields is empty. Create Expense needs an Engagement ID, a name, a date in Incurred on, a category, a Receipt URL, a receipt amount, a receipt currency code and the Approve expense choice. If the source app does not provide a receipt link or a currency, the step cannot run. Check the trigger's test result first, and fill any constant value, such as a default category, by hand in the step.
06What if the Oyster operation you need is not on Zapier?
Then this integration does not cover it. Zapier offers five triggers, six actions and two searches for Oyster, centred on engagements, expenses, payroll changes and time off. Approving a time off request or editing an engagement is not on the list. The options are to rebuild the need from the operations that exist, for example notifying a manager on New Time Off Request, to keep that part manual in Oyster, or to ask Oyster whether more operations are planned.
07Zapier, Make or n8n for Oyster?
Choose on criteria, not a ranking. Availability first: Oyster has thirteen operations on Zapier and runs on the free plan, so check that the other tool lists Oyster before comparing anything else. Then timing: all Oyster triggers poll on Zapier, so the plan's interval matters if speed does. Then shape: approvals by rule need a filter, which means a paid Zapier plan. Finally, who maintains the automation, and which editor that person already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations