Possibilities with Nuvemshop (Tiendanube)

Check out the use cases to automate and make the most of integrations with Nuvemshop (Tiendanube)

Trigger
Nuvemshop (Tiendanube)

Sale created

With each sale created on Nuvemshop

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

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

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

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

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

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

Trusted by over 10.000 amazing companies

Create automations with Nuvemshop (Tiendanube)
and say goodbye to manual (and tedious) tasks!

By connecting Nuvemshop (Tiendanube) to the apps you use through Pluga, you can automate various processes in your routine and
have time for tasks that really matter.

Automatic transfer of your contacts' information to other apps

Automating the transfer of your contact base (leads) information to other apps can greatly facilitate tasks that involve managing them.

At Pluga, you can do this with ease and also helps optimize the work of people, avoiding possible human errors.

Card with contact information being sent to other apps

Automate your sales tracking

With the help of Pluga's automations, you can put your business's sales control on autopilot. This way, tasks surrounding inventory, finance, and logistics can be more aligned and optimized, directly impacting your customer's satisfaction.

Data from a new sale being sent to a spreadsheet

Automated financial control

Dealing with finances requires a lot of attention. For this, integrating apps can be a great ally! With Pluga, you can connect your financial management software and payment methods to other apps to automate tasks involving the organization of your finances.

Data from a new charge being sent to an invoicing app

Reduce communication noise - and rework!

If your company uses any type of internal communication tool, it's possible to automate the routine of notifications and alerts within it.

At Pluga, for example, you can connect this software to your project management platform so that every time a task changes status, this is communicated in a channel. In other words, it increases productivity, reduces communication noise, and avoids possible rework.

Automatic notification in the internal communication app

Customized alerts for customers

Often, personalized communication is what will captivate a customer to keep them interested in your brand. But doing this manually is almost impossible. Using Pluga, you can send these notifications automatically without losing personalization.

Automatic message sent to the customer's WhatsApp

How to automate Nuvemshop (Tiendanube) with Pluga?

Pluga allows you to create automations between Nuvemshop (Tiendanube) and various other apps in a simple, practical way without needing to write a single line of code. See the steps to automate your tasks and start focusing on what really matters.

  • Trigger and source app of the automation

    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. Based on this choice, you can define what will happen in the destination app of your automation.

  • Action and destination app of the automation

    What is an action within an automation with Nuvemshop (Tiendanube)?

    An action works as a response to the selected trigger. In other words, it occurs from the moment the trigger is activated: when something happens in the app selected as the source, the action will be performed in the destination app.

  • Information mapping of the automation

    How does information mapping work?

    Mapping is where you configure which information captured from the source app will be sent to each of the fields in the destination app(s). In this step, you define which information from one app should fill the fields of the other software.

  • Automation with multiple actions among more than two apps

    Is it possible to have more than one action?

    Through Pluga, you can create automations integrating multiple apps at once. For example, you can integrate an ad app + online spreadsheet + internal communication software, so when the trigger is activated, the first action is executed, and a notification is sent to your team.

Nuvemshop (Tiendanube)

Nuvemshop (Tiendanube)

Ecommerce

Nuvemshop (Tiendanube) is an e-commerce platform that allows businesses to create and manage online stores, providing integration with payment methods, logistics, and marketing tools to boost online sales.

Visit Nuvemshop (Tiendanube)

Frequently Asked Questions

  • With Pluga, you can connect the app Nuvemshop (Tiendanube) with over 130 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.