Overview
This node allows you to interact with campaigns in the RD Station CRM system. Specifically, it supports operations to either list all campaigns or retrieve details of a single campaign by its ID. This is useful for marketing automation workflows where you need to fetch campaign data for reporting, synchronization, or triggering further actions based on campaign attributes.
Practical examples:
- Automatically retrieving detailed information about a specific campaign to update your internal dashboards.
- Listing all active campaigns to filter and process them in subsequent workflow steps.
- Integrating campaign data into other systems such as CRMs or analytics platforms.
Properties
| Name | Meaning |
|---|---|
| Recurso | The resource to work with; here, only "Campanha" (campaign) is available. |
| Operação | The operation to perform on the resource: |
| - Listar (getAll): List all campaigns | |
| - Obter (get): Get a campaign by its ID | |
| ID da Campanha | The unique identifier of the campaign to retrieve (required when using the "Obter" operation). |
| Parâmetros de Listagem | Parameters to filter and paginate the list of campaigns (used with "Listar" operation): |
| - Limite: Maximum number of campaigns to return | |
| - Página: Page number to return | |
| - Ordenação: Field to order results by ("Nome" or "Data de Criação") | |
| - Direção da Ordenação: Ascending or Descending | |
| - Status: Filter campaigns by status ("Ativa", "Inativa", or "Todas") | |
| - Termo de Busca: Search term to filter campaigns by name |
Output
The node outputs an array of JSON objects corresponding to the campaigns retrieved:
- For the Obter operation, the output JSON contains the detailed data of the specified campaign.
- For the Listar operation, the output JSON contains a list of campaigns matching the filter criteria.
Each output item is paired with the input item index it corresponds to.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the RD Station CRM API.
- The node makes HTTP requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Missing or invalid campaign ID: When using the "Obter" operation, if the campaign ID is not provided or invalid, the node throws an error indicating that a valid campaign ID is required.
- API request failures: Network issues or invalid credentials can cause request failures. Ensure the API key credential is correctly configured and has sufficient permissions.
- Empty results on listing: If filters are too restrictive (e.g., status or search term), the list operation may return no campaigns.
- Continue on Fail: If enabled, the node will continue processing remaining items even if some fail, returning error messages in the output JSON.
Links and References
- RD Station CRM API Documentation
- n8n HTTP Request Node Documentation (for understanding how API calls are made)