Openpaye Zapier integrationAutomate Openpaye with Zapier.
The Openpaye Zapier integration gives you 0 triggers, 4 actions and 0 searches: Zapier writes into your payroll software, creating or updating companies, establishments, employees and contracts, while the event that starts the Zap comes from another app.
Verified Trustpilot reviews · AI, automation & growth agency
What the Openpaye Zapier integration actually does
Openpaye is online payroll software built for small and mid-sized companies. Through Zapier, other tools can fill it for you without code: a Zap (the automation you build on Zapier) starts on an event elsewhere, then writes the matching company, site, employee or contract into Openpaye.
Three results justify the setup. A client file opened in one go: when a new client is signed in your CRM, Create/Update Company opens the company file and Create/Update Establishment adds its site. New hires that reach payroll on their own: an onboarding form or a sheet feeds Create/Update Employee, so nobody types the same name twice. Contracts kept in step: Create/Update Contract records or corrects the contract attached to that employee.
The limits are clear-cut. Openpaye has no trigger on Zapier, so nothing that happens in your payroll can start a Zap: the integration only writes. It has no search step either, so a Zap cannot look up an existing employee before acting. And every action carries codes (file code, registration number, establishment code) that your source app must already hold. Each action creates the record or updates it, so one action covers both the first entry and later corrections.
Before choosing a tool, you can read Make vs Zapier and our Zapier review.
Zapier vocabulary in one minute
Seven words carry the whole page. Each is explained once here, then used as is.
- Zap
- The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Openpaye, it always comes from another app, such as a form or a sheet.
- Action
- What the Zap does after it starts: here, the step that creates or updates a record in Openpaye for you.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by its app, with no wait for a check.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition, and stops it there otherwise.
- Connection
- Your Openpaye account linked to Zapier once, then reused by every step of every Zap that writes into Openpaye.
What an Openpaye Zap really costs
Zapier bills tasks, not Zaps. The trigger of the source app never costs a task, and Zapier checking that app for new items costs nothing either. Only the Openpaye actions are counted.
- TriggerNever costs a task
- Action that succeeds1 task each
- Action that failsNot counted
- Free plan100 tasks a month, two-step Zaps only
Each action that succeeds counts once: a Zap that creates an employee and then the contract uses two tasks per hire. An action that fails is not counted. Openpaye is not reserved to paid plans, so it works on the free plan, with 100 tasks a month and unlimited Zaps. The catch: the free plan only builds two-step Zaps, one trigger and one action. A second action or a filter makes it a multi-step Zap, which needs a paid plan. The interval grid applies to the trigger of the source app, when it works by polling.
Connect Openpaye to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need an Openpaye account first, plus write access to any company file you do not own and want a Zap to fill.
- 02
Pick Openpaye
Type Openpaye in the search box of the dialog, select it, then click Add connection. Zapier opens a new tab so that you sign in on Openpaye's own side.
- 03
Sign in and grant access
Log in to Openpaye in that tab and allow Zapier to use the account. The connection is then saved once and offered again in every step that writes into Openpaye.
Your first Openpaye Zap
GoalEach new hire added to an onboarding sheet becomes an Openpaye employee with a contract.
- 01
Build: choose the trigger
Create a Zap and pick the app that holds your new hires, here a sheet with one row per hire, then its new row event. Openpaye cannot start a Zap itself.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows of the sheet, so you map the next steps on a real hire rather than a blank.
- 03
Add the employee
Add the Openpaye action Create/Update Employee. Map the file code, the registration number and the name from the row, then test the step.
- 04
Add the contract
Add Create/Update Contract. Map the same file code and registration number, then the contract number, the establishment code and the professional status.
- 05
Test and publish
Test each step once and check the result in Openpaye. When both records look right, click Publish to switch the Zap on. It is now a multi-step Zap.
Openpaye actions
Openpaye gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create/Update Contract
ActionIn Zapier“Create or Update Contract”
Records an employment contract in Openpaye, or updates it if it is already there. It ties together the company file, the employee's registration number, a contract number, the establishment and the professional status.
Create/Update Company
ActionIn Zapier“Create or update a new company.”
Opens a company file in Openpaye from a code and a company name, or updates that file when it exists. Every other action then hangs off this file.
Create/Update Employee
ActionIn Zapier“Create or update an employee”
Adds an employee to a company file, or updates the existing record, from a file code, a registration number and a name. It is the action most onboarding Zaps start with.
Create/Update Establishment
ActionIn Zapier“Create or Update Establishment”
Creates a site, an establishment, inside a company file, or updates it, from the file code, its own code and the legal company name.
When an Openpaye Zap breaks
Zapier attaches no help article to Openpaye and its listing documents no limit of its own. The breakdowns below come from how Zapier works, applied to payroll data.
Most trouble comes from codes the source app does not carry and from history nobody moved. If a Zap misbehaves, our Zapier troubleshooting page is the next stop.
Existing staff are never sent
A Zap only reacts to what happens after you publish it. Employees already in your sheet or HR tool are not pushed to Openpaye: that backlog is a separate job.A company code that is too long
Create/Update Company takes a code of 6 characters at most. A longer code mapped from a CRM will not fit, so shorten it at the source.A bulk import held back
Load a whole team into the source app at once and its trigger may return a huge batch. Zapier's flood protection can hold it back instead of running it.Rows that seem to be skipped
On a polling trigger, Zapier remembers what it has already seen, so a row it has processed does not start the Zap again and the same hire is not created twice.
Need help automating Openpaye with Zapier?
A person reads every message.
