Connect RD Station Marketing with Nuvemshop (Tiendanube)
Connect RD Station Marketing with Nuvemshop (Tiendanube) to scale and automate your operations.
Explore automation templates
Automate RD Station Marketing and Nuvemshop (Tiendanube) with Pluga integrations
With each sale created on Nuvemshop, include or update the lead on RD Station Marketing
For each cancelled sale on Nuvemshop, include or update the lead on RD Station Marketing
For each paid sale on Nuvemshop, include or update the lead on RD Station Marketing
For each paid sale on Nuvemshop, change the lead status to "customer" on RD Station Marketing
Didn't find the template you wanted? Build the integration your own way. ;)
Trusted by over 10.000 amazing companies
RD Station Marketing and Nuvemshop (Tiendanube)
your way
Check out the available triggers and actions in the automation of apps RD Station Marketing + Nuvemshop (Tiendanube)
Lead update
When the lead reaches a certain step in the RD Station Marketing automation flow
lead email
lead name
phone lead
cell phone
cargo
website
city
state
lead id
email user
lead company
public url
created in
Last scheduled opportunity date
Last scheduled opportunity date (date)
Last scheduled opportunity date (time)
Created on (date)
Created at (time)
updated
Updated on (date)
Updated at (time)
It's an opportunity
number of conversions
lead scoring
interest
Lead Internship
Identifier (first conversion)
lead origin - source (first conversion)
lead source - medium (first conversion)
lead source - campaign (first conversion)
User-Agent (first conversion)
twitter lead (first conversion)
Facebook lead (first conversion)
linkedin lead (first conversion)
device (first conversion)
twitter company (first conversion)
facebook company (first conversion)
linkedin company (first conversion)
company size (first conversion)
company address (first conversion)
company id sector (first conversion)
company website (first conversion)
email company (first conversion)
telephone company (first conversion)
url de conversão (primeira conversão)
First Conversion Traffic Source
First conversion (first session) traffic source
First conversion traffic source (current session)
Lead source - traffic medium (first conversion)
Lead source - traffic campaign (first conversion)
Lead source - traffic amount (first conversion)
Identificador de evento (primeira conversão)
Lead origin (last conversion)
Second Conversion Traffic Source (First Session)
Second Conversion Traffic Source (Current Session)
lead source - traffic amount (last conversion)
Telephone (last conversion)
Creation date (last conversion)
seller of last conversion
last conversion identifier
url de conversão (última conversão)
lead origin - source (last conversion)
lead source - medium (last conversion)
lead source - campaign (last conversion)
Creation date in day/month/year format (last conversion)
Creation time (last conversion)
Identificador de evento (última conversão)
Tags (separated by comma)
lead source - utm_medium (first conversion)
lead source - utm_campaign (first conversion)
lead source - utm_term (first conversion)
lead source - utm_content (first conversion)
lead source - utm_source (first conversion)
lead source - utm_medium (last conversion)
lead source - utm_campaign (last conversion)
lead source - utm_term (last conversion)
lead source - utm_content (last conversion)
lead source - utm_source (last conversion)
Paid sale
For each paid sale on Nuvemshop (Tiendanube)
Order products
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
Products formatted as: Cost
Payment method
Number of installments
Coupon codes (comma-separated)
Customer visit: landing page
Customer visit: UTM campaign
Customer visit: UTM content
Customer visit: UTM medium
Customer visit: UTM source
Customer visit: UTM term
Gateway ID
Gateway link
Gateway name
Lead marked as opportunity
When a lead is marked as an opportunity on RD Station Marketing
Lead: uuid
User: Email
Lead: Linkedin
Lead: Facebook
Lead: Twitter
Lead: Company
Lead: Date the opportunity was marked
Lead: Date the opportunity was marked (date)
Lead: Date the opportunity was marked (time)
Lead: Score
Lead: Source
Lead: Tags (separated by comma)
Lead: Email
Lead: Name
Lead: Phone
Lead: Cellphone
Lead: Role
Lead: Website
Lead: City
Lead: State
Cancelled sale
For each cancelled sale on Nuvemshop (Tiendanube)
Order products
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
Products formatted as: Cost
Payment method
Number of installments
Coupon codes (comma-separated)
Customer visit: landing page
Customer visit: UTM campaign
Customer visit: UTM content
Customer visit: UTM medium
Customer visit: UTM source
Customer visit: UTM term
Gateway ID
Gateway link
Gateway name
Sale created
With each sale created on Nuvemshop (Tiendanube)
Order products
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
Products formatted as: Cost
Payment method
Number of installments
Coupon codes (comma-separated)
Customer visit: landing page
Customer visit: UTM campaign
Customer visit: UTM content
Customer visit: UTM medium
Customer visit: UTM source
Customer visit: UTM term
Gateway ID
Gateway link
Gateway name
Change lead status to customer
change the lead status to "customer" on RD Station Marketing
Email Required
Opportunity Required
Event name Required
Create sale for lead
Sale value
Search leads
Search leads in RD Station Marketing
Search Term
Result limit
No leads found?
Create or update lead
include or update the lead on RD Station Marketing
Email Required
Event name Required
Name
Office
Telephone
Cell phone
Country
state
City
Web site
Tags
Lead's birthday
Company
Company website
Company size
Company's adress
Create sale for lead
Sale value
UTM medium
UTM source
UTM campaign
UTM terms
Add or remove lead tag
Add or remove leag tag in RD Station Marketing
Action Required
Lead email Required
Tag Required
Get lead by ID or email
Get a lead in RD Station Marketing
ID or Email Required
Boost this flow in your workflow
With Pluga, you connect RD Station Marketing + Nuvemshop (Tiendanube) to build anything from the simplest integration to the most advanced flows, with several layers of logic.
- Basic 1
Pick the source app and the trigger
Choose which app starts the automation and which event works as the trigger. For example, "For each cancelled sale on Nuvemshop (Tiendanube)".
- Basic 2
Set the destinations and the actions
Select the apps that make up the flow with RD Station Marketing and what Pluga should run automatically at each step. Example: "Get a lead in RD Station Marketing"
- Basic 3
Map the information
Point out, visually, which data from the source app should fill in each field of the destination action.
- Intermediate
Only move forward when it makes sense
Set "AND" or "OR" conditions so the automation only runs in the cases that matter
- Intermediate
Pause the flow for as long as you need
Set the automation to wait minutes, hours or days and resume the next action on its own
- Intermediate
Standardize data across apps
Adjust dates, numbers and characters to the format the next app expects to receive
- Advanced
Send data in several directions
Route each piece of data down the right path within a single flow, according to specific conditions
- Advanced
Add a code block
Run JavaScript or Python in the middle of the automation to transform data before the next step
- Advanced
Create loops
Take lists of items, go through each row and run the same action for every one of them
- Advanced
Use generative AI
Send data to an AI assistant or agent and use the response in the next step
- Advanced
Connect to (almost) any app
Send and receive data through a dedicated URL, and connect to apps that are not integrated with Pluga
- Advanced
Requests to external APIs
Query or send data to any external API inside your automation
RD Station Marketing
MarketingConnect RD Station Marketing to 133+ apps with Pluga and turn your work into a productive machine. Capture leads from all your channels, place each contact in the flow that makes sense for them and keep your database status always current, automatically.
Nuvemshop (Tiendanube)
E-commerceConnect Nuvemshop (Tiendanube) to 133+ apps with Pluga and turn your work into a productive machine. Automate order processing — created, paid, shipped or cancelled: each stage triggers the next steps, from customer notifications to finance and inventory entries.
