RD Station CRM
Read and write data in RD Station CRM. Create, get, update and list contacts (leads/people), deals (sales opportunities), organizations (companies), tasks, notes, and manage pipelines, stages, products, custom fields, sources, campaigns, loss reasons, users, teams and webhooks. Supports API v1 (private token) and API v2 (OAuth2). Usable as an AI Agent tool.
Actions66
- Campaign Actions
- Contact Actions
- Custom Field Actions
- Deal Actions
- Deal Product Actions
- Loss Reason Actions
- Note Actions
- Organization Actions
- Pipeline Actions
- Product Actions
- Source Actions
- Stage Actions
- Task Actions
- Team Actions
- User Actions
- Webhook Actions
Campaign → Create
AI-generatedOverview
This node allows users to create a marketing campaign in RD Station CRM. It supports both API v1 (using a private access token) and API v2 (using OAuth2) for authentication. Users can specify the campaign's name and optionally add a description. This node is useful for automating the creation of marketing campaigns, such as seasonal promotions or special event campaigns, directly within RD Station CRM from an n8n workflow.
Use Case Examples
- Creating a 'Black Friday 2026' campaign with a description 'Summer promotion for new leads'.
- Automating campaign creation as part of a marketing automation workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use: Access Token (API V1) or OAuth2 (API V2). This determines which RD Station CRM API version is used. |
| Name | The name of the marketing campaign to create, e.g., 'Black Friday 2026'. This is a required field. |
| Additional Fields | Optional additional fields for the campaign. Currently supports 'Description' to provide more details about the campaign, e.g., 'Summer promotion for new leads'. |
Output
JSON
id- The unique identifier of the created campaign.name- The name of the created campaign.description- The description of the created campaign, if provided.created_at- Timestamp when the campaign was created.updated_at- Timestamp when the campaign was last updated.
Dependencies
- Requires RD Station CRM API credentials: either an API key credential for API v1 or OAuth2 credentials for API v2.
Troubleshooting
- Common issues include authentication failures due to invalid or expired tokens. Ensure the correct authentication method is selected and credentials are valid.
- If the 'Name' field is missing or empty, the node will throw an error because the campaign name is required.
- API rate limits or network issues may cause request failures; retry or check API status if errors occur.