Skip to content

Microsoft Graph - Custom Request

What it does

Send an advanced authenticated JSON request to a Microsoft Graph path using this HighLevel Location's Microsoft connection.

This is an advanced escape hatch, not the normal way to use the product. Absolute URLs are rejected and requests are confined to the Microsoft Graph origin.

When to use it

  • Use a Microsoft Graph JSON endpoint that is not covered by a dedicated product action.
  • Build an advanced workflow when you understand the Graph endpoint, permissions, request body, and response sensitivity.

Use a Microsoft Graph JSON endpoint that is not covered by a dedicated product action.

Requirements

  • A connected Microsoft 365 connection for this HighLevel Location.
  • A Microsoft Graph path beginning with / rather than an absolute URL.
  • Permissions already granted to the customer-owned Entra app for the endpoint you call.

Inputs

Action inputs
InputTypeRequiredDescriptionExample value
MethodselectYesMicrosoft Graph HTTP method.GET
PathstringYesMicrosoft Graph path beginning with /, for example /v1.0/drives/{drive-id}. Absolute URLs are not accepted./v1.0/drives/{drive-id}
Query JSONtextareaNoOptional JSON object of query parameter names and primitive values.{"$select":"id,name,webUrl"}
Body JSONtextareaNoOptional JSON value sent as an explicitly serialized JSON request body.{}

Example values

Method
GET
Path
/v1.0/drives/{drive-id}
Query JSON
{"$select":"id,name,webUrl"}
Body JSON
{}

Example workflow

Example action workflow
  1. HighLevel workflow trigger

    The business event that starts the workflow.

  2. Microsoft Graph - Custom Request

    Run the SharePoint operation with the approved Drive ID and action-specific inputs.

  3. Use the confirmed result

    Map only the documented outputs required by the next workflow step.

A common advanced pattern is: prepare method/path/query/body → Microsoft Graph Custom Request → inspect Status Code and carefully parse Response JSON.

Outputs

Action outputs
OutputTypeDescriptionExample valueUse in later steps
SuccessbooleanConfirms that the action completed successfully.trueUse as a completion checkpoint before relying on other outputs.
Status CodenumericalHTTP status code returned by Microsoft Graph.200Use to branch on the Graph response status when appropriate.
Response JSONstringSerialized JSON response returned by Microsoft Graph.{"id":"example-drive-id","name":"Documents"}Parse only the fields you need; treat the full response as potentially sensitive.

How to use outputs in later HighLevel steps

  • Success: Use as a completion checkpoint before relying on other outputs.
  • Status Code: Use to branch on the Graph response status when appropriate.
  • Response JSON: Parse only the fields you need; treat the full response as potentially sensitive.

Treat Response JSON as potentially sensitive. Microsoft Graph responses can contain customer data or preauthenticated URLs, so map only the fields your workflow actually needs.

Permissions required

  • The action itself grants no Microsoft permission. It can use only the application permissions and resource grants already configured for this Location's customer-owned Entra app.
  • For SharePoint V1, the reviewed baseline is the Microsoft Graph application permission Sites.Selected with explicit site grants. A custom endpoint may require a separately reviewed permission.

Common errors

Invalid path or JSON
The Graph path is not relative, or Query JSON / Body JSON is invalid. Use a path beginning with / and valid JSON values.
401
The Location's Microsoft connection is unavailable or expired. Reconnect or verify the HighLevel External Authentication connection.
403
The customer-owned Entra app does not have permission for the requested endpoint or resource. Review the endpoint and the app's existing permissions. Do not broaden permissions without an explicit need.
429 / 5xx
Microsoft Graph throttled or failed the request. Follow the endpoint's retry guidance and avoid blind retries for state-changing requests.

Product/action version

Product version
Pre-launch technical release · 2026-10-04
Action version
1.0
Implementation reference
Integration commit 8440a0f · src/modules/workflows/actions/microsoft-graph-custom-request.json · code/microsoft_graph_custom_request.1.0.js

Last updated