Connect Nuvemshop with RD Station CRM
Unlock the superpowers of Nuvemshop + RD Station CRM and automate your tasks without having to write a single line of code.
Nuvemshop and RD Station CRM
your way
Check out the available triggers and actions in the automation of apps Nuvemshop + RD Station CRM
Sale created
With each sale created on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Sale created
With each sale created on NuvemshopTrigger
Order: ID
Order: Store ID
Customer: Email
Customer: Name
Customer: Telephone
Customer: CPF/CNPJ
Order: Numeric ID
Order: Total discount amount
Order: Total price (excluding shipping)
Order: Total price (including shipping and discounts)
Order: Total price (in US dollars)
Order: Currency
Order: Language used by the customer
Order: Origin
Order: Total weight, in kilograms
Order: Status
Order: Payment status
Order: URL of the page that led to the purchase
Customer: Identifier
Customer: Name
Customer: Email
Customer: Identification (CPF/CNPJ)
Customer: Phone number
Order: Notes from the store owner
Shipping address: Street
Shipping address: City
Shipping address: Country
Shipping address: Neighborhood
Shipping address: Name
Shipping address: Number
Shipping address: Phone
Shipping address: State
Shipping address: Postal code
Customer: Type
Customer: Trade name
Customer: Business name
Customer: Fiscal regime
Customer: Invoice use
Customer: Document type
Customer: Accepts marketing actions
Billing: Name
Billing: Phone number
Billing address: Street
Billing address: Number
Billing address: Floor
Billing address: Neighborhood
Billing address: Postal code
Billing address: City
Billing address: State
Billing address: Country code
Billing: Customer type
Billing: Company name
Billing: Trade name
Billing: State registration
Billing: Tax regime (used only in es_MX)
Billing: Invoice usage (used only in es_MX)
Billing: Document type
Delivery: Minimum number of business days
Delivery: Maximum number of business days
Delivery: Owner's shipping cost
Delivery: Customer's shipping cost
Delivery: Shipping method used
Delivery: Customer's shipping option
Delivery: Customer's shipping option code
Delivery: Carrier shipping option reference
Delivery: Tracking number
Delivery: Tracking URL
Delivery: 'ship' or 'pickup'
Delivery: Store branch (in case of pickup)
Delivery: Carrier name
Delivery: Shipping status
Delivery address: Street
Delivery address: City
Delivery address: Country
Delivery address: Neighborhood
Delivery address: Name
Delivery address: Number
Delivery address: Phone
Delivery address: State
Delivery address: Postal code
Creation date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Creation date (in the format: DD-MM-YYYY HH:MM:SS)
Creation time
Creation date
Update date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Update date (in the format: DD-MM-YYYY HH:mm:ss)
Update time
Update date
Closing date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Closing date (in the format: DD-MM-YYYY HH:mm:ss)
Closing time
Closing date
Date the sale was marked as viewed (in ISO format: YYYY-MM-DDTHH:mm:ss:sss)
Date when the sale was marked as viewed (in the format: DD-MM-YYYY HH:mm )
Time when the sale was marked as viewed
Date when the sale was marked as viewed
Sale shipping date (in the ISO format: YYYY-MM-DDTHH:mm:sssZ)
Sale shipping date (in the format: DD-MM-YYYY HH:mm )
Sale shipping time
Sale shipping date
Payment date (in the format: YYYY-MM-DDTHH:mm:sss)
Payment date (in the format: DD-MM-YYYY HH:mm )
Payment time
Payment date
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products: SKU-Name-Quantity-Price
Created opportunity
For each opportunity created on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created opportunity
For each opportunity created on RD Station CRMTrigger
Deal's ID
Opportunity Name
Responsible User
Responsible User Email
Sales pipeline
Sales pipeline stage
Contact name
Contact Position
Contact Email
Contact Phone
Contact's Birthday
Campaign Name
Source Name
Reason for Loss
Company Name
Company's adress
Company user id number
Company username
Company URL
Company segments (comma separated)
Seller team ID (separated by comma)
Organization contact emails (comma separated)
Opportunity tasks (separated by commas and line breaks)
Opportunity notes (separated by commas and line breaks)
Last opportunity note
Company ID
Product names (separated by commas)
Product descriptions (comma separated)
Product IDs (separated by commas)
Product quantities (separated by comma)
Product prices (separated by comma)
Product Names, Descriptions, Quantities and Prices (separated by comma)
Total Gross Products
Total Discount
Unique amount
Recurring amount
Total amount
Qualification
Opportunity Win
Paused Opportunity
Creation date
Closing date
Closing Forecast
Created At in the format 'yyyy-mm-dd'
Created At in the format 'dd/mm/yyyy'
Creation date formatted in 'yyyy-mm-dd HH:mm:ss'
Closed At in the format 'yyyy-mm-dd'
Closed At in the format 'dd/mm/yyyy'
Closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Prediction date in the format 'yyyy-mm-dd'
Prediction date in the format 'dd/mm/yyyy'
Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Date and time the opportunity entered the selected Stage
Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'
Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'
Opportunity moved to specific stage in pipeline
For each opportunity moved to a certain stage in the RD Station CRM funnelHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity moved to specific stage in pipeline
For each opportunity moved to a certain stage in the RD Station CRM funnelTrigger
Deal's ID
Opportunity Name
Responsible user name
Email of the responsible user
Sales pipeline
Sales pipeline stage
Contact name
Contact position
Contact Email
Contact Phone
Contact's Birthday
Campaign Name
Source Name
Reason for Loss
Company Name
Company's adress
Company user id number
Company username
Company URL
Company segments (comma separated)
Seller team ID (separated by comma)
Organization contact emails (comma separated)
Opportunity tasks (separated by commas and line breaks)
Opportunity notes (separated by commas and line breaks)
Last opportunity note
Company ID
Product names (separated by comma)
Product descriptions (comma separated)
Product IDs (separated by comma)
Product quantities (separated by commas)
Product prices (separated by comma)
Product names, descriptions, quantities and prices (separated by commas)
Gross total of products
Full discount
Unique amount
Recurring amount
Total amount
Qualification
Negotiation Wins
Paused Trading
Creation date
Closing date
Estimated closing date
Created At in the format 'yyyy-mm-dd'
Created At in the format 'dd/mm/yyyy'
Creation date formatted in 'yyyy-mm-dd HH:mm:ss'
Closed At in the format 'yyyy-mm-dd'
Closed At in the format 'dd/mm/yyyy'
Closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Prediction date in the format 'yyyy-mm-dd'
Prediction date in the format 'dd/mm/yyyy'
Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Date and time the opportunity entered the selected Stage
Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'
Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'
Paid sale
For each paid sale on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Paid sale
For each paid sale on NuvemshopTrigger
Order: ID
Order: Store ID
Customer: Email
Customer: Name
Customer: Telephone
Customer: CPF/CNPJ
Order: Numeric ID
Order: Total discount amount
Order: Total price (excluding shipping)
Order: Total price (including shipping and discounts)
Order: Total price (in US dollars)
Order: Currency
Order: Language used by the customer
Order: Origin
Order: Total weight, in kilograms
Order: Status
Order: Payment status
Order: URL of the page that led to the purchase
Customer: Identifier
Comprador: Nome
Customer: Email
Customer: Identification (CPF/CNPJ)
Customer: Phone number
Order: Notes from the store owner
Shipping address: Street
Shipping address: City
Shipping address: Country
Shipping address: Neighborhood
Shipping address: Name
Shipping address: Number
Shipping address: Phone
Shipping address: State
Shipping address: Postal code
Customer: Type
Customer: Trade name
Customer: Business name
Customer: Fiscal regime
Customer: Invoice use
Customer: Document type
Customer: Accepts marketing actions
Billing: Name
Billing: Phone number
Billing address: Street
Billing address: Number
Billing address: Floor
Billing address: Neighborhood
Billing address: Postal code
Billing address: City
Billing address: State
Billing address: Country code
Billing: Customer type
Billing: Company name
Billing: Trade name
Billing: State registration
Billing: Tax regime (used only in es_MX)
Billing: Invoice usage (used only in es_MX)
Billing: Document type
Delivery: Minimum number of business days
Delivery: Maximum number of business days
Delivery: Owner's shipping cost
Delivery: Customer's shipping cost
Delivery: Shipping method used
Delivery: Customer's shipping option
Delivery: Customer's shipping option code
Delivery: Carrier shipping option reference
Delivery: Tracking number
Delivery: Tracking URL
Delivery: 'ship' or 'pickup'
Delivery: Store branch (in case of pickup)
Delivery: Carrier name
Delivery: Shipping status
Delivery address: Street
Delivery address: City
Delivery address: Country
Delivery address: Neighborhood
Delivery address: Name
Delivery address: Number
Delivery address: Phone
Delivery address: State
Delivery address: Postal code
Creation date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Creation date (in the format: DD-MM-YYYY HH:MM:SS)
Creation time
Creation date
Update date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Update date (in the format: DD-MM-YYYY HH:mm:ss)
Update time
Update date
Closing date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Closing date (in the format: DD-MM-YYYY HH:mm:ss)
Closing time
Closing date
Date the sale was marked as viewed (in ISO format: YYYY-MM-DDTHH:mm:ss:sss)
Date when the sale was marked as viewed (in the format: DD-MM-YYYY HH:mm )
Time when the sale was marked as viewed
Date when the sale was marked as viewed
Sale shipping date (in the ISO format: YYYY-MM-DDTHH:mm:sssZ)
Sale shipping date (in the format: DD-MM-YYYY HH:mm )
Sale shipping time
Sale shipping date
Payment date (in the format: YYYY-MM-DDTHH:mm:sss)
Payment date (in the format: DD-MM-YYYY HH:mm )
Payment time
Payment date
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products: SKU-Name-Quantity-Price
Lost opportunity
For each closed deal lost on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost opportunity
For each closed deal lost on RD Station CRMTrigger
Deal's ID
Opportunity Name
Responsible user
Email of the responsible user
Sales pipeline
Sales pipeline stage
Contact name
Contact position
Contact email
Contact phone
Contact's birthday
Campaign Name
Source Name
Reason for Loss
Company Name
Company's adress
Company user id number
Company username
Company URL
Organization segments (comma separated)
Seller team ID (separated by comma)
Organization contact emails (comma separated)
Opportunity tasks (separated by commas and line breaks)
Opportunity notes (separated by commas and line breaks)
Last opportunity note
Company ID
Product names (separated by commas)
Product descriptions (comma separated)
Product IDs (separated by commas)
Product quantities (separated by comma)
Product prices (separated by comma)
Product names, descriptions, quantities and prices (separated by commas)
Gross total of products
Full discount
Unique Amount
Recurring Amount
Total amount
Qualification
Opportunity Win
Paused Trading
Creation date
Closing date
Estimated closing date
Created At in the format 'yyyy-mm-dd'
Created At in the format 'dd/mm/yyyy'
Creation date formatted in 'yyyy-mm-dd HH:mm:ss'
Closed At in the format 'yyyy-mm-dd'
Closed At in the format 'dd/mm/yyyy'
Closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Prediction date in the format 'yyyy-mm-dd'
Prediction date in the format 'dd/mm/yyyy'
Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Date and time the opportunity entered the selected Stage
Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'
Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'
For every task created
For each task created on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
For every task created
For each task created on RD Station CRMTrigger
Task ID
Task type
Task subject
Task-related opportunity name
Task-related opportunity pipeline stage name
Task-related opportunity creation date
Total opportunity amount related to the task
Task date and time
Task's date and time (BR timezone)
Task date
Task time
Task notes
Task completion date
Name of the company related to the task
Address of the company related to the task
Names of contacts related to the task (separated by commas)
Job titles of contacts related to the task, separated by commas
Emails from contacts related to the task, separated by a comma and vertical bar
Contact emails related to the task, separated by commas
Telephone numbers of contacts related to the task, separated by commas
Names, positions, emails and telephone numbers of contacts related to the task, separated by commas
Name of users related to the task
Email of users related to the task
Task completion status
Cancelled sale
For each cancelled sale on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cancelled sale
For each cancelled sale on NuvemshopTrigger
Cancellation date (in the format ISO: YYYY-MM-DDTHH:mm:sss)
Cancellation date (in the format: DD-MM-YYYY HH:mm:ss)
Cancellation time
Cancellation date
Order: Reason for cancellation by the store
Order: ID
Order: Store ID
Customer: Email
Customer: Name
Customer: Telephone
Customer: CPF/CNPJ
Order: Numeric ID
Order: Total discount amount
Order: Total price (excluding shipping)
Order: Total price (including shipping and discounts)
Order: Total price (in US dollars)
Order: Currency
Order: Language used by the customer
Order: Origin
Order: Total weight, in kilograms
Order: Status
Order: Payment status
Order: URL of the page that led to the purchase
Customer: Identifier
Customer: Name
Customer: Email
Customer: Identification (CPF/CNPJ)
Customer: Phone number
Order: Notes from the store owner
Shipping address: Street
Shipping address: City
Shipping address: Country
Shipping address: Neighborhood
Shipping address: Name
Shipping address: Number
Shipping address: Phone
Shipping address: State
Shipping address: Postal code
Customer: Type
Customer: Trade name
Customer: Business name
Customer: Fiscal regime
Customer: Invoice use
Customer: Document type
Customer: Accepts marketing actions
Billing: Name
Billing: Phone number
Billing address: Street
Billing address: Number
Billing address: Floor
Billing address: Neighborhood
Billing address: Postal code
Billing address: City
Billing address: State
Billing address: Country code
Billing: Customer type
Billing: Company name
Billing: Trade name
Billing: State registration
Billing: Tax regime (used only in es_MX)
Billing: Invoice usage (used only in es_MX)
Billing: Document type
Delivery: Minimum number of business days
Delivery: Maximum number of business days
Delivery: Owner's shipping cost
Delivery: Customer's shipping cost
Delivery: Shipping method used
Delivery: Customer's shipping option
Delivery: Customer's shipping option code
Delivery: Carrier shipping option reference
Delivery: Tracking number
Delivery: Tracking URL
Delivery: 'ship' or 'pickup'
Delivery: Store branch (in case of pickup)
Delivery: Carrier name
Delivery: Shipping status
Delivery address: Street
Delivery address: City
Delivery address: Country
Delivery address: Neighborhood
Delivery address: Name
Delivery address: Number
Delivery address: Phone
Delivery address: State
Delivery address: Postal code
Creation date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Creation date (in the format: DD-MM-YYYY HH:MM:SS)
Creation time
Creation date
Update date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Update date (in the format: DD-MM-YYYY HH:mm:ss)
Update time
Update date
Closing date (in ISO format: YYYY-MM-DDTHH:mm:sss)
Closing date (in the format: DD-MM-YYYY HH:mm:ss)
Closing time
Closing date
Date the sale was marked as viewed (in ISO format: YYYY-MM-DDTHH:mm:ss:sss)
Date when the sale was marked as viewed (in the format: DD-MM-YYYY HH:mm )
Time when the sale was marked as viewed
Date when the sale was marked as viewed
Sale shipping date (in the ISO format: YYYY-MM-DDTHH:mm:sssZ)
Sale shipping date (in the format: DD-MM-YYYY HH:mm )
Sale shipping time
Sale shipping date
Payment date (in the format: YYYY-MM-DDTHH:mm:sss)
Payment date (in the format: DD-MM-YYYY HH:mm )
Payment time
Payment date
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products: SKU-Name-Quantity-Price
Opportunity marked as sale
For each opportunity marked as sale on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity marked as sale
For each opportunity marked as sale on RD Station CRMTrigger
Deal's ID
Opportunity Name
Responsible User
Responsible User Email
Sales pipeline
Sales Pipeline Stage
Contact name
Contact Position
Contact Email
Contact Phone
Contact's Birthday
Campaign Name
Source Name
Reason for Loss
Company Name
Company's adress
Company user id number
Company username
Company URL
Company segments (comma separated)
Seller team ID (separated by comma)
Organization contact emails (comma separated)
Opportunity tasks (separated by commas and line breaks)
Opportunity notes (separated by commas and line breaks)
Last opportunity note
Company ID
Product names (separated by comma)
Product descriptions (comma separated)
Product IDs (separated by comma)
Product quantities (separated by comma)
Product prices (separated by comma)
Product names, descriptions, quantities and prices (separated by commas)
Gross total of products
Full discount
Unique Amount
Recurring Amount
Total Amount
Qualification
Negotiation Wins
Paused Trading
Creation date
Closing date
Estimated closing date
Created At in the format 'yyyy-mm-dd'
Created At in the format 'dd/mm/yyyy'
Creation date formatted in 'yyyy-mm-dd HH:mm:ss'
Closed At in the format 'yyyy-mm-dd'
Closed At in the format 'dd/mm/yyyy'
Closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Prediction date in the format 'yyyy-mm-dd'
Prediction date in the format 'dd/mm/yyyy'
Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'
Date and time the opportunity entered the selected Stage
Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'
Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'
Created contact
For each created contact on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created contact
For each created contact on RD Station CRMTrigger
Contact ID
Contact name
Contact position
Contact's birthday
Contact Linkedin
Contact-related opportunities
Contact emails (separated by comma)
Contact phone numbers (separated by comma)
First contact phone number
Organization of contact
Contact organization website
Address of the contact organization
Create or update opportunity
create/update an opportunity on RD Station CRMHow it works:
Whenever something happens on the source app
1. An deal will be created/updated from a pipeline stage on RD Station CRM
2. A person/company associated with this deal will be created/updated on RD Station CRM
3. If desired, the created/updated deal can be assigned to a salesperson or distributed among registered salespeople on RD Station CRM (Round Robin)
All happening in a single automation! ✨
Create or update opportunity
create/update an opportunity on RD Station CRMAction
Distribute new deals
Select sellers
Team that will receive opportunities
Email of the Responsible
Update of opportunities
Deal owner update logic
Update criteria for negotiations
Opportunity name Required
Deal forecast date
Opportunity Qualification
Opportunity status
Contact updates
Company/Customer Name
Company website URL
Contact name Required
Contact Phone
Contact Email
Contact Position
Source Name
Name of the Campaign/Marketing Action
Product/Service Name
Product/service description
Product/Service Price
Product/Service Quantity
Product discount type
Product discount
Task Subject
Task date
Task type
Assignment Notes
Opportunity Note
Create or update contact
create or update a contact on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update contact
create or update a contact on RD Station CRMAction
Contact name Required
Update contact based on
Contact Email
Contact Phone
Contact Position
Organization Name
Organization URL
Contact's Birthday
Create or update company
create or update a company on RD Station CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update company
create or update a company on RD Station CRMAction
Company Name Required
Company URL
Company Summary
Didn't find your use case? Send suggestion.
Automate Nuvemshop and RD Station CRM with Pluga integrations
Explore automation templates
For each cancelled sale on Nuvemshop, create or update a contact on RD Station CRM
EXPLORE For each paid sale on Nuvemshop, create or update a contact on RD Station CRM
EXPLORE For each paid sale on Nuvemshop, create or update a company on RD Station CRM
EXPLORE Miss an automation with this apps?
Say to us!Trusted by over 10.000 amazing companies
How to integrate apps with Pluga?
Pluga allows you to integrate two or more apps in a simple, practical way without needing to type a single line of code. Here are the steps to automate your tasks and start focusing on what really matters.
-
What is the automation trigger?
The trigger is the step that initiates automation. In the integration process, it is selected after choosing the source app. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.
-
What is an action within an automation?
The action serves as a response to the previously selected trigger. That is, it occurs once the trigger is activated. For example, in an automation between Facebook Lead Ads (source) and Google Sheets (destination), as soon as the trigger “For each response on an advertisement” is activated in the source app, the action “Add data to a new row on a spreadsheet” will be carried out in the destination app.
-
How does information mapping work?
Information mapping is where you configure which captured information from the source app will be sent to each field in the destination app(s).
For example, in an automation between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.
-
Is it possible to have more than one action?
With Pluga, you can create automations by integrating several apps at once. For example, you can integrate Facebook Lead Ads + Google Sheets + Slack, so when the trigger is activated, the first action is executed and a notification is sent via Slack.
Automate Nuvemshop + RD Station CRM
and say goodbye to manual (and tedious) tasks!
By connecting the apps you use through Pluga, you can automate various processes in your routine and have time for tasks that really matter. 
Nuvemshop
EcommerceLeading e-commerce platform in Latin America, with more than 140,000 active stores - from small businesses to e-commerces that already earn millions.
Integrations with Nuvemshop Visit Nuvemshop RD Station CRM
CRMRD Station CRM is the CRM module of the RD Station platform. It offers tools for customer relationship management, sales automation, analytics, and integration with other digital marketing apps.
Integrations with RD Station CRM Visit RD Station CRM