Actions5
- Negociação Actions
Overview
This node integrates with RD Station CRM to manage sales deals ("Negociações"). Specifically, the "Listar" (List) operation under the "Negociação" resource allows users to retrieve a list of deals from their CRM account. It supports extensive filtering and pagination options, enabling users to query deals based on various criteria such as name, status, associated user, pipeline stage, date ranges, and more.
Typical use cases include:
- Fetching all open or closed deals within a specific time period.
- Retrieving deals assigned to a particular sales representative.
- Listing deals filtered by their current sales funnel stage or campaign.
- Paginating through large sets of deals for reporting or synchronization purposes.
For example, a sales manager could use this node to pull all deals won in the last quarter, sorted by closing date, to analyze team performance.
Properties
| Name | Meaning |
|---|---|
| Página | Page number of the results to fetch. Useful for paginating through deal lists. |
| Limite | Maximum number of deals per page. The maximum allowed is 200. |
| Ordenar Por | Field used to sort the results. Default is created_at. |
| Direção | Sort direction: Ascendente (ascending) or Descendente (descending). Default is descending. |
| Nome | Filter deals by name (partial match). |
| Nome Exato | If true, filters deals by exact name match instead of partial. |
| Status Ganho/Perdido | Filter deals by status: Ganhas (won), Perdidas (lost), or Em Aberto (open). |
| Fechadas | Filter deals by whether they are closed (Ganhas/Perdidas) or open/paused (Em Aberto/Pausadas). |
| Pausadas | If true, returns only paused deals. |
| ID do Usuário | Filter deals by the responsible user's ID. |
| ID da Etapa | Filter deals by the sales funnel stage ID. |
| ID do Funil | Filter deals by the sales funnel (pipeline) ID. |
| ID da Empresa | Filter deals by associated company ID. |
| ID do Motivo de Perda | Filter deals by the reason ID for lost deals. |
| ID da Campanha | Filter deals by campaign ID. |
| ID do Usuário que Fechou | Filter deals by the user ID who closed the deal. |
| Presença de Produtos | Filter deals by product presence: false (no products), true (with products), or a comma-separated list of product IDs. |
| Próxima Página | Token to fetch the next page of results, useful for cursor-based pagination. |
| Período de Fechamento | Boolean flag to filter deals by closing date range. |
| Período de Criação | Boolean flag to filter deals by creation date range. |
| Período de Previsão | Boolean flag to filter deals by predicted closing date range. |
| Data Inicial | Start datetime for the selected period filter(s). Format example: 2020-12-14T15:00:00. |
| Data Final | End datetime for the selected period filter(s). Format example: 2020-12-14T15:00:00. |
Output
The node outputs an array of JSON objects representing the deals retrieved from RD Station CRM. Each item corresponds to one deal and contains all fields returned by the API, including metadata such as deal ID, name, status, associated users, dates, pipeline stages, and any other deal attributes.
If pagination tokens are used, the output may also include information to fetch subsequent pages.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for RD Station CRM configured in n8n.
- The node makes authenticated HTTP requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1. - Proper permissions on the API key are necessary to read deal data.
Troubleshooting
- Missing or invalid API credentials: The node will fail if the API key is not set or invalid. Ensure the credential is correctly configured.
- Invalid or missing required parameters: For listing deals, most parameters are optional, but if you specify filters, ensure they are valid (e.g., page numbers > 0, limit ≤ 200).
- API rate limits or network errors: The node may throw errors if the RD Station CRM API rate limits are exceeded or if there are connectivity issues. Retry after some time or check network settings.
- Incorrect date formats: Period filters require ISO 8601 datetime strings. Invalid formats may cause errors or no results.
- Empty results: If filters are too restrictive, the node may return empty arrays. Try loosening filters or checking the data in RD Station CRM.