Connect Nuvemshop with Moskit CRM
Unlock the superpowers of Nuvemshop + Moskit CRM and automate your tasks without having to write a single line of code.
Nuvemshop and Moskit CRM
your way
Check out the available triggers and actions in the automation of apps Nuvemshop + Moskit CRM
Sale created
With each sale created on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Sale created
With each sale created on NuvemshopTrigger
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
Created contact
For each created contact on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created contact
For each created contact on Moskit CRMTrigger
Name
Main Phone
E-mail Principal
Telephone numbers separated by comma
Emails separated by comma
Site
Creation date
Created by
Responsible
Comments
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Deal reached stage
When a deal reaches a funnel stage on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Deal reached stage
When a deal reaches a funnel stage on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Paid sale
For each paid sale on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Paid sale
For each paid sale on NuvemshopTrigger
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
Created deal
For each created deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created deal
For each created deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Won deal
For each won deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won deal
For each won deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Cancelled sale
For each cancelled sale on NuvemshopHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cancelled sale
For each cancelled sale on NuvemshopTrigger
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
Lost deal
For each lost deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost deal
For each lost deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Deal: Reason for loss
Create or update contact
create or update a contact on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update contact
create or update a contact on Moskit CRMAction
Select responsible Required
Contact: Name
Contact: Email Required
Contact: CPF
Company: Name
Company: Email
Company: CNPJ
Contact: Position
Contact: Telephone
Contact: Observations
Company: Website
Company: Telephone
Company: Observations
Contact updates
Create or update deal
create or update a business on Moskit CRMHow it works:
Whenever something happens on the source app
1. A deal will be created/updated from a pipeline stage on Moskit CRM
2. A contact associated with the deal will be created/updated on Moskit CRM
3. A company associated with the deal will be created/updated on Moskit CRM
4. If desired, the created/updated deal can be assigned to a salesperson or distributed among registered salespeople on Moskit CRM (Round Robin)
All happening in a single automation! ✨
Create or update deal
create or update a business on Moskit CRMAction
Distribute new deal Required
Select sellers
Responsible
Deal Name Required
Company: Name
Contact: Name
Contact: Email
Amount
Expected date
Deal status
Closing date
Reason for loss
Update Main Company
Company: Email
Company: Telephone
Update Primary Contact
Contact: Telephone
Contact: Position
Product's name
Product SKU
Product quantity
Price of the product
Company: Website
Company: Observations
Contact: Observations
Contact updates
Didn't find your use case? Send suggestion.
Automate Nuvemshop and Moskit CRM with Pluga integrations
Explore automation templates
For each cancelled sale on Nuvemshop, create or update a business on Moskit CRM
EXPLORE For each cancelled sale on Nuvemshop, create or update a contact on Moskit CRM
EXPLORE For each paid sale on Nuvemshop, create or update a business on Moskit CRM
EXPLORE For each paid sale on Nuvemshop, create or update a contact on Moskit CRM
EXPLORE Miss an automation with this apps?
Say to us!Trusted by over 10.000 amazing companies
How to integrate apps with Pluga?
Pluga allows you to integrate two or more apps in a simple, practical way without needing to type a single line of code. Here are the steps to automate your tasks and start focusing on what really matters.
-
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. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.
-
What is an action within an automation?
The action serves as a response to the previously selected trigger. That is, it occurs once the trigger is activated. For example, in an automation between Facebook Lead Ads (source) and Google Sheets (destination), as soon as the trigger “For each response on an advertisement” is activated in the source app, the action “Add data to a new row on a spreadsheet” will be carried out in the destination app.
-
How does information mapping work?
Information mapping is where you configure which captured information from the source app will be sent to each field in the destination app(s).
For example, in an automation between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.
-
Is it possible to have more than one action?
With Pluga, you can create automations by integrating several apps at once. For example, you can integrate Facebook Lead Ads + Google Sheets + Slack, so when the trigger is activated, the first action is executed and a notification is sent via Slack.
Automate Nuvemshop + Moskit CRM
and say goodbye to manual (and tedious) tasks!
By connecting the apps you use through Pluga, you can automate various processes in your routine and have time for tasks that really matter. 
Nuvemshop
EcommerceLeading e-commerce platform in Latin America, with more than 140,000 active stores - from small businesses to e-commerces that already earn millions.
Integrations with Nuvemshop Visit Nuvemshop Moskit CRM
CRMMoskit CRM is a customer relationship management (CRM) platform that offers tools to organize contacts, track sales, automate tasks, and improve customer relationships.
Integrations with Moskit CRM Visit Moskit CRM