Connect Asaas with Ploomes
Unlock the superpowers of Asaas + Ploomes and automate your tasks without having to write a single line of code.
Asaas and Ploomes
your way
Check out the available triggers and actions in the automation of apps Asaas + Ploomes
Created payment
For each created payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on AsaasTrigger
id
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer address street
Customer address number
Customer address complement
Customer address neighborhood
Customer address Zip Code
Customer address State
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Billing status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last invoice view
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bankslip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Date the withdrawal becomes available
Created subscription
For each created subscription on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each created subscription on AsaasTrigger
Subscription ID
Subscription creation date
Customer ID
Customer creation date
Customer name
Customer email
Customer company
Customer landline
Customer's cell phone
Address: Customer's street
Address: Customer number
Address: Customer Complement
Address: Customer neighborhood
Address: Customer Zip Code
Customer CPF/CNPJ
Customer type
Additional customer emails
Customer identifier in your system
Disable sending billing notifications?
Additional observations
Customer municipal registration
Customer state registration
Address: Customer city
Address: Customer State
Address: Customer's country
Customer creation date formatted in 'year-month-day'
Customer groups
Payment link
Subscription amount
Billing frequency
Subscription description
Form of payment
Subscription status
Subscription identifier on your system
Fine percentage
Interest percentage per month
First charge: invoice URL
Subscription creation date formatted in 'year-month-day'
Due date of the first monthly installment formatted in 'year-month-day'
First monthly payment due
Deadline for monthly payments to be due
Maximum number of monthly payments to be generated
Discount amount to be applied to the charge amount
Days before expiration to apply discount.
Type of discount
Deadline for monthly installments to be due formatted in 'year-month-day'
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
Reversed payment
For each refunded payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Reversed payment
For each refunded payment on AsaasTrigger
id
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer's public address
Address number
Address complement
Neighborhood
Customer address Zip Code
Customer address state
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Billing status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last invoice view
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bank slip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Confirmed payment
For each confirmed payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Confirmed payment
For each confirmed payment on AsaasTrigger
ID
Payment date created
Payment due date
Payment original due date
Payment value
Payment net value
External payment reference
Customer ID
Customer name
Customer Email
Customer Email Additionals
Customer Company
Customer CPF/CNPJ
Customer phone
Customer mobile phone
Customer Address
Address number
Address complement
Neighborhood
Customer postal code
Customer state
Customer city
Customer country
Customer date create
External customer reference
Customer groups separated by comma.
Customer date create in 'year-month-day' format
Discount value
Discount due date limit days
Discount type
Interest value
Fine percentage
Billing type
Status
Payment description
Payment original value
Calculated interest value
Invoice last viewed date
Bank slip last viewed date
Payment confirmed date (Valid only for credit card)
Asaas payment date
Customer payment date
Invoice URL
Invoice number
Link to the bank slip file
Payment creation fee
Payment deleted
Payment date created in 'year-month-day' format
Payment due date in 'year-month-day' format
Payment original due date in 'year-month-day' format
Invoice last viewed date in 'year-month-day' format
Bank slip last viewed date in 'year-month-day' format
Payment confirmed date (Valid only for credit card) in 'year-month-day' format
Withdrawal available at (Valid only for credit card) in 'year-month-day' format
Asaas payment date in 'year-month-day' format
Customer payment date in 'year-month-day' format
Credit data in 'year-month-day'
Withdrawal available at (any billing type) in 'year-month-day' format
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Withdrawal available at (Valid only for credit card)
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
Overdue payment
For each overdue payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Overdue payment
For each overdue payment on AsaasTrigger
Billing ID
Charge creation date
Billing due date
Original billing due date
Charge amount
Net charge amount
External billing identifier
Customer ID
Customer name
Customer email
Additional customer emails
Customer company
Customer CPF or CNPJ
Customer phone
Customer's cell phone
Customer's public address
Address number
Address complement
Neighborhood
Customer address Zip Code
Customer address State
City of customer address
Country of customer address
Customer creation date
External customer identifier
Comma-separated customer groups.
Customer creation date formatted in 'year-month-day'
Discount amount
Days before expiration to apply discount
Type of discount
Interest percentage
Fine percentage
Form of payment
Status
Description of the charge
Original charge amount
Calculated amount of interest and fine that must be paid after the charge is due
Date of last viewing of the invoice
Date of last viewing of the bank slip
Charge confirmation date (Credit card only)
Bill settlement date in ASAAS
Date on which the customer paid the bank slip
Invoice in URL
Bill number
Link to the bank slip file
Charge issuance fee
Charge removed
Charge creation date formatted in 'year-month-day'
Billing due date formatted in 'year-month-day'
Original billing due date formatted in 'year-month-day'
Date of last viewing of the invoice formatted in 'year-month-day'
Date of last viewing of the bank slip formatted in 'year-month-day'
Billing confirmation date (Credit card only) formatted in 'year-month-day'
Available withdrawal date (Credit card only) formatted in 'year-month-day'
Bill settlement date in ASAAS formatted in 'year-month-day'
Date on which the customer paid the bank slip formatted in 'year-month-day'
Credit data in 'year-month-day'
Available withdrawal date (any type of charge) formatted in 'year-month-day'
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Cobrança recebida
For each received payment on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Cobrança recebida
For each received payment on AsaasTrigger
ID
Payment date created
Payment due date
Payment original due date
Payment value
Payment net value
External payment reference
Customer ID
Customer name
Customer Email
Customer Email Additionals
Customer Company
Customer CPF/CNPJ
Customer phone
Customer mobile phone
Customer Address
Address number
Address complement
Neighborhood
Customer postal code
Customer state
Customer city
Customer country
Customer date create
External customer reference
Customer groups separated by comma.
Customer date create in 'year-month-day' format
Discount value
Discount due date limit days
Discount type
Interest value
Fine percentage
Billing type
Status
Payment description
Payment original value
Calculated interest value
Invoice last viewed date
Bank slip last viewed date
Payment confirmed date (Valid only for credit card)
Asaas payment date
Customer payment date
Invoice URL
Invoice number
Link to the bank slip file
Payment creation fee
Payment deleted
Payment date created in 'year-month-day' format
Payment due date in 'year-month-day' format
Payment original due date in 'year-month-day' format
Invoice last viewed date in 'year-month-day' format
Bank slip last viewed date in 'year-month-day' format
Payment confirmed date (Valid only for credit card) in 'year-month-day' format
Withdrawal available at (Valid only for credit card) in 'year-month-day' format
Asaas payment date in 'year-month-day' format
Customer payment date in 'year-month-day' format
Credit data in 'year-month-day'
Withdrawal available at (any billing type) in 'year-month-day' format
Charge amount in cents
Net amount of the charge in cents
Unique installment identifier
Payment link: name
Payment link: installment count
Payment link: URL
Payment link: description
Payment link: billing type
Payment link: subscription cycle
Payment link: charge type
Payment link: value
Subscription
Number of payment installments
Withdrawal available at
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
Generate billing
generate a billing on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate billing
generate a billing on AsaasAction
Customer: take email into account as a uniqueness criterion?
Customer: Name Required
Customer: CPF/CNPJ Required
Billing: Amount Required
Billing: Due date Required
Billing: Description
Customer: Email
Customer: Landline
Customer: Cell phone
Customer: Company
Split payment
Split: Types of subaccounts for payment splittingAccount selection method
Split: Number of subaccount(s) or Wallet IDs
[Split 1] Select subaccount
[Split 1] Wallet ID
[Split 1] Value type
[Split 1] Value
[Split 2] Select subaccount
[Split 2] Wallet ID
[Split 2] Value type
[Split 2] Value
[Split 3] Select subaccount
[Split 3] Wallet ID
[Split 3] Value type
[Split 3] Value
[Split 4] Select subaccount
[Split 4] Wallet ID
[Split 4] Value type
[Split 4] Value
[Split 5] Select subaccount
[Split 5] Wallet ID
[Split 5] Value type
[Split 5] Value
[Split 6] Select subaccount
[Split 6] Wallet ID
[Split 6] Value type
[Split 6] Value
[Split 7] Select subaccount
[Split 7] Wallet ID
[Split 7] Value type
[Split 7] Value
[Split 8] Select subaccount
[Split 8] Wallet ID
[Split 8] Value type
[Split 8] Value
[Split 9] Select subaccount
[Split 9] Wallet ID
[Split 9] Value type
[Split 9] Value
[Split 10] Select subaccount
[Split 10] Wallet ID
[Split 10] Value type
[Split 10] Value
Billing: Payment method
Billing: External reference
Billing: Number of installments
Billing: Discount amount
Billing: Days before due date to apply discount
Billing: Type of discount
Billing: Percentage of interest per month
Billing: Type of fine
Billing: Fine
Billing: Send via post?
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Zip Code
Customer: Customer identifier in your system
Customer: Disable sending billing notifications?
Cliente: Canais de notificações a serem habilitados
Provider: Notification channels to be enabled
Customers: Notifications to enable
Customer: Notification Options
Cliente: Dias antes do vencimento para enviar a notificação
Cliente: Dias após o vencimento para enviar a notificação
Customer: Additional emails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group name
Schedule/issue invoice
Schedule/issue an invoice on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Schedule/issue invoice
Schedule/issue an invoice on AsaasAction Premium
Customer: Name Required
Customer: CPF/CNPJ Required
Invoice: Amount Required
Authorize invoice immediately Required
Invoice: Date of issue
Address: Street Name
Address: Number
Endereço: Zip Code
Invoice: Description of services
Customer: E-mail
Customer: Telephone
Customer: Mobile phone
Customer: Company
Invoice: Deductions Required
Invoice: Name of municipal service
Invoice: Municipal Service Code
Invoice: Should the service recipient withhold ISS? Required
Invoice: ISS Tax Rate Required
Invoice: COFINS Tax rate Required
Invoice: CSLL Tax rate Required
Invoice: INSS Tax rate Required
Invoice: IR Tax rate Required
Invoice: PIS Tax rate Required
Invoice: External reference
Invoice: Notes
Address: Additional Information
Address: Neighborhood
Customer: Customer identifier in your system
Customer: Disable billing notification sending?
Customer: Additional e-mails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group's name
Should email be used to find the customer?
Create or update customer
create or update a customer on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update customer
create or update a customer on AsaasAction
Customer: take email into account as a uniqueness criterion?
Customer: Name Required
Customer: CPF/CNPJ Required
Customer: Email
Customer: Landline
Customer: Cell phone
Customer: Company
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Zip Code
Customer: External identifier
Customer: Disable sending billing notifications?
Cliente: Canais de notificações a serem habilitados
Provider: Notification channels to be enabled
Customers: Notifications to enable
Customer: Notification Options
Cliente: Dias antes do vencimento para enviar a notificação
Cliente: Dias após o vencimento para enviar a notificação
Customer: Additional emails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group name
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 a subscription
create a subscription on AsaasHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create a subscription
create a subscription on AsaasAction
Customer: take email into account as a uniqueness criterion?
Customer: Name Required
Customer: CPF/CNPJ Required
Subscription: Amount Required
Subscription: Due date of the first monthly payment Required
Subscription: Frequency Required
Signature: Description
Customer: Email
Customer: Landline
Customer: Cell phone
Customer: Company
Subscription: Payment method
Subscription: Discount amount
Subscription: Days before due date to apply discount
Subscription: Discount type
Subscription: Interest percentage per month
Signature: Type of fine
Signature: Fine
Subscription: Deadline for monthly installments to be due
Subscription: Maximum number of monthly payments
Signature: Identifier on your system
Address: Public place
Address: Number
Full address
Address neighborhood
Address: Zip Code
Customer: Customer identifier in your system
Customer: Disable sending billing notifications?
Cliente: Canais de notificações a serem habilitados
Customers: Notifications to enable
Cliente: Dias antes do vencimento para enviar a notificação
Cliente: Dias após o vencimento para enviar a notificação
Customer: Additional emails
Customer: Municipal registration
Customer: State registration
Customer: Observations
Customer: Group name
Split payment
Split: Types of subaccounts for payment splittingAccount selection method
Split: Number of subaccount(s) or Wallet IDs
[Split 1] Select subaccount
[Split 1] Wallet ID
[Split 1] Value type
[Split 1] Value
[Split 2] Select subaccount
[Split 2] Wallet ID
[Split 2] Value type
[Split 2] Value
[Split 3] Select subaccount
[Split 3] Wallet ID
[Split 3] Value type
[Split 3] Value
[Split 4] Select subaccount
[Split 4] Wallet ID
[Split 4] Value type
[Split 4] Value
[Split 5] Select subaccount
[Split 5] Wallet ID
[Split 5] Value type
[Split 5] Value
[Split 6] Select subaccount
[Split 6] Wallet ID
[Split 6] Value type
[Split 6] Value
[Split 7] Select subaccount
[Split 7] Wallet ID
[Split 7] Value type
[Split 7] Value
[Split 8] Select subaccount
[Split 8] Wallet ID
[Split 8] Value type
[Split 8] Value
[Split 9] Select subaccount
[Split 9] Wallet ID
[Split 9] Value type
[Split 9] Value
[Split 10] Select subaccount
[Split 10] Wallet ID
[Split 10] Value type
[Split 10] Value
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
Didn't find your use case? Send suggestion.
Automate Asaas and Ploomes with Pluga integrations
Explore automation templates
For each overdue payment on Asaas, create/update a customer on Ploomes
EXPLORE For each received payment on Asaas, create/update a customer on Ploomes
EXPLORE For each refunded payment on Asaas, create/update a customer on Ploomes
EXPLORE For each created payment on Asaas, create/update a customer on Ploomes
EXPLORE For each overdue payment on Asaas, create/update a card on Ploomes
EXPLORE For each received payment on Asaas, create/update a card on Ploomes
EXPLORE For each refunded payment on Asaas, create/update a card on Ploomes
EXPLORE For each created payment on Asaas, create/update a card on Ploomes
EXPLORE For each won card on Ploomes, generate a billing on Asaas
EXPLORE For each won proposal on Ploomes, generate a billing on Asaas
EXPLORE When a card reaches a funnel stage on Ploomes, generate a billing on Asaas
EXPLORE For each created client on Ploomes, create or update a customer on Asaas
EXPLORE When a card reaches a funnel stage on Ploomes, create or update a customer on Asaas
EXPLORE For each created card on Ploomes, create or update a customer on Asaas
EXPLORE For each won card on Ploomes, create or update a customer on Asaas
EXPLORE For each lost card on Ploomes, create or update a customer on Asaas
EXPLORE For each created proposal on Ploomes, create or update a customer on Asaas
EXPLORE For each won proposal on Ploomes, create or update a customer on Asaas
EXPLORE For each lost proposal on Ploomes, create or update a customer on Asaas
EXPLORE For each won card on Ploomes, create a subscription on Asaas
EXPLORE For each won proposal on Ploomes, create a subscription on Asaas
EXPLORE When a card reaches a funnel stage on Ploomes, create a subscription on Asaas
EXPLORE For each created subscription on Asaas, create/update a customer on Ploomes
EXPLORE For each created subscription on Asaas, create/update a card on Ploomes
EXPLORE For each confirmed payment on Asaas, create/update a customer on Ploomes
EXPLORE For each confirmed payment on Asaas, 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 Asaas + 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. 
Asaas
PaymentAsaas is a financial management platform designed to simplify and reduce business bureaucracy. Its features include providing payment methods, handling various types of sales, and managing cash flow.
Integrations with Asaas Visit Asaas 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