Workeasy

Last reviewed: July 2026

Overview

Integuru's Workeasy integration provides production-ready HTTP API access to Workeasy, the workforce management platform used by businesses to manage employees, schedules, punches, and payroll periods, covering 8 actions: list_employees, list_schedules, get_employee_details, list_punches, validate_api, list_nodes, list_pay_periods, and get_timesheet_time_segments. All 8 actions carry full API documentation with richer reference available. Integuru connects via direct HTTP requests rather than browser automation, so calls complete in under 3 seconds with a 99.9%+ success rate.

No public developer API. Workeasy does not expose an official developer API. HR-tech platforms and multi-location operators that need employee, schedule, punch, or payroll data programmatically have previously relied on manual exports or custom browser automation.

The integration covers every major workforce data surface: employee roster and detail via list_employees and get_employee_details, schedule data via list_schedules, clock punch records with extensive filtering via list_punches, timesheet breakdowns per pay period via get_timesheet_time_segments, pay period configuration via list_pay_periods, and organizational structure via list_nodes. The validate_api action provides a no-parameter health check to confirm connectivity. See the HomeBase integration for another workforce scheduling platform, or browse the full integrations catalogue.

---

Use Cases

Integuru's Workeasy integration covers the employee, scheduling, and payroll data workflows that HR-tech developers and multi-location business operators need to automate programmatically.

• Employee roster retrieval: Call list_employees to retrieve the workforce roster with optional filters. Pass status: [1] for active employees only, employee_type: [4] for contractors, or full_time: true for full-time employees. All filter parameters accept arrays for multi-value selection. Use top and skip for pagination (max 100 per page).
• Employee detail lookup: Call get_employee_details with an integer employee_id to retrieve the full record for a specific employee.
• Schedule retrieval: Call list_schedules with ISO 8601 start and end datetimes to retrieve scheduled shifts for the period. Both dates are required.
• Punch tracking: Call list_punches to retrieve clock records with granular filtering. Filter by employee_id, pay_period_id, origin (0=Employee through 8=Public), status (lifecycle: 0=Created through 3=Archived), and date ranges covering recorded value, original value, or last-modified timestamp.
• Timesheet segments by pay period: Call get_timesheet_time_segments with a pay_period_id (from list_pay_periods) to retrieve time segment breakdowns for employees in that period. The action returns up to 100 employees per page; use skip to paginate and employee_id to scope to a single employee.
• Pay period management: Call list_pay_periods to enumerate available pay periods, filtered by active or archived status, or by a specific pay period definition ID.
• Org structure: Call list_nodes to retrieve organizational structure data. Supports filtering by archived status and field selection via select. Pass count: true to return a record count alongside results.
• API health check: Call validate_api with no parameters to confirm that the Workeasy connection is active and credentials are valid.

---

Setup Notes

Integuru's Workeasy integration authenticates against https://accounts.workeasysoftware.com/account/login. Integuru manages the session automatically; you configure credentials once during setup.

Pagination across Workeasy actions follows a consistent top / skip pattern. top caps at 100 (the API limit) on list_employees; apply the same convention when paging through list_punches, list_schedules, list_nodes, and get_timesheet_time_segments.

For list_punches, the value_start_date and value_end_date parameters filter on the punch's recorded clock time. Use original_start_date / original_end_date to filter on the pre-edit original punch time, and last_modified_start_date / last_modified_end_date to find punches modified within a specific window. The last_id parameter provides cursor-style pagination for large punch exports: pass the ID of the last punch you received to retrieve only punches with a higher ID.

For get_timesheet_time_segments, pay_period_id is required. Retrieve valid IDs from list_pay_periods before calling this action.

Full API documentation for all 8 actions is available via Integuru's richer docs.