RD Station CRM Equipes icon

RD Station CRM Equipes

Consultar equipes no RD Station CRM

Actions2

Overview

This node allows users to interact with the "Equipe" (Team) resource in RD Station CRM. Specifically, it can retrieve information about teams either by listing all teams or by obtaining details of a single team using its ID. This is useful for workflows that need to integrate team data from RD Station CRM, such as syncing team info, reporting, or automating team-based actions.

For the Obter (Get) operation on the Equipe resource, the node fetches detailed information about a specific team identified by its ID.

Practical Example

  • Fetching details of a particular sales team by its ID to update internal records.
  • Automating notifications or tasks based on team attributes retrieved from RD Station CRM.

Properties

Name Meaning
ID da Equipe The unique identifier of the team to be retrieved. This is required for the "Obter" operation.

Output

The node outputs JSON data representing the team object returned by the RD Station CRM API. The structure corresponds directly to the API response for a single team, including all available fields describing the team.

The output format is:

{
  "json": {
    /* Team object properties as returned by RD Station CRM */
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for RD Station CRM to authenticate requests.
  • The node makes HTTP GET requests to the RD Station CRM API endpoint: https://crm.rdstation.com/api/v1/teams/{teamId}.
  • Proper configuration of the RD Station CRM API credentials within n8n is necessary.

Troubleshooting

  • Missing or invalid team ID: If the "ID da Equipe" property is empty or invalid, the node throws an error indicating that a valid team ID must be provided.
  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • API connectivity issues: Network problems or incorrect API URLs can cause request failures.
  • Handling errors gracefully: If "Continue On Fail" is enabled, errors will be returned as part of the output JSON instead of stopping the workflow.

Links and References

Discussion