Actions22
- App Actions
- Account Actions
- Channel Actions
- Message Actions
- Template Actions
- Contact Actions
- Tag Actions
- User Actions
- Team Actions
- Webhook Actions
Overview
The node provides integration with the Poli API, specifically enabling interaction with various resources such as Apps, Accounts, Channels, Messages, Templates, Contacts, Tags, Users, Teams, and Webhooks. For the App resource with the List Apps operation, it allows users to retrieve a paginated list of apps associated with a specified account.
This node is beneficial in scenarios where you need to programmatically fetch and manage apps within an account on the Poli platform. For example, you might want to display all apps for an account in a dashboard, synchronize app data with another system, or filter apps based on specific criteria like status or visibility.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account whose apps you want to list. This is a required string input. |
| Options | A collection of optional parameters to refine the listing: |
| - Search | A search term to filter the apps by name or other searchable fields. |
| - Order | Defines the ordering of the results, e.g., -created_at to order by creation date descending. |
| - Page | The page number of results to fetch (pagination). Defaults to 1. |
| - Per Page | Number of items per page to return. Defaults to 50. |
| - Include | Additional related fields to include in the response. Possible values are: Status, Visibility, Attributes, Roles, Permissions, Attachments, Resources, Settings, Accounts, Metadata. Multiple can be selected. |
| - Query | A raw query string to apply custom filters, e.g., id=18&name=gabriel. |
Output
The node outputs JSON data representing the list of apps retrieved from the Poli API. The structure typically includes an array of app objects, each containing details such as app ID, name, status, visibility, attributes, roles, permissions, attachments, resources, settings, accounts, and metadata depending on the included fields requested.
If binary data were involved (not indicated here), it would represent files or attachments related to apps, but this operation focuses on JSON data output only.
Dependencies
- Requires an API key credential for authenticating requests to the Poli API.
- The node depends on the Poli API service being accessible and the provided account ID being valid.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
Common Issues:
- Invalid or missing Account ID will cause the request to fail.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Requesting pages beyond available data may return empty results.
- Using invalid query strings or unsupported include options may cause API errors.
Error Messages:
"Resource 'app' not found": Indicates the resource parameter was incorrect or missing."Operation 'list' not found for resource 'app'": Means the operation parameter was invalid.- Authentication errors usually mention unauthorized access; verify API credentials.
- Validation errors from the API may indicate malformed queries or invalid parameters.
To resolve these issues, ensure that:
- The Account ID is correct and exists.
- API credentials are properly configured and active.
- Optional parameters conform to expected formats.
- Pagination parameters are within valid ranges.
Links and References
- Poli API Documentation (general reference): [Insert actual Poli API docs URL if known]
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/
- REST API Pagination Best Practices: https://restfulapi.net/pagination-in-rest-api/
Note: The above summary is based solely on static analysis of the provided source code and property definitions.