Search contacts in RD Station CRM by partial name, exact email or exact phone.

Returns one line per contact: name, id, primary email, primary phone, job title. Use the returned id with rdcrm_get_contact for full details (including linked deals).

Use when: "find Maria's contact", "do we have someone with email x@y.com?". Don't use when: you want to create or edit a contact (use rdcrm_upsert_contact).

Get full details of one contact by ID: all emails and phones, title, notes, and the deals linked to the contact with their status (open/won/lost).

Get the contact ID from rdcrm_search_contacts first.

Create a contact, or update it if one already exists with the given email (matched by exact email).

Provide at least email and name. Phone, job title and notes are optional. Returns the contact id.

Use when: "add João (joao@acme.com) to the CRM", "update Maria's phone".

List deals with filters: status (open/won/lost/all, default open), pipeline, stage, owner, name, creation date range. Sorted by most recent first.

Returns one line per deal: name, id, stage, value, status, owner, last update. Use rdcrm_get_deal for full details.

Use when: "what deals are open?", "deals lost this month", "show João's pipeline".

Get full details of one deal by ID: status, stage, value, owner, rating, dates, linked contacts (with email/phone) and products.

Create a deal in a pipeline stage. Accepts the stage by ID or by name (stage_name, optionally with pipeline_name to disambiguate) — names are resolved automatically.

Optional: value (BRL), rating (1-5), owner (user_id or user by email/name), a contact to link (contact_email + contact_name), expected close date.

Use when: "create a deal for Acme in the Qualification stage worth R$5000".

Update a deal: move it to another stage (by ID or name), change owner, rename, set rating, expected close date, or pause/resume (hold).

Use when: "move the Acme deal to Negotiation", "assign this deal to Maria". Don't use when: marking a deal won or lost (use rdcrm_close_deal).

Mark a deal as won or lost. For lost deals, pass the reason by name (lost_reason) or ID (lost_reason_id) — names are resolved against the reasons configured in the account — plus an optional note.

Use when: "mark the Acme deal as won", "we lost the Beta deal because of price".

List tasks with filters: deal, assignee, status (pending/done/all, default pending), type (call, email, meeting, task, lunch, visit, whatsapp) and due-date range.

Returns one line per task: status, subject, id, type, due date, assignee, deal.

Use when: "what are my pending tasks?", "overdue follow-ups this week".

Create a task on a deal: subject, type (call, email, meeting, task, lunch, visit, whatsapp), due date and time, assignee. Note: free-plan accounts only allow type 'task'; other types return a 403 (paid feature).

The assignee can be given by user_id, by email/name in 'user' (resolved automatically), or omitted when the account has a single user.

Use when: "schedule a follow-up call on the Acme deal for Friday 10am".

Add a text note (annotation) to a deal's timeline.

The author can be given by user_id, by email/name in 'user', or omitted when the account has a single user.

Use when: "note on the Acme deal: client asked for a discount".

Aggregated health report of a sales pipeline: open deal count and value per stage (in funnel order), won/lost counts and win rate over a recent window (default 30 days), and stalled deals with no updates for N days (default 14).

Also the fastest way to discover the account's pipelines and stage names/IDs (errors list all options).

Use when: "how's my pipeline?", "where are deals stuck?", "sales summary for this month".