RD Station CRM Funis icon

RD Station CRM Funis

Consultar funis e etapas no RD Station CRM

Actions4

Overview

This node integrates with the RD Station CRM API to retrieve information about sales pipelines ("funis") and their stages ("etapas"). Specifically, for the Etapa - Obter operation, it fetches detailed data about a single stage by its ID. This is useful when you want to get precise information about a particular stage in a sales pipeline, such as its name, position, or other metadata.

Common scenarios include:

  • Automating workflows that depend on the status or details of a specific sales stage.
  • Synchronizing stage data with other systems or dashboards.
  • Triggering actions based on stage properties or changes.

Example: You have a sales process with multiple stages and want to pull details about the "Negotiation" stage to display in a custom report or trigger follow-up tasks.

Properties

Name Meaning
ID da Etapa The unique identifier of the stage to be retrieved. This must be provided to fetch the specific stage details.

Output

The node outputs JSON data representing the stage object returned by the RD Station CRM API. This typically includes fields such as the stage's ID, name, position within the pipeline, and possibly other metadata related to the stage.

The output structure is:

{
  "id": "string",
  "name": "string",
  "position": "number",
  "pipeline_id": "string",
  // ... other stage-specific fields as returned by the API
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for RD Station CRM configured in n8n to authenticate requests.
  • Uses the RD Station CRM REST API endpoint at https://crm.rdstation.com/api/v1.
  • The node depends on network connectivity to RD Station CRM services.

Troubleshooting

  • Missing or invalid stage ID: If the "ID da Etapa" property is empty or invalid, the node will throw an error indicating that a valid stage ID must be provided.
  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions to access stage data.
  • Network issues: Connectivity problems or API downtime can cause request failures.
  • API rate limits: Excessive requests may be throttled by RD Station CRM; handle such errors by implementing retries or backoff strategies.
  • Error messages: Errors from the API are captured and returned in the output if "Continue On Fail" is enabled, allowing workflow continuation despite failures.

Links and References

Discussion