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
Task → Create
AI-generatedSummary
Create a new task in RD Station CRM linked to a specific deal, specifying its subject, type, scheduled date and time, and optional details such as completion status, notes, and assigned users.
Inputs
- Authentication (required) — Choose between Access Token (API V1) or OAuth2 (API V2) for authenticating the API requests.
- Subject (required) — Title or subject describing the task (e.g., 'Call the client to confirm the proposal').
- Deal ID (required) — ID of the deal this task is linked to in RD Station CRM, obtained from a deal create or get operation.
- Type — Category of the activity, one of: call, email, lunch, meeting, task, visit, whatsapp. Defaults to 'task'.
- Date — Date the task is scheduled for in ISO 8601 format; only the date part is sent to RD Station CRM.
- Hour — Time of day the task is scheduled for, in 24-hour HH:MM format (e.g., 14:30).
- Additional Fields — Optional fields including 'Done' (boolean to mark task as completed), 'Notes' (free-text details), and 'User Names or IDs' (array of RD Station CRM user IDs assigned to the task).
Output shape
A JSON object representing the created task, as returned by RD Station CRM API.
The task payload is wrapped in a 'task' key in the API request body. Only the date part of 'Date' is sent, and 'Hour' is sent separately. User assignments accept multiple user IDs. The output's exact fields depend on the RD Station CRM API response.
Examples
Example 1: Create a meeting task scheduled for 2026-07-08 at 14:30 linked to a deal with ID '1234', assigned to users with IDs 'u1' and 'u2', marked as not done, with notes.
Use OAuth2 authentication, set Subject to the meeting title, specify dealId as '1234', Type as 'meeting', Date as '2026-07-08', Hour as '14:30', Done as false, Notes as desired, and User IDs ['u1','u2'].