RD Station CRM Negociações icon

RD Station CRM Negociações

Operações com negociações no RD Station CRM

Actions5

Overview

This node integrates with RD Station CRM to perform operations on sales deals ("Negociações"). It allows users to create, update, list, and retrieve individual deals, as well as list contacts associated with a specific deal. This is useful for automating sales pipeline management, syncing deal data between systems, or enriching CRM data within workflows.

For the Obter (Get) operation on the Negociação (Deal) resource, the node fetches detailed information about a single deal by its ID. This is beneficial when you need to retrieve up-to-date deal details for reporting, decision-making, or further processing in an automation workflow.

Example use cases:

  • Fetching a deal’s current status and details after a webhook triggers on deal updates.
  • Retrieving deal information to enrich customer profiles or trigger follow-up actions.
  • Integrating deal data into dashboards or other business tools.

Properties

Name Meaning
ID da Negociação The unique identifier of the deal to retrieve. This property is required for the "Obter" operation.

Output

The node outputs a JSON object representing the deal's data as returned by the RD Station CRM API. The structure includes all available fields of the deal such as name, stage, user responsible, rating, dates, status, custom fields, associated campaigns, organization, products, and contacts if applicable.

The output is structured as:

{
  "json": {
    /* Deal object with all its properties */
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is output by this node.

Dependencies

  • Requires an API key credential for RD Station CRM configured in n8n.
  • Uses the RD Station CRM REST API endpoint https://crm.rdstation.com/api/v1.
  • The node depends on proper authentication and permissions to access deal data via the API.

Troubleshooting

  • Missing or invalid deal ID: The node throws an error if the "ID da Negociação" property is empty or not provided for the "Obter" operation. Ensure the deal ID is correctly set.
  • API authentication errors: If the API key or token is invalid or expired, requests will fail. Verify credentials in n8n settings.
  • Network or API downtime: Temporary connectivity issues or RD Station CRM service outages can cause request failures.
  • Permission issues: The authenticated user must have permission to read deal data; otherwise, the API may return authorization errors.
  • Unexpected response format: If RD Station CRM changes their API, the node might receive unexpected data structures.

To resolve errors:

  • Double-check the deal ID input.
  • Confirm API credentials are valid and have necessary scopes.
  • Review API limits and usage quotas.
  • Check RD Station CRM status pages for outages.

Links and References

Discussion