RD Station CRM icon

RD Station CRM

Integração com RD Station CRM API v2 - API v2 completa

Actions64

Contato → Criar

AI-generated

Summary

Creates a new contact in RD Station CRM (API v2) via POST to /contacts, with optional emails, phones, social profiles, LGPD legal bases and custom fields. Returns the created contact.

Inputs

  • contactName (required) — Contact name. Sent as name; overridden if 'Nome' is set in Campos do Contato.
  • contactEmails — Multiple email entries, sent as emails: [{email}].
  • contactPhones — Multiple phone entries with number and type (cellphone, work, home, fax; default cellphone). A leading '+' is stripped from the number.
  • contactFields — Optional extras: Nome (overrides contact name), Cargo (job_title), Data de Nascimento (sent as YYYY-MM-DD), ID da Empresa (organization_id).
  • socialProfiles — Entries of type (facebook, linkedin, twitter, instagram, skype) and username/URL. Each is sent as a top-level key named after the type, e.g. linkedin: username. Entries missing either value are skipped.
  • legalBases — LGPD consent records, each with category (communications/data_processing), type (consent, legitimate_interest, contract, etc.) and status (granted/declined). Sent as legal_bases.
  • customFields — Custom fields for contacts, chosen from a list loaded from the account (by slug), each with a string value. Sent as a custom_fields object keyed by slug.

Output shape

The created contact record as returned by the API (the data object of the response), one output item per input item.

Empty values are stripped from the request body before sending. With 'Continue On Fail' enabled, failed items return an item with an error message instead of stopping the run. Authentication uses the rdStationCrmOAuth2Api credential.

Examples

Example 1: Create a lead contact from a form submission with email and mobile phone

contactName = {{$json.name}}; contactEmails: add one email; contactPhones: number {{$json.phone}}, type Celular

Example 2: Register a contact with LGPD consent and a LinkedIn profile

contactName set; legalBases: category Comunicações, type Consentimento, status Concedido; socialProfiles: LinkedIn + profile URL

Links

Discussion