Automate Ploomes with Olist ERP (Tiny ERP)
Unlock the superpowers of Ploomes + Olist ERP (Tiny ERP) and automate your tasks without having to write a single line of code.
Ploomes and Olist ERP (Tiny ERP)
your way
Check out the available triggers and actions in the automation of apps Ploomes + Olist ERP (Tiny ERP)
Won Card
For each won card on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won Card
For each won card on PloomesTrigger
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Person: ID
Person: Type ID
Person: Name
Person: Legal Name
Person: Legal Registration
Person: CNPJ
Person: CPF
Person: Birthday
Person: Upcoming birthday
Person: Previous birthday
Person: Observations
Person: Email
Person: Website
Person: Skype
Person: Facebook
Person: City
Person: State
Person: Country
Person: Position
Person: Department
Person: Address
Person: Address Number
Person: Address Complement
Person: Neighborhood
Person: Zip Code
Person: Zipcode
Person: Marketing Email
Person: CNAE Code
Person: Name CNAE
Person: Secondary Name CNAE
Person: Phone Numbers (separated by comma)
Status: Id
Status: Name
Pipeline: Pipeline ID
Pipeline: Pipeline name
Pipeline: Pipeline name in singular
Pipeline: Pipeline name in plural
Internship: ID
Stage: Name of the stage in the pipeline
Stage: Pipeline ID
Stage: Last stage of the pipeline when the card has been closed
Stage: Position in the pipeline (number)
Card Owner: Name
Card Owner: Email
Won proposal
For each won proposal on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won proposal
For each won proposal on PloomesTrigger Premium
Proposal: ID
Proposal: Contact ID
Proposal: Customer name
Proposal: Title
Proposal: Date
Proposal: Number
Proposal: Contact name
Proposal: ID of the Currency Used
Proposal: Amount
Proposal: Discount
Proposal: Due Date
Proposal: Delivery Time
Proposal: Payment Method
Proposal: Description
Proposal: Observations
Proposal: Shipping Cost
Proposal: Shipping Method
Proposal: Number of Installments
Proposal: Key
Proposal: Document URL
Proposal: Creation Date
Proposal: Last Update Date
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Contacted: ID
Contact: Type ID
Contact: Name
Contact: Legal Name
Contact: Legal Registration
Contact: CNPJ
Contact: CPF
Contact: Birthday
Contact: Next birthday
Contact: Previous birthday
Contact: Observations
Contact: Email
Contact: Website
Contact: Skype
Contact: Facebook
Contact: City
Contact: State
Contact: Country
Contact: Position
Contact: Department
Contact: Address
Contact: Address Number
Contact: Address Supplement
Contact: Neighborhood
Contact: Zip Code
Contato: Zipcode
Contact: Marketing Email
Contact: CNAE Code
Contact: CNAE Name
Contact: CNAE Secondary Name
Contact: Telephone Numbers (separated by commas)
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Products: Product Name (separated by commas)
Products: Quantity (separated by commas)
Products: Unit price (separated by commas)
Products: Discount (separated by commas)
Products: Total sales (separated by commas)
Products: Product Code (separated by commas)
Produtos: Nomes e quantidades (separado por vírgulas)
Products: Names, quantities, and unit prices (separated by commas)
Internship: ID
Internship: Name
Stage: Pipeline ID
Stage: Last stage of the pipeline?
Internship: Pipeline position
Pipeline: ID
Pipeline: Name
Pipeline: Single Unit Name
Pipeline: Plural Unit Name
Card Owner: Name
Card Owner: Email
Created client
For each created client on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created client
For each created client on PloomesTrigger
Customer: ID
Customer: Type ID
Customer: Name
Customer: Legal Name
Customer: Legal Registry
Customer: CNPJ
Customer: CPF
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Customer: Contact Type ID
Customer: Type of Contact (Person or Company)
Customer Company: ID
Customer Company: Type ID
Customer Company: Name
Customer Company: Legal Name
Customer Company: Legal Registration
Customer Company: CNPJ
Customer Company: CPF
Customer Company: Birthday
Customer Company: Upcoming anniversary
Customer Company: Previous birthday
Customer Company: Email
Customer Company: Website
Customer Company: Skype
Customer Company: Facebook
Customer Company: Address
Customer Company: Address Number
Customer Company: Address Complement
Customer Company: Zip Code
Customer Company: Zip Code abroad
Customer Company: Marketing Email
Customer Company: CNAE Code
Customer Company: CNAE Name
Customer Company: CNAE Secondary Name
Unpaid account will expire
For each new due account pay on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Unpaid account will expire
For each new due account pay on Olist ERP (Tiny ERP)Trigger
Identification number
Date of issue
Due date
Amount
Balance
Document number
Supplier code
Provider's name
Supplier person type
Supplier's CPF or CNPJ
Supplier state registration
Supplier ID
Supplier address
Supplier address number
Supplier address supplement
Supplier neighborhood
Supplier Zip Code
Supplier city
Supplier UF
Supplier country
Supplier phone number
Supplier email
Historic
Category
Situation
Type of occurrence
Due date
Number of plots
Added receivable account
For each added accounts receivable on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Added receivable account
For each added accounts receivable on Olist ERP (Tiny ERP)Trigger
Account receivable: ID
Account receivable: Issue date
Account receivable: Due date
Account receivable: Amount
Account receivable: Document number
Account receivable: Document series
Account receivable: Bank number
Account receivable: Competence
Customer: Code
Customer: Name
Customer: Type of person (in the format: 'F', 'J', or 'E')
Customer: Type of person in full (in the format: Individual, Legal Entity, Foreigner)
Customer: CPF or CNPJ
Customer: State registration
Customer: RG
Customer: Address
Customer: Address number
Customer: Address complement
Customer: Neighborhood
Customer: Zip Code
Customer: City
Customer: UF
Customer: Country
Customer: Telephone
Customer: Email
Account receivable: History
Account receivable: Category
Account receivable: Payment method
Account receivable: Payment method
Account receivable: Status
Account receivable: Occurrence (in the format: 'U', 'P', 'W', 'M', 'T', 'S', 'A')
Account receivable: Occurrence in words (in the format: 'Single', 'Instalments', 'Weekly', 'Monthly', 'Quarterly', 'Six-monthly', 'Annual')
Account receivable: Due date
Account receivable: Number of installments
Account receivable: Day of the week when the weekly installment is due
Account receivable: Account receivable balance
Lost card
For each lost card on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost card
For each lost card on PloomesTrigger
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Card: Loss reason ID
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Person: ID
Person: Type ID
Person: Name
Person: Legal Name
Person: Legal Registration
Person: CNPJ
Person: CPF
Person: Birthday
Person: Upcoming birthday
Person: Previous birthday
Person: Observations
Person: Email
Person: Website
Person: Skype
Person: Facebook
Person: City
Person: State
Person: Country
Person: Position
Person: Department
Person: Address
Person: Address Number
Person: Address Complement
Person: Neighborhood
Person: Zip Code
Person: Zipcode
Person: Marketing Email
Person: CNAE Code
Person: Name CNAE
Person: Secondary Name CNAE
Person: Phone Numbers (separated by comma)
Status: Id
Status: Name
Pipeline: ID
Pipeline: Pipeline name
Pipeline: Pipeline name in singular
Pipeline: Pipeline name in plural
Internship: ID
Internship: Name
Stage: Name of the stage in the pipeline
Stage: Last stage of the pipeline when the card has been closed
Stage: Position in the pipeline (number)
Card Owner: Name
Card Owner: Email
Card created
For each created card on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Card created
For each created card on PloomesTrigger
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Person: ID
Person: Type ID
Person: Name
Person: Legal Name
Person: Legal Registration
Person: CNPJ
Person: CPF
Person: Birthday
Person: Upcoming birthday
Person: Previous birthday
Person: Observations
Person: Email
Person: Website
Person: Skype
Person: Facebook
Person: City
Person: State
Person: Country
Person: Position
Person: Department
Person: Address
Person: Address Number
Person: Address Complement
Person: Neighborhood
Person: Zip Code
Person: Zipcode
Person: Marketing Email
Person: CNAE Code
Person: Name CNAE
Person: Secondary Name CNAE
Person: Phone Numbers (separated by comma)
Status: Id
Status: Name
Pipeline: Pipeline ID
Pipeline: Pipeline name
Pipeline: Pipeline name in singular
Pipeline: Pipeline name in plural
Internship: ID
Stage: Name of the stage in the pipeline
Stage: Pipeline ID
Stage: Last stage of the pipeline when the card has been closed
Stage: Position in the pipeline (number)
Card Owner: Name
Card Owner: Email
Card reaches a stage in the pipeline
When a card reaches a funnel stage on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Card reaches a stage in the pipeline
When a card reaches a funnel stage on PloomesTrigger
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Person: ID
Person: Type ID
Person: Name
Person: Legal Name
Person: Legal Registration
Person: CNPJ
Person: CPF
Person: Birthday
Person: Upcoming birthday
Person: Previous birthday
Person: Observations
Person: Email
Person: Website
Person: Skype
Person: Facebook
Person: City
Person: State
Person: Country
Person: Position
Person: Department
Person: Address
Person: Address Number
Person: Address Complement
Person: Neighborhood
Person: Zip Code
Person: Zipcode
Person: Marketing Email
Person: CNAE Code
Person: Name CNAE
Person: Secondary Name CNAE
Person: Phone Numbers (separated by comma)
Status: Id
Status: Name
Pipeline: Pipeline ID
Pipeline: Pipeline name
Pipeline: Pipeline name in singular
Pipeline: Pipeline name in plural
Internship: ID
Stage: Name of the stage in the pipeline
Stage: Pipeline ID
Stage: Last stage of the pipeline when the card has been closed
Stage: Position in the pipeline (number)
Card Owner: Name
Card Owner: Email
Included new customer or supplier
When a new customer or supplier is included on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Included new customer or supplier
When a new customer or supplier is included on Olist ERP (Tiny ERP)Trigger
Identification number
code
Name or company name
Kind of person
Date of birth
Sex
Fancy name
CPF or CNPJ
RG
State registration
Municipal registration
Landline
Cell phone
Profession
Address
Address number
Address complement
Neighborhood
City
UF
Contact email
Situation
Creation date
Observations about contact
Lost proposal
For each lost proposal on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost proposal
For each lost proposal on PloomesTrigger Premium
Proposal: ID
Proposal: Contact ID
Proposal: Customer name
Proposal: Title
Proposal: Date
Proposal: Number
Proposal: Contact name
Proposal: ID of the Currency Used
Proposal: Amount
Proposal: Discount
Proposal: Due Date
Proposal: Delivery Time
Proposal: Payment Method
Proposal: Description
Proposal: Observations
Proposal: Shipping Cost
Proposal: Shipping Method
Proposal: Number of Installments
Proposal: Key
Proposal: Document URL
Proposal: Creation Date
Proposal: Last Update Date
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Contacted: ID
Contact: Type ID
Contact: Name
Contact: Legal Name
Contact: Legal Registration
Contact: CNPJ
Contact: CPF
Contact: Birthday
Contact: Next birthday
Contact: Previous birthday
Contact: Observations
Contact: Email
Contact: Website
Contact: Skype
Contact: Facebook
Contact: City
Contact: State
Contact: Country
Contact: Position
Contact: Department
Contact: Address
Contact: Address Number
Contact: Address Supplement
Contact: Neighborhood
Contact: Zip Code
Contato: Zipcode
Contact: Marketing Email
Contact: CNAE Code
Contact: CNAE Name
Contact: CNAE Secondary Name
Contact: Telephone Numbers (separated by commas)
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: Card stage ID in the pipeline
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Products: Product Name (separated by commas)
Products: Quantity (separated by commas)
Products: Unit price (separated by commas)
Products: Discount (separated by commas)
Products: Total sales (separated by commas)
Products: Product Code (separated by commas)
Products: Name with Quantity and Units Sold
Products: Names, quantities, and unit prices (separated by commas)
Internship: ID
Internship: Name
Stage: Pipeline ID
Stage: Last stage of the pipeline?
Internship: Pipeline position
Pipeline: ID
Pipeline: Name
Pipeline: Single Unit Name
Pipeline: Plural Unit Name
Created proposal
For each created proposal on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created proposal
For each created proposal on PloomesTrigger Premium
Proposal: ID
Proposal: Contact ID
Proposal: Customer name
Proposal: Title
Proposal: Date
Proposal: Number
Proposal: Contact name
Proposal: ID of the Currency Used
Proposal: Amount
Proposal: Discount
Proposal: Due Date
Proposal: Delivery Time
Proposal: Payment Method
Proposal: Description
Proposal: Observations
Proposal: Shipping Cost
Proposal: Shipping Method
Proposal: Number of Installments
Proposal: Key
Proposal: Document URL
Proposal: Creation Date
Proposal: Last Update Date
Customer: ID
Customer: Type ID
Customer: Name
Customer: Social Reason
Customer: CPF or CNPJ
Customer: CNPJ (if the contact is a company)
Customer: CPF (if the contact is a person)
Customer: Birthday
Customer: Next birthday
Customer: Previous birthday
Customer: Observations
Customer: Email
Customer: Website
Customer: Skype
Customer: Facebook
Customer: City
Customer: State
Customer: Country
Customer: Position
Customer: Department
Customer: Address
Customer: Address Number
Customer: Address Complement
Customer: Neighborhood
Customer: Zip Code
Customer: Zip Code abroad
Customer: Marketing Email
Customer: CNAE Code
Customer: CNAE Name
Customer: CNAE Secondary Name
Customer: Phone Numbers (comma separated)
Contacted: ID
Contact: Type ID
Contact: Name
Contact: Legal Name
Contact: Legal Registration
Contact: CNPJ
Contact: CPF
Contact: Birthday
Contact: Next birthday
Contact: Previous birthday
Contact: Observations
Contact: Email
Contact: Website
Contact: Skype
Contact: Facebook
Contact: City
Contact: State
Contact: Country
Contact: Position
Contact: Department
Contact: Address
Contact: Address Number
Contact: Address Supplement
Contact: Neighborhood
Contact: Zip Code
Contato: Zipcode
Contact: Marketing Email
Contact: CNAE Code
Contact: CNAE Name
Contact: CNAE Secondary Name
Contact: Telephone Numbers (separated by comma)
Card: ID
Card: Name
Card: Contact name
Card: Person's name
Card: Card pipeline ID
Card: ID of the deal stage on the card
Card: Card status ID
Card: Card creation date
Card: Card completion date
Card: Amount
Card: Amount negotiated at the beginning of the negotiation
Card: Card time in days
Card: Card time in hours
Products: Product Name (separated by commas)
Products: Quantity (separated by commas)
Products: Unit price (separated by commas)
Products: Discount (separated by commas)
Products: Total sales (separated by commas)
Products: Product Code (separated by commas)
Products: Name with Quantity and Units Sold
Products: Names, quantities, and unit prices (separated by commas)
Internship: ID
Internship: Name
Stage: Pipeline ID
Stage: Last stage of the pipeline?
Internship: Pipeline position
Pipeline: ID
Pipeline: Name
Pipeline: Single Unit Name
Pipeline: Plural Unit Name
Included new order
For each new order added on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Included new order
For each new order added on Olist ERP (Tiny ERP)Trigger
Identification number
Order number
Request Date
Forecast date
Description of payment condition
Form of payment
Payment method
Number of installments
Carrier name
Responsible for shipping
Shipping method
Cost of shipping
Discount
Total amount of products
Purchase order number
Seller identification number
Observation
Internal observation
Order tracking code
Order tracking URL
Identifier of the invoice referenced by the sale
Name of the deposit linked by the sale
Order status
Total amount
Total amount (comma separated)
ecommerce order number
Order markers (Description)
Order installments
Order item list
Order seller name
Name of the e-commerce
Order number in e-commerce
Description of the sales channel linked to e-commerce
Customer code
Customer name
Customer's trade name
Customer person type
Customer CPF or CNPJ
Customer state registration
Customer ID
Customer address
Customer address number
Customer address complement
Customer neighborhood
Customer Zip Code
Customer city
Customer UF
Customer phone
Customer email
Name of delivery recipient
Type of delivery person
CPF or CNPJ for delivery
Delivery address
Delivery address number
Delivery address complement
Delivery neighborhood
Delivery Zip Code
Delivery city
UF delivery
Delivery phone
Summary of items (Description - Quantity). Separated by semicolons.
Summary of items (Description - Quantity). Separated by semicolons.
Resumo dos itens (Descrição - Quantidade). Separado por vírgula
Resumo dos itens (Descrição - SKU - Quantidade). Separado por vírgula
Description of items separated by commas
Quantity of items separated by comma
Unit amount of items separated by commas
Comma-separated item SKUs
Achieved status
When an order reaches a certain status on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Achieved status
When an order reaches a certain status on Olist ERP (Tiny ERP)Trigger
Identification number
Sales order number in Tiny
Date of sale
Expected delivery date
Payment terms
Method of receipt
Payment method
Number of installments
Carrier name
Responsible for shipping
Shipping method
Cost of shipping
Discount
Total amount of products
Sale details: Order number
Seller identification number
Observation
Internal observation
Order tracking code
Order tracking URL
Identifier of the invoice referenced by the sale
Name of the deposit linked to the sale
Order status
Total amount
Total amount (comma separated)
ecommerce order number
Order markers (Description)
Order installments
Order item list
Seller's name
Nome do ecommerce
Código do pedido do ecommerce
Descrição do canal de venda do ecommerce
Customer code
Customer name
Customer's trade name
Customer person type
Customer CPF/CNPJ
Customer state registration
Customer ID
Customer address
Customer address number
Customer address complement
Customer address neighborhood
Customer address Zip Code
City of customer address
UF of the customer's address
Customer phone
Customer email
Name of delivery recipient
Type of delivery person
Delivery CPF/CNPJ
Delivery address
Delivery address number
Delivery address complement
Delivery address neighborhood
Delivery address Zip Code
City of delivery address
State of delivery address
Delivery phone
Summary of items (Description - Quantity). Separated by semicolon
Summary of items (Description - Quantity - Amount). Separated by comma
Summary of items (Description - Quantity). Separated by comma
Resumo dos itens (Descrição - SKU - Quantidade). Separado por ponto e vírgula
Description of items separated by commas
Quantity of items separated by comma
Unit amount of items separated by commas
Comma-separated item SKUs
Create or update client
create/update a customer on PloomesHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update client
create/update a customer on PloomesAction
Person: Name
Person: Email
Company: Social Name
Person: CPF
Person: Position
Email do responsável
Person: Department
Person: Birthday
Person: Phone
Company: Company Name
Company: Email
Company: CNPJ
Person: Phone
Company: Origin
Company: Operating Segment
Company: Website
Company: Skype User
Company: Facebook User
Person Address: State
Person Address: City
Person Address: Street
Person Address: Number
Person Address: Complement
Person Address: Neighborhood
Person Address: Zip Code
Company Address: State
Company Address: City
Company Address: Street
Company Address: Address Number
Company Address: Address Complement
Company Address: Bairro do Address
Company Address: Zip Code
Company: CNAE Code
Include accounts receivable
include an account receivable on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
1. An accounts receivable will be added on Olist ERP (Tiny ERP)
2. A contact associated with the accounts receivable will be added on Olist ERP (Tiny ERP)
All happening in a single automation! ✨
Include accounts receivable
include an account receivable on Olist ERP (Tiny ERP)Action
Due date Required
Amount Required
Mark bill as received
Date of issue
Document number
Customer name Required
Customer person type
Customer CPF or CNPJ
Customer state registration
Customer ID
Customer address
Customer address number
Customer address complement
Customer neighborhood
Customer Zip Code
Customer city
Customer UF
Customer country
Customer phone
Customer email
Historic
Category selection mode
Category
Category
Method of receipt
Type of occurrence
Due date
Number of installments
Create sales order (single item)
create a sales order on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
1. A sales order will be created on Olist ERP (Tiny ERP)
2. A contact associated with the sales order will be created/updated on Olist ERP (Tiny ERP)
3. An item will be deducted from Olist ERP (Tiny ERP) inventory
All happening in a single automation! ✨
Create sales order (single item)
create a sales order on Olist ERP (Tiny ERP)Action Premium
Order date
Order predicted date
Customer name Required
Item Description Required
Item code
Item unit Required
Item Quantity Required
Item unit price Required
Item type Required
Item origin Required
Installment period
Número de parcelas
Gap between installments
Forma de recebimento das parcelas do pedido.
Customer person type
Nome fantasia do cliente
Customer CPF or CNPJ
Código do cliente
Customer state registration
Customer address
Customer address number
Customer address complement
Customer neighborhood
Customer Zip Code
Customer city
Customer UF
Customer country
Customer phone
Customer email
Order markers
How to receive the order
Payment method
Carrier name
Shipping on account
Cost of shipping
Shipping method
Shipping method
Discount amount
Other expenses
Purchase order number
Order observation
Internal order observation
Order status
Seller selection method
Order seller
Order seller
Order identification number in e-commerce
Platform sending the order
Name of the intermediary
CNPJ of the transaction intermediary
CNPJ of the intermediary's payment institution
Name of the nature of operation
Create or update card
create/update a card on PloomesHow it works:
Whenever something happens on the source app
1. A card will be created/updated from a pipeline stage on Ploomes
2. A person associated with this card will be created/updated on Ploomes
3. A company associated with this card will be created/updated on Ploomes
4. If desired, the created/updated card can be assigned to a salesperson or distributed among registered salespeople on Ploomes (Round Robin)
All happening in a single automation! ✨
Create or update card
create/update a card on PloomesAction
Choose the sellers who will be responsible for the cards created
List of sellers
Seller's email
Title Required
Start date
Amount
Initial amount
Person: Name
Person: Email
Person: Phone
Company: Social Name
Person: CPF
Company: Name
Company: Email
Company: CNPJ
Company: Website
Company: Facebook
Company Address: Street
Company Address: Number
Company Address: Complement
Company Address: Neighborhood
Company Address: Zip Code
Company Address: State
Company Address: City
Person: Birthday
Person Address: Street
Person Address: Number
Person Address: Complement
Person Address: Neighborhood
Person Address: Zip Code
Person Address: State
Person Address: City
Include accounts payable
include an account payable on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
1. An accounts payable will be added on Olist ERP (Tiny ERP)
2. A supplier associated with the accounts payable will be added on Olist ERP (Tiny ERP)
All happening in a single automation! ✨
Include accounts payable
include an account payable on Olist ERP (Tiny ERP)Action
Maturity Required
Amount Required
Date of issue
Document number
Provider's name Required
Supplier person type
Supplier's CPF or CNPJ
Código do fornecedor
Supplier state registration
Supplier ID
Supplier address
Supplier address number
Supplier address supplement
Supplier neighborhood
Supplier Zip Code
Supplier city
Supplier UF
Supplier country
Supplier phone number
Supplier email
Historic
Category selection mode
Category
Category
Type of occurrence
Due date
Number of installments
Include or update customer/vendor
include or update a customer/supplier on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Include or update customer/vendor
include or update a customer/supplier on Olist ERP (Tiny ERP)Action
Type Required
Name or business name of the Contact Required
Situation Required
Fantasy name
Kind of person
Nome fantasia do cliente
CPF or CNPJ
Código do contato
Legal Entity: state registration
RG
Legal Entity: municipal registration
Type of deal
Address
Address number
Address complement
Neighborhood
Zip Code
City
UF
Foreign: Country
Billing address
Billing address number
Address billing add-on
Billing district
Billing Zip Code
Billing city
Billing UF
Contact phone
Fax
Contact cell phone
Contact email
Email to send nfe
Web site
Legal Entity: Tax regime code
Individual and Foreigner in Brazil: Marital status
Individual and Foreigner in Brazil: Profession
Individual and Foreigner in Brazil: Sex
Individual and Foreigner in Brazil: Date of birth
Individual and Foreigner in Brazil: Birthplace
Individual and Foreigner in Brazil: Father’s name
Individual and Foreigner in Brazil: Father's CPF
Individual and Foreigner in Brazil: Mother’s name
Individual and Foreigner in Brazil: Mother's CPF
Credit limit
General observations
Add NFS-e
add an NFS-e on Olist ERP (Tiny ERP)How it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Add NFS-e
add an NFS-e on Olist ERP (Tiny ERP)Action
customer name Required
customer cpf/cnpj
customer address
customer address number
add the customer's address
neighborhood of the customer's address
customer address Zip Code
city of customer address
uf of customer address
customer phone
customer email
service description Required
service amount Required
Deduct ISS (ISS Withheld) Required
Didn't find your use case? Send suggestion.
Automate Ploomes and Olist ERP (Tiny ERP) with Pluga integrations
Explore automation templates
For each won proposal on Ploomes, create a sales order on TinyERP
EXPLORE For each won card on Ploomes, include an account receivable on TinyERP
EXPLORE For each won proposal on Ploomes, include an account receivable on TinyERP
EXPLORE For each won card on Ploomes, include an account payable on TinyERP referring to a fee
EXPLORE For each won proposal on Ploomes, include an account payable on TinyERP referring to a fee
EXPLORE For each created client on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE When a card reaches a funnel stage on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each created card on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each won card on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each lost card on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each created proposal on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each won proposal on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each lost proposal on Ploomes, include or update a customer/supplier on TinyERP
EXPLORE For each new order added on TinyERP, create/update a card on Ploomes
EXPLORE When a new customer or supplier is included on TinyERP, create/update a card on Ploomes
EXPLORE For each won card on Ploomes, create a sales order on TinyERP
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 Ploomes + Olist ERP (Tiny ERP)
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. 
Ploomes
CRMPloomes is a CRM platform that works with process automation, proposal generation, orders, and contracts. Its features help organize contacts, track business opportunities, and improve the productivity of sales teams.
Integrations with Ploomes Visit Ploomes Olist ERP (Tiny ERP)
ERPOlist ERP is an ideal management system for micro or small businesses due to its modularity and intuitiveness. It enables automation of sales, invoice issuance, and efficient management of products, listings, and inventory.
Integrations with Olist ERP (Tiny ERP) Visit Olist ERP (Tiny ERP)