Connect Ploomes with MercadoPago
Unlock the superpowers of Ploomes + MercadoPago and automate your tasks without having to write a single line of code.
Ploomes and MercadoPago
your way
Check out the available triggers and actions in the automation of apps Ploomes + MercadoPago
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: 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: 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
Cancelled payment
For each cancelled payment on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cancelled payment
For each cancelled payment on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
card owner name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
Declined payment
For each declined payment on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Declined payment
For each declined payment on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
card owner name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
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: 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: 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: 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
Issued chargeback
For each chargeback on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Issued chargeback
For each chargeback on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
card owner name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
Payment in dispute
For each disputed payment on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Payment in dispute
For each disputed payment on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
card owner name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
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: 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: 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
Approved payment
For each approved payment on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved payment
For each approved payment on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
owner card full name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
Refunded payment
For each refunded payment on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refunded payment
For each refunded payment on MercadoPagoTrigger
payment id
payment creation date
payment approval date
payment update date
payment release date
payment creation date in DD/MM/YYYY
payment approval date in DD/MM/YYYY
payment update date in DD/MM/YYYY
payment release date in DD/MM/YYYY
seller code
operation type
free market - buyer first name
free market - buyer last name
free market - nickname buyer
free market - document number
free market - standard document
email do usuário
typical buyer
buyer id
buyer address Zip Code
buyer street address
buyer address number
buyer email
buyer document type
buyer document number
DDD phone buyer
buyer phone number
extension phone buyer
buyer name
buyer surname
binary mode
live mode
type request
request id
external id
description
coin
transaction amount
transaction amount (formatted in R$)
sales management cost
sales fee
Financing Rates
Sum of sales fees
Shipping fee
transaction amount withdrawn
coupon amount
campaign id
coupon code
transaction details financing entity id
transaction details amount received by seller
transaction details amount received by the seller (formatted in R$)
transaction id
transaction details amount paid by customer
transaction details total installment amount
transaction details exceeded amount paid
transaction details source url identifier
transaction details reference id
financing entity schema id
status
status detail
status captured
bank identifier
payment method id
issuer id
type of payment method
id card
card last 4 digits
card first 6 digits
expiry year card
month due card
creation date card
card last updated date
card owner name
owner card formatted name
card owner number
owner card document type
Barcode
additional information: generated barcode
source descriptor
number of installments
notification url
additional buyer information customer's first name
additional information buyer last name of customer
additional information buyer phone area code
additional information buyer phone number
additional buyer information Zip Code
additional buyer information street name
additional buyer information street number
additional buyer information customer registration date
additional buyer information customer Zip Code
additional information buyer street name of customer
additional information buyer customer street number
additional buyer information customer address complement
additional information buyer department customer address
additional information description of items separated by commas
additional information item titles separated by commas
additional information total amount of items
details of shipping charges
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
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
Create customer
create a customer on MercadoPagoHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create customer
create a customer on MercadoPagoAction
customer name
customer's last name
customer email
Didn't find your use case? Send suggestion.
Automate Ploomes and MercadoPago with Pluga integrations
Explore automation templates
For each refunded payment on Mercado Pago, create/update a customer on Ploomes
EXPLORE For each declined payment on Mercado Pago, create/update a customer on Ploomes
EXPLORE For each created payment on Mercado Pago, create/update a customer on Ploomes
EXPLORE For each cancelled payment on Mercado Pago, create/update a customer on Ploomes
EXPLORE For each approved payment on Mercado Pago, create/update a customer on Ploomes
EXPLORE For each approved payment on Mercado Pago, create/update a card on Ploomes
EXPLORE For each cancelled payment on Mercado Pago, create/update a card on Ploomes
EXPLORE For each created payment on Mercado Pago, create/update a card on Ploomes
EXPLORE For each declined payment on Mercado Pago, create/update a card on Ploomes
EXPLORE For each refunded payment on Mercado Pago, create/update a card on Ploomes
EXPLORE For each created proposal on Ploomes, create a customer on MercadoPago
EXPLORE For each created client on Ploomes, create a customer on MercadoPago
EXPLORE When a card reaches a funnel stage on Ploomes, create a customer on MercadoPago
EXPLORE For each created card on Ploomes, create a customer on MercadoPago
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 + MercadoPago
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 MercadoPago
PaymentMercadoPago is an online payment platform from Mercado Livre, offering options to make payments, receive payments, manage subscriptions, and more.
Integrations with MercadoPago Visit MercadoPago