3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node operation "Get Google Users" under the "Google Settings" resource is designed to retrieve user information from a Google environment. This operation is useful for scenarios where you need to programmatically access and manage Google user data, such as syncing users with another system, auditing user accounts, or generating reports on user activity.

A practical example would be automating the extraction of all Google Workspace users in an organization to update an internal directory or to trigger workflows based on user attributes.

Properties

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

The "Options" property allows users to specify any valid JSON structure that will be sent as the body of the request. This can include filters, pagination settings, or other API-specific options supported by the underlying Google API endpoint.

Output

The output of this operation is a JSON object containing the retrieved Google user data. The exact structure depends on the Google API response but typically includes user details such as email addresses, names, status, and other profile information.

If the node supports binary data output (not indicated here), it would represent files or attachments related to users, but this operation primarily deals with JSON user data.

Dependencies

  • Requires an API key credential or OAuth2 authentication configured in n8n to access Google APIs.
  • The node depends on proper permissions granted to the authenticated account to read user information from Google Workspace or the relevant Google service.
  • No external dependencies beyond the Google API and n8n's HTTP request capabilities are indicated.

Troubleshooting

  • Common issues:

    • Authentication errors due to invalid or expired credentials.
    • Insufficient permissions if the authenticated account lacks rights to list users.
    • Malformed JSON in the "Options" property causing request failures.

  • Error messages:

    • 401 Unauthorized: Check that the API key or OAuth token is valid and has not expired.
    • 403 Forbidden: Ensure the authenticated user has permission to access user data.
    • 400 Bad Request: Verify that the JSON provided in "Options" is correctly formatted.

Resolving these usually involves re-authenticating, adjusting permissions in Google Admin Console, or correcting the JSON input.

Links and References

Discussion