Connect Z-API with Nuvemshop (Tiendanube)
Connect Z-API with Nuvemshop (Tiendanube) to scale and automate your operations.
Explore automation templates
Automate Z-API and Nuvemshop (Tiendanube) with Pluga integrations
With each sale created on Nuvemshop, send text message on WhatsApp (Z-API)
For each cancelled sale on Nuvemshop, send text message on WhatsApp (Z-API)
For each paid sale on Nuvemshop, send text message on WhatsApp (Z-API)
Didn't find the template you wanted? Build the integration your own way. ;)
Trusted by over 10.000 amazing companies
Z-API and Nuvemshop (Tiendanube)
your way
Check out the available triggers and actions in the automation of apps Z-API + Nuvemshop (Tiendanube)
New message received
New message received on WhatsApp (Z-API)
Sender phone number
Sender name
Message ID
Sent at (timestamp)
Message sent from own number?
Text content of the message
URL to download the audio
Message type: 'text' or 'audio'
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
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
Send text message
Send text message on WhatsApp (Z-API)
Recipient number Required
Message Required
Send delay (seconds)
Typing time (seconds)
Boost this flow in your workflow
With Pluga, you connect Z-API + 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 paid sale on Nuvemshop (Tiendanube)".
- Basic 2
Set the destinations and the actions
Select the apps that make up the flow with Z-API and what Pluga should run automatically at each step. Example: "Send text message on WhatsApp (Z-API)"
- 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
Z-API
CommunicationConnect Z-API to 131+ apps with Pluga and turn your work into a productive machine. Every move inside your apps can become a message to the customer or an alert to the team — in the right channel and with the right data.
Nuvemshop (Tiendanube)
E-commerceConnect Nuvemshop (Tiendanube) to 131+ 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.
