3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The "Get Microsoft 365 Integration" operation retrieves information about Microsoft 365 integrations configured in the connected environment. This node is useful for scenarios where you want to list, filter, or search through Microsoft 365 integration instances, such as checking which integrations are active, retrieving details for reporting, or managing integrations programmatically.

Practical examples include:

  • Fetching a list of all Microsoft 365 integrations with specific properties.
  • Searching integrations by name or status.
  • Filtering integrations based on connection state or other attributes.
  • Paginating results when many integrations exist.

Properties

Name Meaning
$top Show only the first n items (limit the number of returned integrations).
$skip Skip the first n items (useful for pagination).
$search Search items by search phrases. If the phrase contains spaces and is not quoted, it will be wrapped in quotes automatically.
$filter Filter items by property values using OData syntax (e.g., State eq 'Connected').
$count Include count of items in the response (boolean).
$orderby Order items by property values (e.g., Name desc, CreatedAt asc).
$select Select specific properties to be returned (e.g., Id,Name).
$expand Expand related entities to include additional linked data (e.g., RelatedEntity1,RelatedEntity2).

Note: The node provides two sets of options collections with overlapping fields $select and $expand, both serving to customize the returned data.

Output

The node outputs JSON data representing the Microsoft 365 integrations retrieved from the service. The structure typically includes an array of integration objects with properties depending on the selected fields ($select) and expanded related entities ($expand).

If binary data were involved, it would be summarized here, but this operation deals solely with JSON data describing integrations.

Dependencies

  • Requires an authenticated connection to Microsoft 365 services via an API key or OAuth token configured in n8n credentials.
  • The node sends HTTP requests to Microsoft Graph or a similar Microsoft 365 API endpoint supporting OData query parameters.
  • Proper permissions/scopes must be granted to the API authentication to read Microsoft 365 integration data.

Troubleshooting

  • Empty or incomplete results: Check if filters or search queries are too restrictive or malformed.
  • Authentication errors: Ensure the API credential is valid and has sufficient permissions.
  • Invalid query parameters: Verify that OData query strings ($filter, $orderby, etc.) follow correct syntax.
  • Pagination issues: Use $top and $skip correctly to navigate large result sets.
  • Unexpected errors: Review API limits or service availability; consult Microsoft 365 API documentation for error codes.

Links and References

Discussion