Generate Your Drive ID Map
Why the map matters
Section titled “Why the map matters”A SharePoint document library is represented as a drive in Microsoft Graph. Its Drive ID is different from the site URL and an individual file’s item ID. Record the library’s name beside its ID so workflow users can choose an approved destination reliably.
Microsoft documents drives in the drive resource reference and library enumeration in List drives.
Intended result
Section titled “Intended result”| Site | Library | Drive ID |
|---|---|---|
| Operations | Documents | b!exampleDriveId123 |
| Operations | Products | b!exampleDriveId456 |
| Clients | Client Documents | b!exampleDriveId789 |
These are fictional examples, not discovered IDs. The Site and Library columns help people understand the mapping. The Drive ID is the value reused by relevant HighLevel workflow actions that request it; not every action necessarily needs one. Replace these examples with validated values before configuring a workflow.
Generate and validate
Section titled “Generate and validate”Use the reviewed product setup tool or an administrator-approved procedure once its instructions are confirmed. Match each returned drive to its site and library name, then validate access with the intended runtime connection.
Handoff
Section titled “Handoff”Record the map’s owner and date. Share the map with the workflow user, keeping any client secret in a separate secret manager. Regenerate or review the map when destinations change.
The administrator will be able to produce a reusable map once the discovery procedure is verified. The tool’s commands, output fields, and export format require implementation review. See PowerShell setup for helper availability and a safe local formatting example.