Connector name: Zendesk_workforce_management

Table name: shift and shift_task

API documentation link: https://z3nwfm.zendesk.com/wfm/l5/public-api/docs#/Shifts/PublicApiFetchShifts

Additional details: 

The connector syncs actual activity (activity, agent_activity) and attendance aggregates (agent_attendance), but not the planned schedule. scheduled_time is a total duration with no start or end time. We need each agent’s scheduled shift per day (start and end) to measure punctuality, meaning planned start vs. actual start. Right now we load that by hand from a report.

The WFM public API exposes this data through POST /wfm/public/api/v1/shifts/fetch:

• Body: startDate, endDate, orderBy (required), plus agentIds (optional; all active agents if empty), published (optional), page
• Returns, for each shift: id, agentId, startTime, endTime (epoch), published, parentId, and a tasks[] array (id, startTime, endTime, name, taskableId, taskableType, …)

Suggested tables: shift (PK id, FK agent_id) and shift_task (PK id, FK shift_id). Ideally:

• sync only published shifts (published: true), or include the flag so we can filter
• cover future dates too, since schedules are published ahead of time
• include the shift-table changes in the same 31-day rollback window as the other tables, since schedules get edited after publishing

We run 4 WFM connections and would use this on all of them. Thanks!