Poli icon

Poli

Node principal para interagir com a API da Poli

Actions22

Overview

This node interacts with the Poli API to list teams associated with a specific account. It allows users to retrieve paginated lists of teams, optionally filtering and ordering the results, and including additional related data fields.

Common scenarios where this node is beneficial include:

  • Managing or auditing teams within an organization by fetching their details.
  • Integrating team data into workflows for reporting or synchronization with other systems.
  • Searching for specific teams by name or other criteria.
  • Retrieving extended information about teams such as their status, visibility, users, or metadata.

Practical example:

  • A user wants to get all teams in an account, ordered by creation date, including the list of users in each team, to generate a report on team membership.

Properties

Name Meaning
Account UUID UUID of the account for which to list the teams (required).
Options Collection of optional parameters:
- Search Term to search for matching teams.
- Order Ordering of the results (e.g., ascending or descending by a field).
- Page Page number of the results to retrieve (default is 1).
- Per Page Number of results per page (default is 100).
- Query Raw query string to filter results (e.g., id=18&name=gabriel).
- Include Additional data to include in the response. Possible values: Key, Status, Visibility, Staging, Attributes, Users, Metadata.

Output

The node outputs JSON data representing the list of teams retrieved from the Poli API. The structure includes team details according to the requested options and included fields. If additional data like users or metadata is requested via the "Include" option, those will be nested within each team object.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Poli API.
  • The node depends on the Poli API service being accessible and properly configured.
  • No other external dependencies are indicated.

Troubleshooting

  • Error: Resource 'team' not found — This indicates the resource parameter was set incorrectly or the node's internal mapping failed. Ensure the resource is set to "team".
  • Error: Operation 'list' not found for resource 'team' — Indicates the operation parameter is invalid for the selected resource. Confirm that the operation is set to "list".
  • API authentication errors — Verify that the API key credential is correctly configured and has sufficient permissions.
  • Empty or incomplete results — Check the pagination settings (page and perPage) and any filters applied via search or query.
  • Including additional data fails — Some included fields may require specific permissions or may not be available depending on the account state.

Links and References

Discussion