Automate PagBank with Meets
Unlock the superpowers of PagBank + Meets and automate your tasks without having to write a single line of code.
PagBank and Meets
your way
Check out the available triggers and actions in the automation of apps PagBank + Meets
Approved payment
For each approved payment on PagBankHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved payment
For each approved payment on PagBankTrigger
transaction id
reference
status
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
Date on which the transaction amount will be available in the seller's account
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY)
Date on which the transaction amount will be available in the seller's account (formatted - H:M:S)
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY - H:M:S)
total amount
total amount (formatted)
amount received
received amount (formatted)
amount of fees
amount of fees (formatted)
items id
items description
items quantity
amount items
type of payment method
the payment method
payment link
installments
Nome do titular do PIX
buyer email
buyer name
phone buyer
address street
address number
full address
address neighborhood
city address
state address
Zip Code address
Refunded payment
For each refunded payment on PagBankHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refunded payment
For each refunded payment on PagBankTrigger
transaction id
reference
status
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
Date on which the transaction amount will be available in the seller's account
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY)
Date on which the transaction amount will be available in the seller's account (formatted - H:M:S)
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY - H:M:S)
total amount
total amount (formatted)
amount received
received amount (formatted)
amount of fees
amount of fees (formatted)
items id
items description
items quantity
amount items
type of payment method
the payment method
payment link
installments
Nome do titular do PIX
buyer email
buyer name
phone buyer
address street
address number
full address
address neighborhood
city address
state address
Zip Code address
Opportunity reaches stage in the sales pipeline
When an opportunity reaches a certain funnel stage on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity reaches stage in the sales pipeline
When an opportunity reaches a certain funnel stage on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Declined payment
For each declined payment on PagBankHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Declined payment
For each declined payment on PagBankTrigger
transaction id
reference
status
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
Date on which the transaction amount will be available in the seller's account
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY)
Date on which the transaction amount will be available in the seller's account (formatted - H:M:S)
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY - H:M:S)
total amount
total amount (formatted)
amount received
received amount (formatted)
amount of fees
amount of fees (formatted)
items id
items description
items quantity
amount items
type of payment method
the payment method
payment link
installments
Nome do titular do PIX
buyer email
buyer name
phone buyer
address street
address number
full address
address neighborhood
city address
state address
Zip Code address
Disputed payment
For each disputed payment on PagBankHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Disputed payment
For each disputed payment on PagBankTrigger
transaction id
reference
status
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
Date on which the transaction amount will be available in the seller's account
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY)
Date on which the transaction amount will be available in the seller's account (formatted - H:M:S)
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY - H:M:S)
total amount
total amount (formatted)
amount received
received amount (formatted)
amount of fees
amount of fees (formatted)
items id
items description
items quantity
amount items
type of payment method
the payment method
payment link
installments
Nome do titular do PIX
buyer email
buyer name
phone buyer
address street
address number
full address
address neighborhood
city address
state address
Zip Code address
Lost opportunity
For each lost opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost opportunity
For each lost opportunity on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Created payment
For each created payment on PagBankHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on PagBankTrigger
transaction id
reference
status
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
Date on which the transaction amount will be available in the seller's account
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY)
Date on which the transaction amount will be available in the seller's account (formatted - H:M:S)
Date on which the transaction amount will be available in the seller's account (formatted - DD/MM/YYYY - H:M:S)
total amount
total amount (formatted)
amount received
received amount (formatted)
amount of fees
amount of fees (formatted)
items id
items description
items quantity
amount items
type of payment method
the payment method
payment link
installments
Nome do titular do PIX
buyer email
buyer name
phone buyer
address street
address number
full address
address neighborhood
city address
state address
Zip Code address
Won opportunity
For each conquered opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won opportunity
For each conquered opportunity on MeetsTrigger
Opportunity ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
Name of the user responsible for the opportunity
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Created opportunity
For each created opportunity on MeetsHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created opportunity
For each created opportunity on MeetsTrigger
ID
Opportunity status
Opportunity registration date
Description of the opportunity
Opportunity stage ID
Opportunity stage
Opportunity Pipeline ID
Opportunity pipeline
User ID responsible for the opportunity
RESPONSIBLE USER
Reason for missing the opportunity
Opportunity loss reason ID
Total amount
Customer ID
Customer's area of activity
Customer origin
Address neighborhood
Customer cell phone
Address: Zip Code
Address: City
Customer name
Company CNPJ
Customer CPF
Customer email
Customer phone
Customer Address
Address: Number
Full address
Kind of person
Address: UF
Add or update opportunity
register an opportunity on MeetsHow it works:
Whenever something happens on the source app
1. An deal will be added/updated on Meets
2. A person associated with this deal will be created/updated on Meets
All happening in a single automation! ✨
Add or update opportunity
register an opportunity on MeetsAction
Opportunity Title Required
Opportunity Tag/Status
Responsible Required
Amount
Products/Services
Name/Corporate Name
Kind of person Required
CPF
CNPJ
Cell phone
Telephone
Occupation area
Origin
City
State
Didn't find your use case? Send suggestion.
Automate PagBank and Meets with Pluga integrations
Explore automation templates
For each declined payment on PagBank, register an opportunity on Meets
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 PagBank + Meets
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. 
PagBank
PaymentPagBank (also known by its former name, PagSeguro) is a Brazilian online payment platform that offers options to receive payments in online stores, in-person, and through payment links, with security and ease.
Integrations with PagBank Visit PagBank Meets
CRMMeets is a CRM platform designed to simplify and streamline contact management. The app allows you to visualize your entire sales process, tracking the right activities to be performed.
Integrations with Meets Visit Meets