Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nekt.com/llms.txt

Use this file to discover all available pages before exploring further.

RD Station CRM is a sales management platform that helps businesses organize and track their sales pipeline. It provides tools for managing contacts, deals, organizations, and sales activities to improve conversion rates and revenue. The RD Station CRM destination supports three operating modes:
  • Contacts - creates or updates contacts in the CRM.
  • Deals - creates or updates deals (sales opportunities) in the CRM.
  • Organizations - creates or updates organizations (companies) in the CRM.

​
1. Add your RD Station CRM access

  1. In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the RD Station CRM option from the list of connectors.
  2. Click Next and you’ll be prompted to add your access:
    • Authorization: Complete RD Station authorization to grant permissions for Nekt to load data into the CRM.
    • Mode: Select the operating mode for the connector:
      • Create/Update Contacts - maps your input table columns to contact fields and creates or updates contacts.
      • Create/Update Deals - maps your input table columns to deal fields and creates or updates deals.
      • Create/Update Organizations - maps your input table columns to organization fields and creates or updates organizations.
    • Enable partial success: Whether the connector should continue trying to sync records after one fails.
  3. Click Next.

​
2. Select your data to send

  1. The next step is letting us know which data you want to send. Select the layer and then the desired table.
    Tip: The table can be found more easily by typing its name.
  2. Click Next.

​
3. Map your columns

Map the columns from your input table to the corresponding RD Station CRM fields. The available destination fields depend on the mode you selected.

​
Create vs. update behavior

If you map a column to the _id destination field, the connector performs an update (PUT) on the existing record with that ID. If no _id is mapped, the connector creates a new record (POST).

​
Custom fields

RD Station CRM supports custom fields on contacts, deals, and organizations. To map a column to a custom field, prefix the field slug with @ in the destination field (e.g., @cpf, @erp_id).

​
Contacts mode

In contacts mode, each row in your input table represents a contact to create or update. Available destination fields:
Destination fieldDescription
_idCRM contact ID (for updates only)
nameContact full name
emailContact email address
phoneContact phone number
job_titleContact job title
organization_idID of the associated organization
Example input table (contacts mode):
full_namecontact_emailphone_numbercpf
Maria Silvamaria@example.com+55 11 91234-5678111.111.111-11
Joao Santosjoao@example.com+55 21 99876-5432222.222.222-22
Column mapping: full_name -> name, contact_email -> email, phone_number -> phone, cpf -> @cpf.

​
Deals mode

In deals mode, each row in your input table represents a deal to create or update. Available destination fields:
Destination fieldDescription
_idCRM deal ID (for updates only)
nameDeal name (required for creation)
statusDeal status (must be ongoing for creation)
contact_idID of the associated contact
organization_idID of the associated organization
stage_idID of the deal stage
pipeline_idID of the sales pipeline
owner_idID of the deal owner (user)
campaign_idID of the associated campaign
expected_close_dateExpected close date (ISO 8601 format)
ratingNumeric rating/classification
When creating deals, the status field must be set to ongoing. The RD Station CRM API only allows creating deals with this status.
Example input table (deals mode - create):
deal_nameorg_idstageamount
Credito PJ 0016621a1b2c3d4e5f6789056786621a1b2c3d4e5f67890000150000
Credito PF 0026621a1b2c3d4e5f6789056796621a1b2c3d4e5f67890000115000
Column mapping: deal_name -> name, org_id -> organization_id, stage -> stage_id, amount -> @valor_credito.

​
Organizations mode

In organizations mode, each row in your input table represents an organization to create or update. Available destination fields:
Destination fieldDescription
_idCRM organization ID (for updates only)
nameOrganization name
websiteOrganization website URL
phoneOrganization phone number
owner_idID of the organization owner (user)
segment_idsSegment IDs to associate
Example input table (organizations mode):
company_namecompany_websitecnpj
Empresa ABC Ltdahttps://empresaabc.com.br11.111.111/0001-11
Tech Corp SAhttps://techcorp.com.br22.222.222/0001-22
Column mapping: company_name -> name, company_website -> website, cnpj -> @cnpj.

​
4. Configure your RD Station CRM data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
  2. To define your Trigger, consider how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).
  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!
  2. You can view your new destination on the Destinations page. Now, for you to be able to see it on RD Station CRM, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on RD Station CRM.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!