Start in minutes

Ready-made templates with Nuvemshop (Tiendanube)

Pre-configured flows with Nuvemshop (Tiendanube), ready to activate in a few clicks.

Todoist
Nuvemshop (Tiendanube)

For each paid sale on Nuvemshop, create a task on Todoist

Automate
Gmail
Nuvemshop (Tiendanube)

With each sale created on Nuvemshop, create a draft in Gmail

Automate
Google Contacts
Nuvemshop (Tiendanube)

For each paid sale on Nuvemshop, create/update a contact on Google Contacts

Automate
Leadlovers
Nuvemshop (Tiendanube)

For each paid sale on Nuvemshop, create/update a lead on Leadlovers

Automate
Intercom
Nuvemshop (Tiendanube)

For each paid sale on Nuvemshop, create/update a user on Intercom

Automate
See all templates with Nuvemshop (Tiendanube)

All automations with Nuvemshop (Tiendanube)

Trusted by over 10.000 amazing companies

🏆 Top 3 use cases

How do companies use Nuvemshop (Tiendanube)?

Popular, smart ways to use Nuvemshop (Tiendanube) every day

  • When a sale comes into the store, a notification reaches every team involved (shipping, finance, team chat). Order processing starts moving at the same moment, without waiting on manual checks.

  • Each recorded sale sends the order to the ERP, the spreadsheet or the matching logistics tool. Sales stay consolidated across every point of the operation, with no errors in the handoff.

  • When a cart is left behind, a reminder message or email goes out at the right time. An almost lost sale gets another chance, without pulling in the sales team.

Possibilities with Nuvemshop (Tiendanube) on Pluga

Available triggers with Nuvemshop (Tiendanube)

The trigger is the event on Nuvemshop (Tiendanube) that automatically starts the flow on Pluga, firing one or more actions.

Trigger
Nuvemshop (Tiendanube)

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

Trigger
Nuvemshop (Tiendanube)

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

Trigger
Nuvemshop (Tiendanube)

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

How it works

How to integrate with Nuvemshop (Tiendanube)

1. Trigger Nuvemshop (Tiendanube) Sale created, Paid sale, Cancelled sale
2. Action Target app Perform an action…
How to use Nuvemshop (Tiendanube) on Pluga

Boost Nuvemshop (Tiendanube) in your workflow

With Pluga, you connect Nuvemshop (Tiendanube) to one (or more!) apps 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, "With each sale created on Nuvemshop (Tiendanube)".

  • Basic 2

    Set the destinations and the actions

    Select the apps that make up the flow with Nuvemshop (Tiendanube) and what Pluga should run automatically at each step.

  • 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

    Explore
  • Intermediate

    Standardize data across apps

    Adjust dates, numbers and characters to the format the next app expects to receive

    Explore
  • Advanced

    Send data in several directions

    Route each piece of data down the right path within a single flow, according to specific conditions

    Explore
  • Advanced

    Add a code block

    Run JavaScript or Python in the middle of the automation to transform data before the next step

    Explore
  • Advanced

    Create loops

    Take lists of items, go through each row and run the same action for every one of them

    Explore
  • Advanced

    Use generative AI

    Send data to an AI assistant or agent and use the response in the next step

    Explore
  • Advanced

    Connect to (almost) any app

    Send and receive data through a dedicated URL, and connect to apps that are not integrated with Pluga

    Explore
  • Advanced

    Requests to external APIs

    Query or send data to any external API inside your automation

    Explore
Nuvemshop (Tiendanube)

Nuvemshop (Tiendanube)

E-commerce

Connect 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.

See more integrations with e-commerce Visit Nuvemshop (Tiendanube)

Frequently Asked Questions

Everything you need to know to get started with Nuvemshop (Tiendanube) on Pluga.

  • With Pluga, you can connect the app Nuvemshop (Tiendanube) with over 133 other software platforms and automate various business processes and tasks. Just follow these steps:


    • 1. Log in or sign up (for free) at Pluga and click on “Create Automation”;
    • 2. Select the source app and trigger;
    • 3. Connect the app;
    • 4. Select the destination app and action;
    • 5. Connect the app account;
    • 6. Make the necessary adjustments, specifying which data will be sent from one app to another.

  • At Pluga, you can create up to 3 automations with the free plan. Additionally, you have the option to try all features for 7 days at no cost to create automations between Nuvemshop (Tiendanube) and other apps.

    We also offer three other plans, with prices ranging from $17 to $71 per month, which include premium automations and features, as well as a higher volume of events and automations. For companies with specific needs, we have the Enterprise plan, designed to offer customized solutions beyond the resources available in other plans.

    Check out Pluga's pricing page for more details.

  • The number of automations between Nuvemshop (Tiendanube) and other apps on Pluga will depend on the chosen plan.

  • No. Pluga is an intuitive platform that allows the creation of automations between Nuvemshop (Tiendanube) and other apps without any technical knowledge required.

  • Automating Nuvemshop (Tiendanube) with other apps allows you to boost various activities (such as marketing, sales, customer service, and internal communication) and eliminate potential human errors.

  • No, Pluga is not affiliated with or created by Nuvemshop (Tiendanube). Generally, Pluga accesses the documentation provided by Nuvemshop (Tiendanube) and independently develops the available integrations. Any mentions of Pluga on the Nuvemshop (Tiendanube) website are strictly voluntary collaborations. Pluga remains solely responsible for the maintenance and support of its automation services.