RD Station CRM Contatos icon

RD Station CRM Contatos

Operações com contatos no RD Station CRM

Actions4

Overview

This node integrates with RD Station CRM to perform operations on contacts. Specifically, the "Listar" (List) operation under the "Contato" (Contact) resource allows users to retrieve a paginated list of contacts from their RD Station CRM account. It supports filtering, sorting, and searching by various contact attributes such as name, email, phone, job title, organization ID, and user ID.

Common scenarios for this node include:

  • Synchronizing contacts from RD Station CRM into another system.
  • Generating reports or dashboards based on filtered contact lists.
  • Automating workflows that require processing or analyzing contacts meeting specific criteria.

For example, you could use this node to fetch all contacts created in the last month, sorted by creation date descending, or to find contacts associated with a particular organization or user.

Properties

Name Meaning
Página Page number of the contact list to retrieve. Default is 1.
Limite Maximum number of contacts to return per request. Default is 20; maximum allowed is 200.
Ordenar Por Field to sort the contacts by. Options: Nome (name), Data de Criação (created_at), Data de Atualização (updated_at). Default is "name".
Direção Sort direction. Options: Ascendente (asc), Descendente (desc). Default is "asc".
Busca Search query string to filter contacts by name.
E-mail Filter contacts by email address.
Telefone Filter contacts by phone number.
Cargo Filter contacts by job title.
ID da Organização Filter contacts by the ID of the organization they belong to.
ID do Usuário Filter contacts by the ID of the user responsible for them.

Output

The node outputs an array of JSON objects representing the contacts retrieved from RD Station CRM. Each item corresponds to one contact and contains all the fields returned by the API, including but not limited to contact details like name, emails, phones, job title, organization ID, and custom fields if available.

No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "id": "contact_id",
  "name": "Contact Name",
  "emails": [
    {
      "email": "example@example.com",
      "type": "personal",
      "primary": true
    }
  ],
  "phones": [
    {
      "phone": "+1234567890",
      "type": "mobile"
    }
  ],
  "title": "Job Title",
  "organization_id": "org_id",
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2023-02-01T12:00:00Z"
}

Dependencies

  • Requires an API key credential for RD Station CRM configured in n8n to authenticate requests.
  • The node makes HTTP requests to the RD Station CRM API endpoint at https://crm.rdstation.com/api/v1/contacts.
  • Proper network connectivity to RD Station CRM API is necessary.

Troubleshooting

  • Missing or invalid API credentials: Ensure the RD Station CRM API key credential is correctly set up in n8n.
  • Invalid filter values: For example, providing a non-numeric value for "Página" or "Limite" may cause errors.
  • API rate limits or downtime: If the RD Station CRM API is unavailable or rate-limited, requests will fail.
  • Empty results: If filters are too restrictive or no contacts match, the output will be an empty array.
  • Error messages about required parameters: The node enforces required parameters like contact ID for other operations, but for listing, ensure page and limit are valid numbers.

To resolve errors, verify input parameters, check API credentials, and consult RD Station CRM API status.

Links and References

Discussion