Poli icon

Poli

Node principal para interagir com a API da Poli

Actions22

Overview

The node provides integration with the Poli API, specifically enabling interaction with various resources such as accounts, contacts, apps, channels, messages, templates, tags, users, teams, and webhooks. For the Account resource with the List Accounts operation, it allows users to retrieve a list of accounts from the Poli platform.

This is useful in scenarios where you want to fetch account data for reporting, synchronization, or further processing within an n8n workflow. For example, you might use this node to pull all accounts matching certain criteria, paginate through large datasets, or include related information like status or metadata.

Properties

Name Meaning
Options A collection of optional parameters to customize the listing of accounts:
- Search: Text string to search accounts by name or other fields.
- Order: Specify ordering of results.
- Page: Page number for pagination (default 1).
- Per Page: Number of accounts per page (default 100).
- Query: Raw query string for advanced filtering (e.g., id=18&name=gabriel).
- Include: Select additional related data to include with each account. Options are: Status, Attributes, Organization, Account Channels, Addresses, Applications, Metadata.

Output

  • The output is a JSON array containing account objects retrieved from the Poli API.
  • Each account object includes standard account fields plus any additional included data as specified in the "Include" options.
  • The structure depends on the API response but typically contains identifiers, names, statuses, and related entities.
  • No binary data output is indicated for this operation.

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 additional environment variables or external services are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect query strings or unsupported filter parameters may result in empty responses or errors.
    • Pagination parameters out of range could lead to no data returned.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • "Resource 'account' não encontrado": Means the specified resource was not found; ensure the resource name is correct.
    • "Operação 'list' não encontrada para o resource 'account'": Indicates the operation is not available for the resource; verify operation spelling and availability.
    • API errors related to authentication or rate limits should be resolved by checking API keys and usage quotas.

Links and References

Discussion