Connect Ploomes with Vindi Recorrência
Unlock the superpowers of Ploomes + Vindi Recorrência and automate your tasks without having to write a single line of code.
Ploomes and Vindi Recorrência
your way
Check out the available triggers and actions in the automation of apps Ploomes + Vindi Recorrência
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
Charge declined
For each declined billing on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Charge declined
For each declined billing on Vindi RecorrênciaTrigger
billing id
expiration date (formatted - DD/MM/YYYY)
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
Payment method
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
id and invoice
plan name
payment method name
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Approved invoice
For each approved invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved invoice
For each approved invoice on Vindi RecorrênciaTrigger
invoice id
expiration date (formatted - DD/MM/YYYY)
expiration date - charges (formatted - DD/MM/YYYY)
invoice url
email customer
customer name
status
total amount
total amount (text)
total amount paid of charges
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created on (day - DD)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
Payment method
Payment company code
items name
items description
Total discount amount of items (Positive)
Amount of items separated by comma
Formatted amount of items separated by comma
creation date of the item pricing scheme
charges information
charges: gateway authorization
charges: gateway response fields
cobranças: NSUs (separados por vírgula)
subscription id
plan id on subscription
plan name on subscription
Plan code upon subscription
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Fiscal Note: Id
Invoice: External integration code
Invoice: Number or reference at the government institution
Tax Note: Amount
Nota Fiscal: Status
Invoice: URL
Invoice: Description
Invoice: Date and time of issue
Invoice: Competence date
Invoice: Date and time of appointment
Invoice: Date and time of generation
Invoice: Date and time of last update
Period Cycle
Fim do período contratado
Metadata summary
Metadata amounts
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
Canceled subscription
For each subscription canceled on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Canceled subscription
For each subscription canceled on Vindi RecorrênciaTrigger
subscription id
start date (formatted - DD/MM/YYYY)
end date (formatted - DD/MM/YYYY)
date of next invoice (formatted - DD/MM/YYYY)
cancellation date (formatted - DD/MM/YYYY)
Maximum number of subscription periods
late since (formatted - DD/MM/YYYY)
plan id
plan name
Plan code upon subscription
products name
products description
email customer
customer name
status
total amount
installments
Payment method
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
billing date current period (YYYY-MM-DDTHH:mm:ss-Z)
start date of the current period (formatted - DD/MM/YYYY)
end date of the current period (formatted - DD/MM/YYYY)
customer id
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Created invoice
For each created invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created invoice
For each created invoice on Vindi RecorrênciaTrigger
id and invoice
expiration date (formatted - DD/MM/YYYY)
expiration date - charges (formatted - DD/MM/YYYY)
invoice url
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created on (day - DD)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
Payment method
items name
items description
Valor total do desconto dos itens (Positivo)
Valor dos items separado por vírgula
Valor formatado dos items separado por vírgula
data de criação do esquema de precificação dos items
charges information
charges: gateway authorization
charges: gateway response fields
subscription id
plan id on subscription
plan name on subscription
Plan code upon subscription
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
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
Charge refunded
For each reversed billing on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Charge refunded
For each reversed billing on Vindi RecorrênciaTrigger
billing id
expiration date (formatted - DD/MM/YYYY)
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
Payment method
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
id and invoice
plan name
payment method name
Customer CPF/CNPJ
customer status
External code
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Created subscription
For each subscription created on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each subscription created on Vindi RecorrênciaTrigger
subscription id
start date (formatted - DD/MM/YYYY)
start day (formatted - DD)
end date (formatted - DD/MM/YYYY)
date of next invoice (formatted - DD/MM/YYYY)
cancellation date (formatted - DD/MM/YYYY)
Maximum number of subscription periods
late since (formatted - DD/MM/YYYY)
plan id
plan name
Plan code upon subscription
products name
products description
email customer
customer name
total discount amount
status
total amount
installments
Payment method
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
billing date current period (YYYY-MM-DDTHH:mm:ss-Z)
start date of the current period (formatted - DD/MM/YYYY)
end date of the current period (formatted - DD/MM/YYYY)
customer id
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
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 subscription
create a subscription on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create subscription
create a subscription on Vindi RecorrênciaAction
customer name Required
email customer
Subscription start date
Payment method Required
Plan selection form
Plan
Plan
Plan
Plan interval count
Plan billing cycles
plan billing trigger type
billing trigger day
plan code
plan description
plan item name
plan item price
plan item code
plan item description
plan item unit of measurement
telephone
cell phone
document
Update customer based on
Customer Code
Zip Code address
address street
address number
full address
address neighborhood
city address
state address
country address
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 invoice
Create invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create invoice
Create invoice on Vindi RecorrênciaAction
Update customers
Customer: Name Required
Customer: Email
Customer: CPF/CNPJ
Invoice: Payment method Required
Invoice: Due date
Item: Name Required
Item price Required
Item: Quantity
Item: Code
Customer: Telephone
Customer: Cellphone
Customer: Code
Customer: Zip code
Customer: Street
Customer: Address number
Customer: Address complement
Customer: Neighborhood
Customer: City
Customer: State
Customer: Country
Create customer
create a customer on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create customer
create a customer on Vindi RecorrênciaAction
name Required
telephone
cell phone
document
External code
Zip Code address
address street
address number
full address
address neighborhood
city address
state address
country address
Didn't find your use case? Send suggestion.
Automate Ploomes and Vindi Recorrência with Pluga integrations
Explore automation templates
For each created invoice on Vindi Recorrência, create/update a customer on Ploomes
EXPLORE For each approved invoice on Vindi Recorrência, create/update a customer on Ploomes
EXPLORE For each declined billing on Vindi Recorrência, create/update a customer on Ploomes
EXPLORE For each reversed billing on Vindi Recorrência, create/update a customer on Ploomes
EXPLORE For each created invoice on Vindi Recorrência, create/update a card on Ploomes
EXPLORE For each approved invoice on Vindi Recorrência, create/update a card on Ploomes
EXPLORE For each declined billing on Vindi Recorrência, create/update a card on Ploomes
EXPLORE For each reversed billing on Vindi Recorrência, create/update a card on Ploomes
EXPLORE For each won card on Ploomes, create a customer on Vindi Recorrência
EXPLORE For each won proposal on Ploomes, create a customer on Vindi Recorrência
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 + Vindi Recorrência
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 Vindi Recorrência
PaymentVindi Recorrência is a payment management platform that helps businesses automate billing, manage subscriptions, default control, and improve financial management.
Integrations with Vindi Recorrência Visit Vindi Recorrência