Overview
This node interacts with the RD Station CRM to manage notes (annotations) related to deals. Specifically, the "Listar" (List) operation under the "Nota" (Note) resource allows users to retrieve multiple notes from the CRM system based on various filtering and pagination parameters.
Common scenarios where this node is beneficial include:
- Fetching recent notes for a specific deal or user to display in dashboards or reports.
- Extracting notes within a date range for audit or analysis purposes.
- Integrating CRM notes into other systems or workflows by listing and processing them automatically.
For example, a sales manager might use this node to list all notes created by a particular salesperson within the last month, ordered by creation date descending, to review recent customer interactions.
Properties
| Name | Meaning |
|---|---|
| Limite | Maximum number of notes to return (number). |
| Página | Page number of results to return (number). |
| ID do Negócio | Filter notes by a specific deal ID (string). |
| ID do Usuário | Filter notes by the author user ID (string). |
| Data Inicial | Start date to filter notes (format YYYY-MM-DD) (string). |
| Data Final | End date to filter notes (format YYYY-MM-DD) (string). |
| Ordenação | Field to order the results by; currently only "Data de Criação" (creation date) is supported. |
| Direção da Ordenação | Direction of ordering: "Ascendente" (ascending) or "Descendente" (descending). |
Output
The output is an array of JSON objects representing the notes retrieved from RD Station CRM. Each item corresponds to one note and includes all fields returned by the CRM API for activities of type "note". The exact structure depends on the CRM's API response but typically includes identifiers, timestamps, text content, associated deal and user IDs, and metadata.
No binary data is output by this node.
Dependencies
- Requires an API key credential for RD Station CRM configured in n8n to authenticate requests.
- Uses the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1/activities. - The node relies on standard HTTP headers for JSON communication (
AcceptandContent-Typeset toapplication/json).
Troubleshooting
- Empty Results: If no notes are returned, verify that the filter parameters (deal ID, user ID, dates) are correct and that notes exist matching those criteria.
- Invalid Date Format: Ensure that
start_dateandend_dateare provided in theYYYY-MM-DDformat; otherwise, the API may reject the request. - API Authentication Errors: If authentication fails, check that the API key credential is correctly configured and has sufficient permissions.
- Pagination Issues: If expecting more results, adjust the
limitandpageparameters accordingly. - Error Messages: The node throws errors if required parameters are missing or if the API returns an error. Enabling "Continue On Fail" allows processing subsequent items even if some fail.