Overview
This node allows you to query user data from the RD Station CRM system. It supports listing multiple users with various filtering and sorting options, as well as retrieving details of a single user by their ID.
Common scenarios where this node is useful include:
- Synchronizing user data from RD Station CRM into other systems.
- Generating reports or dashboards based on user attributes such as role, status, or team.
- Automating workflows that depend on user information, like sending notifications to active users or managers.
For example, you could use this node to list all active users in a specific team, ordered by their email address, or fetch detailed information about a particular user by their unique ID.
Properties
| Name | Meaning |
|---|---|
| Parâmetros de Listagem (listParameters) | Collection of parameters to customize the user listing: |
| - Limite (limit) | Maximum number of users to return |
| - Página (page) | Page number of results to retrieve |
| - Ordenação (order) | Field to sort results by: name or email |
| - Direção da Ordenação (direction) | Sort direction: asc (ascending) or desc (descending) |
| - ID da Equipe (team_id) | Filter users by a specific team ID |
| - Papel/Função (role) | Filter users by role/function: admin, user, or manager |
| - Status (status) | Filter users by account status: active, inactive, or pending |
| ID do Usuário (userId) | The unique identifier of a user to retrieve (used only when fetching a single user) |
Output
The node outputs an array of items, each containing a json field with the user data returned from RD Station CRM.
- For the Listar (getAll) operation, the output JSON contains a list of users matching the specified filters and pagination.
- For the Obter (get) operation, the output JSON contains the details of a single user identified by the provided user ID.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the RD Station CRM API.
- The node makes HTTP GET requests to the RD Station CRM endpoint at
https://crm.rdstation.com/api/v1/users. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Missing or invalid user ID: When using the "Obter" operation, if the user ID is not provided or invalid, the node throws an error indicating that a valid user ID must be supplied.
- API request failures: Network issues, invalid credentials, or permission problems may cause the API requests to fail. Check your API key and network connectivity.
- Empty results: If filters are too restrictive (e.g., filtering by a non-existent team or role), the node may return an empty list.
- Pagination limits: Ensure the
limitandpageparameters are set correctly to avoid missing data or excessive API calls.
If the node is configured to continue on failure, errors will be included in the output JSON under an error field instead of stopping execution.