Employment Hero Payroll (formerly KeyPay)
Business software
Sync Employment Hero Payroll employee, pay run, timesheet, and leave data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.
The Employment Hero Payroll connector syncs your Australian/NZ payroll data into analytics-ready tables in your data warehouse. Pull employees, pay runs, timesheets, and leave from the Employment Hero Payroll API (formerly KeyPay), with Ingest handling auth, pagination, and retries so the tables stay current.
What you would get
Each of these arrives as its own table, kept current on the schedule you choose:
- Employees
- Pay runs
- Timesheets
- Leave
How it gets built
- Choose Employment Hero Payroll (formerly KeyPay) when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads Employment Hero Payroll (formerly KeyPay)'s documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against Employment Hero Payroll (formerly KeyPay) itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
API key, OAuth 2.0, or Basic Auth (method varies by integration). KeyPay rebranded to Employment Hero; existing customers or partners set up credentials through Employment Hero's own onboarding, not an open public signup.
You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.
Questions
- Does Ingest have a Employment Hero Payroll (formerly KeyPay) connector?
- Not as a finished connector yet. Ingest builds it from Employment Hero Payroll (formerly KeyPay)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can Employment Hero Payroll (formerly KeyPay) data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
Employment Hero Payroll (formerly KeyPay) API documentation: https://api.keypay.com.au/
Where this would land, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.