Get event type scheduling config - Automate.ax

calcom.getEventTypeSchedulingConfig retrieves effective scheduling configuration for an event type.

automations/get-event-type-scheduling-config.automation.ts

import { automation, markSignificant } from "automate.ax"
import { calcom } from "automate.ax/calcom"

export default automation("Get event type scheduling config", () => {
  markSignificant(calcom.getEventTypeSchedulingConfig({ eventTypeId: 23 }))
})

Input

Pass these fields:

Field	Type	Required	Description
`eventTypeId`	`integer`	Yes	Must be greater than 0.

Output

Returns an object with these fields:

Field	Type	Required	Description
`eventTypeId`	`number`	Yes	Event type ID
`schedulingType`	`"roundRobin" \| "collective" \| "managed"`	Yes	The scheduling type of this event type. Determines which fields are populated.
`hosts`	`object[]`	Yes	Array of hosts assigned to this event type
`assignAllTeamMembers`	`boolean`	Yes	Whether all team members are automatically assigned as hosts
`hostGroups`	`object[]`	No	Host groups for organizing round-robin hosts. Only present for roundRobin scheduling type.
`rescheduleWithSameRoundRobinHost`	`boolean`	No	Whether rescheduled events keep the same round-robin host. Only present for roundRobin scheduling type.
`allowRRHostChoiceOnReschedule`	`boolean`	No	Whether the person rescheduling may choose between the original host and the whole team. Only present for roundRobin scheduling type.
`isRRWeightsEnabled`	`boolean`	No	Whether round-robin weights are enabled for host distribution. Only present for roundRobin scheduling type.
`maxLeadThreshold`	`number \| null`	No	—
`includeNoShowInRRCalculation`	`boolean`	No	Whether no-show bookings are included in round-robin calculations. Only present for roundRobin scheduling type.
`crmRecordOwnerFallbackWindowHours`	`number \| null`	No	—
`crmRecordOwnerFallbackWindowSkipWeekends`	`boolean`	No	Whether to exclude weekends from the CRM record owner fallback window calculation. Only present for roundRobin scheduling type.

Cal.com enforces account role, plan, and availability requirements. Provider rejections surface as structured action failures with the HTTP status and any Retry-After delay.