Connect Pagar.me with Ploomes
Unlock the superpowers of Pagar.me + Ploomes and automate your tasks without having to write a single line of code.
Pagar.me and Ploomes
your way
Check out the available triggers and actions in the automation of apps Pagar.me + Ploomes
Approved payment
For each approved payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved payment
For each approved payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
código
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
ticket: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Acquirer fee (in cents) [only pagar.me 1.0]
Acquirer fee [only pagar.me 1.0]
Acquirer fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
List of IDs of sales intermediaries [only pagar.me 1.0]
List of amounts per sales intermediary [only pagar.me 1.0]
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
Declined payment
For each declined payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Declined payment
For each declined payment on Pagar.meTrigger
transaction id [only pagar.me 1.0]
tid of the acquirer
not as a buyer
status
código
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
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
Created payment
For each created payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
Created subscription
For each created subscription on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each created subscription on Pagar.meTrigger
Transaction: ID
Subscription: Creation date
Subscription: Creation date (format - DD/MM/YYYY)
Subscription: Creation hour (format - H:M:S)
Subscription: Creation date (format - DD/MM/YYYY - H:M:S)
Subscription: Update date
Subscription: Update date (format - DD/MM/YYYY)
Subscription: Update date (format - H:M:S)
Subscription: Update date (format - DD/MM/YYYY - H:M:S)
Subscribed: Total price (in cents)
Subscribed: Total price
Subscribed: Total price (format - R$)
Client: Telephone (DDI)
Client: Telephone (DDD)
Client: Telephone
Client: Document
Client: Email
Client: Name
Address: Street
Address: Number
Address: Complement
Address: Neighborhood
Address: City
Address: State
Address: CEP
Subscribed: Current period start
Subscribed: Current period start (format - DD/MM/YYYY)
Subscribed: Current period start (format - H:M:S)
Subscribed: Current period start (format - DD/MM/YYYY - H:M:S)
Subscribed: Current period end
Subscribed: Current period end (format - DD/MM/YYYY)
Subscribed: Current period end (format - H:M:S)
Subscribed: Current period end (format - DD/MM/YYYY - H:M:S)
Transaction: Payment method
Transaction: Card holder name
Transaction: Card brand
Subscribed: Metadata origin
Subscribed: Metadata internal name
Subscribed: Items description resume, separated by comma [only pagar.me 2.0]
Subscribed: Quantity items resume, separated by comma [only pagar.me 2.0]
Subscribed: Items price resume, separated by comma [only pagar.Me 2.0]
Subscribed: Description, price and quantity resume, separated by comma [only pagar.me 2.0]
Subscribed: Next billing dates [only pagar.me 2.0]
Subscribed: Next billing dates (format - DD/MM/YYYY) [only pagar.me 2.0]
Subscribed: Next billing dates (format - H:M:S) [only pagar.me 2.0]
Subscribed: Next billing dates (format - DD/MM/YYYY - H:M:S) [only pagar.Me 2.0]
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
Refunded payment
For each refunded payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refunded payment
For each refunded payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
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
Create customer
create a customer on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create customer
create a customer on Pagar.meAction
Customer: Name Required
Customer: Email Required
Customer: CPF/CNPJ
Address: Street Required
Address: Number Required
Address: Additional information
Address:neighborhood Required
Address: City
Address: State
Address: Country
Address: Zip Code Required
Customer: Area code of the phone Required
Customer: Telephone Required
Customer: International dialing 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
Generate billing
generate a billing on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate billing
generate a billing on Pagar.meAction
Payment method Required
Payment deadline Required
Amount Required
Customer email Required
Customer name
Customer Type Required
CPF/CNPJ (Individual Person Registry/National Legal Entity Registry) Required
Description
Notify customer of billing
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
Didn't find your use case? Send suggestion.
Automate Pagar.me and Ploomes with Pluga integrations
Explore automation templates
For each created payment on Pagar.me, create/update a customer on Ploomes
EXPLORE For each created payment on Pagar.me, create/update a card on Ploomes
EXPLORE For each declined payment on Pagar.me, create/update a customer on Ploomes
EXPLORE For each declined payment on Pagar.me, create/update a card on Ploomes
EXPLORE For each refunded payment on Pagar.me, create/update a customer on Ploomes
EXPLORE For each refunded payment on Pagar.me, create/update a card on Ploomes
EXPLORE For each approved payment on Pagar.me, create/update a customer on Ploomes
EXPLORE For each approved payment on Pagar.me, create/update a card on Ploomes
EXPLORE For each won card on Ploomes, generate a billing on Pagar.me
EXPLORE For each won proposal on Ploomes, generate a billing on Pagar.me
EXPLORE For each created client on Ploomes, create a customer on Pagar.me
EXPLORE When a card reaches a funnel stage on Ploomes, create a customer on Pagar.me
EXPLORE For each created card on Ploomes, create a customer on Pagar.me
EXPLORE For each won card on Ploomes, create a customer on Pagar.me
EXPLORE For each lost card on Ploomes, create a customer on Pagar.me
EXPLORE For each created proposal on Ploomes, create a customer on Pagar.me
EXPLORE For each won proposal on Ploomes, create a customer on Pagar.me
EXPLORE For each lost proposal on Ploomes, create a customer on Pagar.me
EXPLORE For each subscribed created on Pagar.me, create/update a customer on Ploomes
EXPLORE For each subscribed created on Pagar.me, create/update a card on Ploomes
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 Pagar.me + Ploomes
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. 
Pagar.me
PaymentPagar.me is an online payment platform offering solutions for businesses to receive payments via credit card, payslip, bank transfer, and other payment methods.
Integrations with Pagar.me Visit Pagar.me 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