Connect ClickUp with Nuvemshop

Unlock the superpowers of ClickUp + Nuvemshop and automate your tasks without having to write a single line of code.

ClickUp and Nuvemshop
your way

Check out the available triggers and actions in the automation of apps ClickUp + Nuvemshop

ClickUp-icon

Created task

For each created task on ClickUp

Trigger

Information from ClickUp that can be used and sent to other apps.

Task Name

End date

Description

Initial date

Task creator

List name

Task URL

ID of those responsible separated by comma

Responsible persons separated by comma

Email of those responsible separated by comma

Color of those responsible separated by comma

Initials of those responsible for the task

Task ID

Task creation date

Task Status

Task priority

Task folder name

Tags

Project name

Update date

Estimated task time

Time spent on task

Task creator email

List ID

Task 'parent' task

Checklists

Space ID

Project ID

Task end date

Task points

Task creator ID

I give status

Linked tasks

Folder ID

Orderindex

Name of attachments separated by comma

Comma-separated attachment link

Name and link of attachments separated by comma

Nuvemshop-icon

Paid sale

For each paid sale on Nuvemshop

Trigger

Information from Nuvemshop that can be used and sent to other apps.

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

ClickUp-icon

Updated task status

When a task reaches a certain status on ClickUp

Trigger

Information from ClickUp that can be used and sent to other apps.

Task name

End date

Description

Initial date

Task creator

List name

Task URL

ID of those responsible separated by comma

Responsible persons separated by comma

Email of those responsible separated by comma

Color of those responsible separated by comma

Initials of those responsible for the task

Task ID

Task creation date

Task status

Task priority

Task folder name

Tags

Project name

Update date

Estimated task time

Time spent on task

Task creator email

List ID

Task 'parent' task

Checklists

Space ID

Project ID

Task end date

Task points

Task creator ID

I give status

Linked tasks

Folder ID

Orderindex

Name of attachments separated by comma

Comma-separated attachment link

Name and Link of attachments separated by comma

Nuvemshop-icon

Cancelled sale

For each cancelled sale on Nuvemshop

Trigger

Information from Nuvemshop that can be used and sent to other apps.

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

Nuvemshop-icon

Sale created

With each sale created on Nuvemshop

Trigger

Information from Nuvemshop that can be used and sent to other apps.

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

ClickUp-icon

Create/update task

create or update a new task on ClickUp

Action

Fields in ClickUp that can receive information from other apps.

Task update settings

Task name Required

Task description

Responsible for the task

Task status

Task Tags

Task priority

Task due date

Task start date

Notify users?

checklist name

checklist items

Separator

Didn't find your use case? Send suggestion.

Automate ClickUp and Nuvemshop
with Pluga integrations

Explore automation templates

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.

  • 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. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.

  • Action and destination app of the automation

    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.

  • Information mapping of the automation

    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.

  • Automation with multiple actions among more than two apps

    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 ClickUp + Nuvemshop
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.

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
ClickUp-icon

ClickUp

Project

ClickUp is a task and team management app. The platform assists various teams, including marketing, sales, IT, HR, and others, that aim to optimize their routines.

Integrations with ClickUp Visit ClickUp
Nuvemshop-icon

Nuvemshop

Ecommerce

Leading 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

Frequently Asked Questions

  • With Pluga, you can easily automate ClickUp com Nuvemshop . Just follow these steps:

    • 1. Log in or sign up (for free) on Pluga and click on “Create automation”;
    • 2. Select the source app and trigger;
    • 3. Select the destination app and action;
    • 4. Make the necessary adjustments, specifying which data will be sent to one app to another.
  • By automating ClickUp with Nuvemshop on Pluga, you can automate various manual tasks that reduce productivity for those who perform them, while also avoiding human errors. The best part is that the process is simple and doesn’t require typing a single line of code.

  • On Pluga, you can make several automations for free with the free plan. Additionally, you have the option to try all the features for 7 days at no cost to create automations between ClickUp, Nuvemshop, and even 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 Pluga's pricing page for more details.