Actions22
- App Actions
- Account Actions
- Channel Actions
- Message Actions
- Template Actions
- Contact Actions
- Tag Actions
- User Actions
- Team Actions
- Webhook Actions
Overview
This node interacts with the Poli API to list tags associated with a specific account. It is useful for retrieving and managing tag data within an account, such as filtering or organizing contacts or other entities by tags. Typical use cases include fetching all tags to display in a UI, syncing tags with another system, or applying logic based on tag attributes.
For example, you might use this node to:
- Retrieve all tags for an account to show them in a dashboard.
- Search for tags matching certain criteria.
- Paginate through large sets of tags.
- Include additional related information like status, category, or metadata about each tag.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique identifier of the account whose tags you want to list. |
| Options | Additional parameters to refine the tag listing: |
| - Search | A string to search tags by name or other fields. |
| - Order | The order in which to sort the results (e.g., ascending or descending). |
| - Page | The page number to retrieve when paginating results (default is 1). |
| - Per Page | Number of tags to return per page (default is 100). |
| - Query | A raw query string for advanced filtering (e.g., id=18&name=gabriel). |
| - Include | Related data to include with each tag. Options are: Status, Category, Attributes, Contacts, Metadata. Default includes Attributes. |
Output
The output JSON contains an array of tag objects retrieved from the Poli API. Each tag object may include:
- Basic tag details such as ID, name, and description.
- Additional included data depending on the "Include" options selected, such as status, category, attributes, contacts linked to the tag, and metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Poli API via an API key credential configured in n8n.
- The node depends on the Poli API being accessible and the provided Account ID being valid.
- Pagination and filtering depend on the Poli API's support for these features.
Troubleshooting
- Error: Resource 'tag' not found — This indicates the resource parameter was incorrect or missing; ensure "Tag" is selected as the resource.
- Error: Operation 'list' not found for resource 'tag' — This means the operation parameter is invalid; verify that "List Tags" is chosen.
- API authentication errors — Check that the API key credential is correctly set up and has permissions to access the account's tags.
- Empty results — Confirm the Account ID is correct and that tags exist for that account. Also, check if filters or queries are too restrictive.
- Pagination issues — If not all tags appear, try increasing the "Per Page" value or iterating over pages using the "Page" property.
Links and References
- Poli API Documentation (general reference for tag endpoints)
- n8n Documentation on Credentials and API integrations