iPayroll and Keeping Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Connect iPayroll and Keeping to automate hr workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about iPayroll and Keeping

Detailed info you need to know about iPayroll and Keeping integrations in WEXTL. Explore which modules apps support and how you connect them.

  • iPayroll

    • HR
    • 1 trigger
    • 10 searches
    • 7 actions

    Manage employees, cost centres, superannuation and custom fields in iPayroll, the cloud payroll and HR software.[5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

    Time tracking software for logging hours against clients, projects and tasks.[6]

How to connect iPayroll to Keeping

Set up your iPayroll and Keeping integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between iPayroll and Keeping work in WEXTL?

WEXTL exposes actions and triggers for iPayroll and Keeping that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

iPayroll triggersKeeping actions

iPayroll modules

  • Create a Superannuation Record Starts superannuation for an employee with a Pay Element such as SUPER or MV and a Quantity for the contribution amount or percentage. Use Superann Member Number to record the member number held with the super fund.
  • Create Cost Centres Saves a batch of cost centres in iPayroll, giving each a Code and a Description. The response gives the ID and Display Value of the new cost centre.
  • Create Employees Adds employees to iPayroll, each with a Surname, First Names, Start Date, Pay Frequency, Payment Method, Bank Account Number and Tax Number. Use Employee ID to set your own ID, otherwise iPayroll assigns one.
  • Delete a Superannuation Record Deletes a superannuation record from an employee in iPayroll.
  • Get a Cost Centre Fetches one cost centre from iPayroll, including whether it is Active and its Display Value.
  • Get a Custom Field Reads one custom field of an employee, returning its Name, Category Name and Description.
  • Get a Superannuation Record Fetches the superannuation record with its Pay Element, Amount and Super Fund Identifier for an employee.
  • Get an Employee Retrieves a single employee with Surname, First Names, Email, Start Date and Pay Frequency from iPayroll.
  • Get Cost Centres Returns the cost centres in iPayroll with their Code, Description and Display Value. Set Limit to return only part of the list.
  • Get Employee Custom Fields Lists the custom fields set on one employee, each with its Category Name and Name. Add Limit to stop after a fixed number of results.
  • Get Employee Custom Fields By Category Lists the custom fields that belong to a single category on an employee record, with their Category Name and Name. Use Limit to return fewer results.
  • Get Employees Lists the employees of your iPayroll account with the Surname, First Names and Email of each. Lower Limit to keep the list short.
  • Get Superannuation Records Lists the superannuation records held for an employee, showing Pay Element, Quantity and Cost Centre for each. Lower Limit to see fewer of them.
  • Make an API Call Runs a free-form request against the iPayroll REST API using your saved credential.
  • Search Custom Fields Looks up custom fields across iPayroll and narrows them by Category ID, Category Name, Custom Field ID or Custom Field Name. Add Employee ID to search one employee only.
  • Update a Superannuation Record Sets a different Pay Element, Quantity, Cost Centre or Super Fund Identifier on a superannuation record. Use Amount with MV, Super Sacrifice or Reportable Super pay elements.
  • Update an Employee Changes data of an employee such as Surname, Email, Pay Frequency or Bank Account Number. Several tax and KiwiSaver fields apply to NZ or AU payroll only.
  • Watch Cost Centres Polls iPayroll on a schedule and runs the workflow once for each newly created cost centre. Use Limit to cap how many cost centres each check returns.

Keeping modules

  • Archive a Project Archives a project, which hides it from the default project list until it is restored.
  • Archive a Task Archives a task in Keeping, which sets its State to archived. The task can be brought back with Restore a Task.
  • Create a Client Adds a client to your Keeping organisation under a unique Name. Add a Code of up to 30 characters to identify the client across your organisation.
  • Create a Project Creates a project in Keeping under a unique Name. Leave Client empty for an internal project, and give Task Assignments and Participations to pick the tasks and users yourself.
  • Create a Task Creates a task with a unique Name. Turn off Assign to active projects to stop it being assigned to existing and future active projects, and use Direct to control whether time entries count as direct.
  • Create an Entry Records a time entry in Keeping, either with a Start and End or with Hours for an exact duration on hour timesheets. Leave User ID empty for your own user, and add Project ID and Task ID to book the time against them.
  • Delete a Client Removes a client from your organisation in Keeping. Deleted items stay gone.
  • Delete a Project Removes a project belonging to the Keeping organisation you work in. Deleted items are lost.
  • Delete a Task Deletes one task of the chosen organisation. The delete is final.
  • Delete an Entry Deletes a logged time entry from a Keeping organisation. It stays gone.
  • Get a Client Fetches the Name, Code and State of one client.
  • Get a Project Looks up one project and returns its Client ID, Name, Code, Direct setting, Task assignments and Participations.
  • Get a Task Loads one task from an organisation, with its Name, Code and State.
  • Get a User Reads one user of the organisation, as opposed to the signed-in user.
  • Get an Entry Reads a single time entry, showing its Purpose, Hours and Note, and whether it is Locked or Ongoing.
  • Get the Current User Returns the Keeping user you are signed in as, including its State.
  • List Clients Shows clients in an organisation. Use State to filter by active or inactive, and Search query to find a client by name or code.
  • List Organizations Retrieves the organisations your Keeping account belongs to, with the Time zone, Currency, Current plan and Features of each.
  • List Projects Finds projects and returns the active ones when State is not set. Narrow the results to projects linked to a task, user or client with Task ID, User ID or Client ID.
  • List Tasks Returns tasks, active ones by default. Use State to include archived tasks, and Project to see only the tasks assigned to one project when projects are enabled.
  • List Timesheet Entries Gets time entries of a user. Use User ID to read another user and Date to choose the day, otherwise the entries default to the connected user and the current day.
  • List Users Searches users of an organisation, showing First name, Surname, Role and State. Set Project ID to list the users participating in a given project.
  • Make an API Call Makes an authorized free-form request to the Keeping REST API with your saved credential.
  • Restore a Project Brings an archived project back to active use in Keeping.
  • Restore a Task Reactivates an archived task so it shows in the default task list again.
  • Resume an Entry Restarts the clock on an existing time entry, which then reports as Ongoing again.
  • Stop an Entry Ends a running time entry, fixing its End time and Hours.
  • Update a Client Renames a client with Name or changes the Code that identifies it. Names must be unique within the organisation.
  • Update a Project Changes the Name, Code, Direct setting or Client of a project. Use Task Assignments and Participations to set which tasks and users are linked.
  • Update a Task Alters a task. Use Name or Code to rename or recode it, and Direct to control whether assignments or time entries are treated as direct.
  • Update an Entry Edits a time entry. Change its Date, Purpose, Note or Tag IDs, move it to another Project ID or Task ID, or correct Start, End and Hours.
  • Watch Clients Polls on a schedule and runs the workflow once for every client added to Keeping since the previous poll. Use Limit to bound how many are processed in one cycle.
  • Watch Organizations Checks for organisations that newly appear on your account and fires once for each, with its Time zone and Currency.
  • Watch Projects Runs on a schedule, picks up new projects and emits each one with the Client and State it has.
  • Watch Tasks Checks for tasks added after the previous poll on a schedule, triggering per task and carrying the Name, Code and Direct setting of each.
  • Watch Timesheet Entries Looks for time entries added since the previous poll and starts the workflow for every one, carrying its User ID, Date and Hours.
  • Watch Users On each scheduled run, finds users added to the organisation and triggers once per user, with First name, Surname and Role.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with iPayroll and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate iPayroll and Keeping on WEXTL®

Claim your 3-day trial to build iPayroll with Keeping integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting iPayroll and Keeping.

How do I connect iPayroll and Keeping?

Connect your iPayroll and Keeping accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between iPayroll and Keeping?

Example: when the "Watch Cost Centres" trigger in iPayroll fires, WEXTL can "Archive a Project" in Keeping. iPayroll has 1 trigger (including Watch Cost Centres). Keeping has 31 actions (including Archive a Project, Archive a Task, and Create a Client). Add filters and transforms between steps when you need them.[1]

Can iPayroll trigger actions in Keeping, and Keeping in iPayroll?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate iPayroll and Keeping?

No. iPayroll-to-Keeping automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does iPayroll integrate with Keeping in real time?

Yes. Trigger-based automations start the moment iPayroll (or Keeping) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a iPayroll + Keeping integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect iPayroll with Keeping?

You can build your iPayroll + Keeping automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the iPayroll and Keeping integration.

  1. iPayroll and Keeping integration source code, module specs and credentials implementation.
  2. Our iPayroll and Keeping integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for iPayroll and Keeping, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. iPayroll integration information
  6. Keeping integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted iPayroll and Keeping integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore iPayroll and Keeping, or get started