Poli's listing nodes are responsible for searching and organizing information already registered in the system, such as accounts, channels, users, contacts, messages, teams, templates, tags, apps, and webhooks.
These nodes are very useful when you need to consult data before performing an action or when you want to automate flows that depend on specific information (for example: searching for a contact to then send a message).
In this tutorial, you will understand:
- Which listing nodes are currently available.
- What each node does.
- Which parameters or identifiers are necessary for the node to work.
- How to obtain the most used identifiers:
account_uuidandcontact_uuid.
⚠ Attention: Before using any listing node, it is mandatory to have an access token. This token will be used in all requests. If you don’t have one yet, see how to generate and save yours at this link/tutorial.
Listing Nodes Available in n8n
Currently, there are 10 listing nodes. Below, I explain in detail the functionality of each one and the requirements to use it:
1. List Accounts
- Function: Returns all companies (accounts) linked to the user's token.
- Required parameter: Only the token.
2. List Channels
- Function: Returns all communication channels linked to a specific company.
- Required parameter: Account UUID.
3. List and Search Users
- Function: Lists all users linked to a company.
- Required parameter: Account UUID.
4. List Messages from Contact ID
- Function: Lists all messages linked to a specific contact.
- Required parameter: Contact UUID.
5. List and Search Contacts
- Function: Returns all contacts of a company, along with their respective UUIDs.
- Required parameter: Account UUID.
6. List Teams
- Function: Returns all teams/departments linked to a company.
- Required parameter: Account UUID.
7. List Templates
- Function: Returns all templates created in the company.
- Practical application: These templates are later used to send messages via WhatsApp or other channels.
- Required parameter: Account UUID.
8. List Tags
- Function: Returns all tags created in the company.
- Practical application: The tag UUID can be used to associate it with specific contacts.
- Required parameter: Account UUID.
9. List Apps
- Function: Lists all apps created within the company, usually used for webhooks and integration tokens.
- Required parameter: Account UUID.
10. List Webhooks
- Function: Returns all webhooks linked to a specific app.
- Required parameter: Application UUID.
How to Obtain Account UUID, Contact UUID, and Application UUID
Account UUID and Application UUID
The Account UUID is the unique identifier of the company linked to your user.
The Application UUID is the unique identifier of the app linked to your company.
To obtain them, just follow this step-by-step/link (same process used to generate the token).
Contact UUID
The Contact UUID is the unique identifier of a specific contact.
It can be obtained through the List and Search Contacts node.
By using this node with the Account UUID, you will have access to the list of all contacts linked to the company. Within the response, each contact comes with its respective UUID.
This identifier is essential for nodes that need to directly refer to a contact, such as List Messages from Contact ID.
