3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node operation "Get Google Settings" is designed to retrieve configuration or settings data from a Google-related service. It allows users to query and fetch specific Google settings with fine-grained control over the returned data through various OData-like query options such as filtering, searching, ordering, selecting specific fields, and expanding related entities.

This node is beneficial in scenarios where you need to programmatically access and manage Google service configurations within an automated workflow. For example, it can be used to:

  • Retrieve a list of Google account settings filtered by certain criteria.
  • Fetch only specific properties of Google settings to reduce payload size.
  • Search for particular settings using search phrases.
  • Paginate through large sets of settings using skip and top parameters.

Properties

Name Meaning
Options A collection of optional query parameters to customize the request:
$top Show only the first n items (limit the number of results).
$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 quoted automatically.
$filter Filter items by property values (e.g., State eq 'Connected').
$count Include count of items (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 (e.g., RelatedEntity1,RelatedEntity2).

These options allow flexible querying of Google settings data, enabling precise control over what data is retrieved and how it is presented.

Output

The output of this node operation is JSON data representing the requested Google settings. The structure depends on the query parameters used but generally includes an array of setting objects with their properties.

If $count is set to true, the output may also include a count of total items matching the query.

No binary data output is indicated for this operation.

Dependencies

  • Requires an authenticated connection to the relevant Google API service that exposes the settings endpoint.
  • An API key credential or OAuth token must be configured in n8n to authorize requests.
  • The node relies on standard HTTP query parameters to interact with the Google API.

Troubleshooting

  • Common issues:

    • Incorrect or missing authentication credentials will cause authorization errors.
    • Invalid query parameter syntax (e.g., malformed filter expressions) may result in API errors.
    • Using unsupported or misspelled property names in $select, $filter, or $orderby can cause the API to reject the request.
    • Pagination parameters ($top and $skip) must be numeric strings; non-numeric values may cause failures.

  • Error messages:

    • Authorization errors typically indicate invalid or expired credentials; re-authenticate or update credentials.
    • Query parameter errors usually return descriptive messages from the API; verify parameter syntax and supported fields.
    • Network or connectivity errors suggest checking internet connection or API endpoint availability.

Links and References

  • OData Query Options
  • Google API documentation for the specific service exposing settings (refer to your Google service's API docs for exact details).

Discussion