3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node provides an operation to retrieve Microsoft 365 users via the "Get M 365 Users" action. This is useful for workflows that need to access user information from a Microsoft 365 tenant, such as syncing user data, managing licenses, or integrating with other systems that require user details.

Typical use cases include:

  • Automating user directory synchronization between Microsoft 365 and other platforms.
  • Fetching user profiles for reporting or auditing purposes.
  • Integrating Microsoft 365 user data into custom applications or dashboards.

Properties

Name Meaning
Options A JSON object containing additional parameters or filters to customize the user query.

The "Options" property allows you to specify any valid JSON configuration that modifies how the Microsoft 365 users are retrieved. This could include filtering criteria, pagination settings, or selecting specific user fields.

Output

The node outputs a JSON array of Microsoft 365 user objects under the json field. Each object represents a user with their associated properties as returned by the Microsoft 365 API.

If the node supports binary data output (not indicated in the provided code), it would typically represent user-related files or attachments, but this is not evident here.

Dependencies

  • Requires an authenticated connection to Microsoft 365 services, typically through an API key or OAuth2 token configured in n8n credentials.
  • The node depends on Microsoft Graph API or equivalent Microsoft 365 user management endpoints to fetch user data.
  • Proper permissions/scopes must be granted to the authentication token to read user information.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or expired tokens.
    • Insufficient permissions leading to authorization errors.
    • Malformed JSON in the "Options" property causing parsing errors.
    • Network connectivity problems preventing API calls.

  • Error messages and resolutions:

    • 401 Unauthorized: Check and refresh your API authentication credentials.
    • 403 Forbidden: Ensure the API token has the necessary permissions to read user data.
    • 400 Bad Request: Verify the JSON syntax in the "Options" input; it must be valid JSON.
    • Timeouts or network errors: Confirm network access to Microsoft 365 endpoints and retry.

Links and References

Discussion