Microsoft GraphGet free/busy schedule
BetaReads data
Finds when people and rooms in Microsoft 365 are free or busy over a time window.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Microsoft Graph connection the step signs in with. |
| Ask asRequired | The user whose calendar asks, by object id or sign-in address. |
| People and roomsRequired | The addresses of users, distribution lists or rooms to read free/busy for. |
| FromRequired | ISO 8601 without a zone — the time zone below applies. |
| UntilRequired | text |
| Time zone | An IANA name, e.g. Europe/Amsterdam. Defaults to UTC. The answer's times are in it too. |
| Slot length | Minutes per character of the availability view, 5 to 1440. A calendar slot holding more than 1000 entries is refused by Graph. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `microsoft-graph`) |
user | text |
schedules | text |
start | text |
end | text |
timeZone | text, by default "UTC" |
interval | number, by default 30 |
Output
| Field | Type |
|---|---|
schedulesOne schedule per address | array |
countSchedules in this answer | number |
Sample output, and the expression for each field
- count0
- schedules[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"end": "<until>",
"interval": 30,
"schedules": "<people and rooms>",
"start": "<from>",
"timeZone": "UTC",
"user": "<ask as>"
},
"label": "Get free/busy schedule",
"type": "graph.getSchedule",
"version": 1
}