RD Station CRM Equipes icon

RD Station CRM Equipes

Consultar equipes no RD Station CRM

Actions2

Overview

This node allows you to interact with the "Equipe" (Team) resource in RD Station CRM by listing teams or retrieving a specific team by its ID. It is useful for workflows that need to fetch team information from RD Station CRM, such as synchronizing team data, reporting on team statuses, or integrating team details into other systems.

A common scenario is to list all active teams with pagination and sorting options to display or process them in another system. Another use case is to get detailed information about a single team by providing its unique ID.

Properties

Name Meaning
Parâmetros de Listagem Collection of parameters to control the listing of teams:
- Limite Maximum number of teams to return
- Página Page number to return
- Ordenação Field to sort results by; options: Nome (name), Data de Criação (created_at)
- Direção da Ordenação Sort direction; options: Ascendente (ascending), Descendente (descending)
- Status Filter teams by status; options: Ativa (active), Inativa (inactive), Todas (all)

Output

The node outputs an array of JSON objects representing the teams retrieved from RD Station CRM.

  • For the Listar operation, the output JSON contains a list of teams according to the specified filters, pagination, and sorting.
  • For the Obter operation (not requested here), it would output the JSON object of a single team.

Each output item corresponds to one input item, paired by index.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with RD Station CRM.
  • The node makes HTTP requests to the RD Station CRM API endpoint at https://crm.rdstation.com/api/v1/teams.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Missing or invalid team ID: When using the "Obter" operation, if the team ID is not provided or invalid, the node throws an error indicating a valid team ID must be supplied.
  • API request failures: Network issues or invalid credentials can cause request failures. Ensure the API key credential is correctly configured and has sufficient permissions.
  • Pagination limits: Requesting pages beyond available data may return empty results; adjust the page and limit parameters accordingly.
  • If "continue on fail" is enabled, errors will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion