Connect Tiendanube with Loop
Connect Tiendanube with Loop to scale and automate your operations.
Explore automation templates
Automate Tiendanube and Loop with Pluga integrations
Add each product from a Nuvemshop order as a separate row in Google Sheets.
Create a new Trello card for each product whenever a paid sale is completed in Nuvemshop (Tiendanube), then notify your team in Slack
Didn't find the template you wanted? Build the integration your own way. ;)
Trusted by over 10.000 companies
Tiendanube and Loop
your way
Check out the available triggers and actions in the automation of apps Tiendanube + Loop
Sale created
With each sale created on Tiendanube
Order products
Order: ID
Order: Store ID
Customer: Email
Customer: Name
Customer: Telephone
Customer: CPF/CNPJ
Order: Numeric ID
Order: Total discount amount
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
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
Order pending
Order pending on Tiendanube
Order products
Payment gateway
Order's ID
Store's ID
Email of the buyer
Name of the buyer
Phone of the buyer
Identification of the buyer (CPF/CNPJ/DNI/CUIT)
Unique number identifier for an Order used by the shop owner and customers. It's sequential and starts at 100
Total value of the discount applied to the price of the order
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
Price of the order before shipping
Total price of the order including shipping and discounts
Total price of the order in US dollars
The total spent's currency
Idioma do pedido utilizado.
Origin of the order.
Order's total weight, in kilograms
Order's status
Order's payment status
URL of the landing page
The unique numeric identifier for the Customer
Name of the Customer
Email of the Customer
Customer's identification (in Brazil for example, it would be the CPF/CNPJ)
Phone number of the customer
Store owner's notes about the customer
Default shipping address of the Customer: address
Default shipping address of the Customer: city
Default shipping address of the Customer: country
Default shipping address of the Customer: locality
Default shipping address of the Customer: name
Default shipping address of the Customer: number
Default shipping address of the Customer: phone
Default shipping address of the Customer: province
Default shipping address of the Customer: zipcode
Customer's type
Customer's trade name
Customer's business name
Customer's fiscal regime
Customer's invoice use
Customer's document type
Customer accepts Marketing
Billing name for the order
Billing phone for the order
Billing address for the order
Billing number for the order
Billing floor for the order
Billing locality for the order
Billing zipcode for the order
Billing city for the order
Billing province for the order
Billing country code for the order
Billing customer type (person or company)
Billing business name
Billing trade name
Billing state registration
Billing Fiscal Regime
The Billing Invoice Use
Billing document type
The minimum number of weekdays needed for the order to be delivered
The maximum number of weekdays needed for the order to be delivered
The shipping cost the store owner has to pay to the shipping company.
The shipping cost the customer has to pay to the store owner.
The shipping method used
The shipping option chosen by the customer during the checkout process.
The shipping option code selected by the consumers.
The shipping option reference provided by a custom shipping carrier during the checkout process.
The shipping tracking number for the order
The shipping tracking URL where the customer can check for the shipment status.
'ship' if the order is going to be shipped; 'pickup' if it's going to be picked up from a store branch
If order is going to be picked up, shows the store branch name
The shipping carrier name. If shipping method is custom, then null.
Order's shipping status
The customer's shipping address where the order will be shipped: address
The customer's shipping address where the order will be shipped: city
The customer's shipping address where the order will be shipped: country
The customer's shipping address where the order will be shipped: locality
The customer's shipping address where the order will be shipped: name
The customer's shipping address where the order will be shipped: number
The customer's shipping address where the order will be shipped: phone
The customer's shipping address where the order will be shipped: province
The customer's shipping address where the order will be shipped: zipcode
Date when the Order was created in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was created in format: DD/MM/AAAA HH:mm:ss
Date when the Order was created in format: HH:mm:ss
Date when the Order was created in format: DD/MM/AAAA
Date when the Order was last updated in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was last updated in format: DD/MM/AAAA HH:mm:ss
Date when the Order was last updated in format: HH:mm:ss
Date when the Order was last updated in format: DD/MM/AAAA
Date when the order was closed in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was closed in format: DD/MM/AAAA HH:mm:ss
Date when the order was closed in format: HH:mm:ss
Date when the order was closed in format: DD/MM/AAAA
Date when the order was marked as read in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was marked as read in format: DD/MM/AAAA HH:mm:ss
Date when the order was marked as read in format: HH:mm:ss
Date when the order was marked as read in format: DD/MM/AAAA
Date when the Order was shipped in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was shipped in format: DD/MM/AAAA HH:mm:ss
Date when the Order was shipped in format: HH:mm:ss
Date when the Order was shipped in format: DD/MM/AAAA
Date when the order was paid in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was paid in format: DD/MM/AAAA HH:mm:ss
Date when the order was paid in format: HH:mm:ss
Date when the order was paid in format: DD/MM/AAAA
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products formatted as: 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 Tiendanube
Order products
Order: ID
Order: Store ID
Customer: Email
Customer: Name
Customer: Telephone
Customer: CPF/CNPJ
Order: Numeric ID
Order: Total discount amount
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
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
Order sent
Order sent on Tiendanube
Order products
Order's ID
Store's ID
Email of the buyer
Name of the buyer
Phone of the buyer
ID of the buyer (CPF/CNPJ/DNI/CUIT)
Order's ID
Total value of the discount applied to the price of the order
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
Price of the order before shipping
Total price of the order including shipping and discounts
Total price of the order in US dollars
The total spent's currency
Order's language.
Origin of the order.
Order's total weight, in kilograms
Order's status
Order's payment status
URL of the landing page
Client's ID
Name of the Customer
Email of the Customer
CPF/CNPJ or customor document
Phone number of the customer
Store owner's notes about the customer
Default shipping address of the Customer: address
Default shipping address of the Customer: city
Default shipping address of the Customer: country
Default shipping address of the Customer: locality
Default shipping address of the Customer: name
Default shipping address of the Customer: number
Default shipping address of the Customer: phone
Default shipping address of the Customer: province
Default shipping address of the Customer: zipcode
Customer's type
Customer's trade name
Customer's business name
Customer's fiscal regime
Customer's invoice use
Customer's document type
Customer accepts Marketing
Billing name for the order
Billing phone for the order
Billing address for the order
Billing number for the order
Billing floor for the order
Billing locality for the order
Billing zipcode for the order
Billing city for the order
Billing province for the order
Billing country code for the order
Billing customer type (person or company)
Billing business name
Billing trade name
Billing state registration
Billing Fiscal Regime
The Billing Invoice Use
Billing document type
The minimum number of weekdays needed for the order to be delivered
The maximum number of weekdays needed for the order to be delivered
The shipping cost the store owner has to pay to the shipping company.
The shipping cost the customer has to pay to the store owner.
The shipping method used
The shipping option chosen by the customer during the checkout process.
The shipping option code selected by the consumers.
The shipping option reference provided by a custom shipping carrier during the checkout process.
The shipping tracking number for the order
The shipping tracking URL where the customer can check for the shipment status.
'ship' if the order is going to be shipped; 'pickup' if it's going to be picked up from a store branch
If order is going to be picked up, shows the store branch name
The shipping carrier name. If shipping method is custom, then null.
Order's shipping status
The customer's shipping address where the order will be shipped: address
The customer's shipping address where the order will be shipped: city
The customer's shipping address where the order will be shipped: country
The customer's shipping address where the order will be shipped: locality
The customer's shipping address where the order will be shipped: name
The customer's shipping address where the order will be shipped: number
The customer's shipping address where the order will be shipped: phone
The customer's shipping address where the order will be shipped: province
The customer's shipping address where the order will be shipped: zipcode
Date when the Order was created in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was created in format: DD/MM/AAAA HH:mm:ss
Date when the Order was created in format: HH:mm:ss
Date when the Order was created in format: DD/MM/AAAA
Date when the Order was last updated in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was last updated in format: DD/MM/AAAA HH:mm:ss
Date when the Order was last updated in format: HH:mm:ss
Date when the Order was last updated in format: DD/MM/AAAA
Date when the order was closed in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was closed in format: DD/MM/AAAA HH:mm:ss
Date when the order was closed in format: HH:mm:ss
Date when the order was closed in format: DD/MM/AAAA
Date when the order was marked as read in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was marked as read in format: DD/MM/AAAA HH:mm:ss
Date when the order was marked as read in format: HH:mm:ss
Date when the order was marked as read in format: DD/MM/AAAA
Date when the Order was shipped in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was shipped in format: DD/MM/AAAA HH:mm:ss
Date when the Order was shipped in format: HH:mm:ss
Date when the Order was shipped in format: DD/MM/AAAA
Date when the order was paid in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was paid in format: DD/MM/AAAA HH:mm:ss
Date when the order was paid in format: HH:mm:ss
Date when the order was paid in format: DD/MM/AAAA
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products formatted as: 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
Cancelled sale
For each cancelled sale on 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
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
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
Order voided
Order voided on Tiendanube
Order products
Payment gateway
The unique numeric identifier for the Order.
ID of the store the order belongs to
Email of the buyer
Name of the buyer
Phone of the buyer
Identification of the buyer (CPF/CNPJ/DNI/CUIT)
Unique number identifier for an Order used by the shop owner and customers. It's sequential and starts at 100
Total value of the discount applied to the price of the order
Promotional discount
Discount from the discount coupon
Discount from the payment gateway
Price of the order before shipping
Total price of the order including shipping and discounts
Total price of the order in US dollars
The total spent's currency
Order's language used by the customer during the checkout process
Origin of the order.
Order's total weight, in kilograms
Order's status
Order's payment status
URL of the landing page that led to the purchase. If the order was created via API by an app, then null.
The unique numeric identifier for the Customer
Name of the Customer
Email of the Customer
Customer's identification (in Brazil for example, it would be the CPF/CNPJ)
Phone number of the customer
Store owner's notes about the customer
Default shipping address of the Customer: address
Default shipping address of the Customer: city
Default shipping address of the Customer: country
Default shipping address of the Customer: locality
Default shipping address of the Customer: name
Default shipping address of the Customer: number
Default shipping address of the Customer: phone
Default shipping address of the Customer: province
Default shipping address of the Customer: zipcode
Customer's type
Customer's trade name
Customer's business name
Customer's fiscal regime
Customer's invoice use
Customer's document type
Customer accepts Marketing
Billing name for the order
Billing phone for the order
Billing address for the order
Billing number for the order
Billing floor for the order
Billing locality for the order
Billing zipcode for the order
Billing city for the order
Billing province for the order
Billing country code for the order
Billing customer type (person or company)
Billing business name
Billing trade name
Billing state registration
The (Billing Fiscal Regime) is only used in es_MX, and the default is 601. For other countries, the default is null
The (Billing Invoice Use) is only used in es_MX, and the default is G01. For other countries, the default is null
Billing document type
The minimum number of weekdays needed for the order to be delivered
The maximum number of weekdays needed for the order to be delivered
The shipping cost the store owner has to pay to the shipping company.
The shipping cost the customer has to pay to the store owner.
The shipping method used
The shipping option chosen by the customer during the checkout process.
The shipping option code selected by the consumers.
The shipping option reference provided by a custom shipping carrier during the checkout process.
The shipping tracking number for the order
The shipping tracking URL where the customer can check for the shipment status.
'ship' if the order is going to be shipped; 'pickup' if it's going to be picked up from a store branch
If order is going to be picked up, shows the store branch name
The shipping carrier name. If shipping method is custom, then null.
Order's shipping status
The customer's shipping address where the order will be shipped: address
The customer's shipping address where the order will be shipped: city
The customer's shipping address where the order will be shipped: country
The customer's shipping address where the order will be shipped: locality
The customer's shipping address where the order will be shipped: name
The customer's shipping address where the order will be shipped: number
The customer's shipping address where the order will be shipped: phone
The customer's shipping address where the order will be shipped: province
The customer's shipping address where the order will be shipped: zipcode
Date when the Order was created in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was created in format: DD/MM/AAAA HH:mm:ss
Date when the Order was created in format: HH:mm:ss
Date when the Order was created in format: DD/MM/AAAA
Date when the Order was last updated in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was last updated in format: DD/MM/AAAA HH:mm:ss
Date when the Order was last updated in format: HH:mm:ss
Date when the Order was last updated in format: DD/MM/AAAA
Date when the order was closed in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was closed in format: DD/MM/AAAA HH:mm:ss
Date when the order was closed in format: HH:mm:ss
Date when the order was closed in format: DD/MM/AAAA
Date when the order was marked as read in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was marked as read in format: DD/MM/AAAA HH:mm:ss
Date when the order was marked as read in format: HH:mm:ss
Date when the order was marked as read in format: DD/MM/AAAA
Date when the Order was shipped in format: YYYY-MM-DDTHH:mm.sssZ
Date when the Order was shipped in format: DD/MM/AAAA HH:mm:ss
Date when the Order was shipped in format: HH:mm:ss
Date when the Order was shipped in format: DD/MM/AAAA
Date when the order was paid in format: YYYY-MM-DDTHH:mm.sssZ
Date when the order was paid in format: DD/MM/AAAA HH:mm:ss
Date when the order was paid in format: HH:mm:ss
Date when the order was paid in format: DD/MM/AAAA
Products: Names
Products: Quantities
Products: Prices
Products: SKU
Products formatted as: 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
Update stock
Update stock in Nuvemshop (Tiendanube)
Product's SKU Required
Operation Required
Stock quantity Required
Loop through a list
Loops through the items in a list and repeats the next actions for each one
- Turn each product in an order into its own row in a spreadsheet or task in your project management tool
- Loop through search results (tickets, leads, or orders) and trigger the next action for each item
- Process batches of data received through a webhook or API response
- Apply specific rules to each item by combining Loop with Formatter, Router, or HTTP Request
List Required
Search sales
Search sales in Nuvemshop (Tiendanube)
Search filters
Page
Items per page
Search products
Search products in Nuvemshop (Tiendanube)
Search filters
Sort by
Page
Items per page
Boost this flow in your workflow
With Pluga, you connect Tiendanube + Loop 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 Tiendanube".
- Basic 2
Set the destinations and the actions
Select the apps that make up the flow with Loop and what Pluga should run automatically at each step. Example: "Loops through the items in a list and repeats the next actions for each one"
- 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
Tiendanube
E-commerceConnect Tiendanube to 136+ 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.
Loop
PlugaConnect Loop to 136+ apps with Pluga and turn your work into a productive machine. Take full control of your flows: schedule execution, hold the flow for as long as you need, branch by condition and reshape the data along the way.
