Connect Pipefy with PagBank
Unlock the superpowers of Pipefy + PagBank and automate your tasks without having to write a single line of code.
Pipefy and PagBank
your way
Check out the available triggers and actions in the automation of apps Pipefy + PagBank
Created card
When a card is created on PipefyHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created card
When a card is created on PipefyTrigger
Name of card creator
Card creator email
Current phase name
Card expiration date
Title of the card
Name of users assigned to the card
Emails of users assigned to the card
Name of card tags
Card creation date
Card update date
Card update date in 'dd/mm/yyyy'
Card URL
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
Finished card
When a card is finalized on PipefyHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Finished card
When a card is finalized on PipefyTrigger
Name of card creator
Card creator email
Current phase name
Card expiration date
Title of the card
Name of users assigned to the card
Emails of users assigned to the card
Name of card tags
Card creation date
Card update date
Card update date in 'dd/mm/yyyy'
Card URL
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
Moved card
When a card is moved to a certain phase of a pipe on PipefyHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Moved card
When a card is moved to a certain phase of a pipe on PipefyTrigger
Name of card creator
Card creator email
Current phase name
Card expiration date
Title of the card
Name of users assigned to the card
Emails of users assigned to the card
Name of card tags
Card creation date
Card update date
Card update date in 'dd/mm/yyyy'
URL do card
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
Create card
create a card on PipefyHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create card
create a card on PipefyAction
Card comment
Create record in table
create a record on a table on PipefyHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create record in table
create a record on a table on PipefyAction
Didn't find your use case? Send suggestion.
Automate Pipefy and PagBank with Pluga integrations
Explore automation templates
For each approved payment on PagBank, create a card on Pipefy
EXPLORE For each approved payment on PagBank, create a record on a table on Pipefy
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 Pipefy + PagBank
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. 
Pipefy
ProjectPipefy is a flexible platform for process and workflow management. The app allows you to create and track complex tasks without relying on IT personnel to quickly automate processes, workflows, and approvals.
Integrations with Pipefy Visit Pipefy 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