Represent teams and org subsets with Merge HRIS's Group common model
domain: hr-payroll · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call the Groups endpoint to list Group objects; each has a name, an optional parent_group reference, and a type field
Use type to determine whether the source platform represents the Group as a team, since Merge normalizes this per-provider based on how each platform models teams
Traverse parent_group references to reconstruct a nested team/department hierarchy from a flat list of groups
Join Groups back to Employees (employees can belong to multiple Groups) rather than assuming a single department per employee
Use remote_id to correlate a Group back to its native ID in the underlying HRIS if you need to write back to the source system via passthrough
Known gotchas
A Group is a generic container for "any subset of employees" (department, team, etc.) - don't assume every Group instance represents the same organizational concept across providers
Group hierarchy depth and semantics vary by underlying provider - test against each connected provider rather than assuming a uniform tree shape
Group membership is read via the Employee object's group reference(s) - the Group object itself does not enumerate its members inline
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?