Automate PagBank with Moskit CRM
Unlock the superpowers of PagBank + Moskit CRM and automate your tasks without having to write a single line of code.
PagBank and Moskit CRM
your way
Check out the available triggers and actions in the automation of apps PagBank + Moskit CRM
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
Created deal
For each created deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created deal
For each created deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Won deal
For each won deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Won deal
For each won deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
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 deal
For each lost deal on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Lost deal
For each lost deal on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Deal: Reason for loss
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
Created contact
For each created contact on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created contact
For each created contact on Moskit CRMTrigger
Name
Main Phone
E-mail Principal
Telephone numbers separated by comma
Emails separated by comma
Site
Creation date
Created by
Responsible
Comments
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Deal reached stage
When a deal reaches a funnel stage on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Deal reached stage
When a deal reaches a funnel stage on Moskit CRMTrigger
Deal: ID
Deal: Name
Deal: Expected Date
Deal: Amount in cents
Deal: Status
Deal: Number of projects running
Deal: Number of archived projects
Deal: Created by
Deal: Responsible
Deal: Stage
Deal: Pipeline
Deal: Pipeline ID
Deal: Amount
Deal: Creation date
Deal: Date of last stage change
Deal: Closing date
Deal: Product SKU separated by comma
Deal: Name of products separated by comma
Deal: SKU and Product name separated by comma
Deal: Name, quantity and price of products separated by commas
Contact: Name
Contact: Main Telephone
Contact: Principal Email
Contact: Telephone numbers separated by commas
Contact: Comma-separated emails
Contact: Website
Contact: Creation Date
Contact: Created by
Contact: Responsible
Contact: Observations
Company: Name
Company: Main Telephone
Company: Main Email
Company: Comma separated telephone numbers
Company: Comma separated emails
Company: Website
Company: Creation Date
Company: Created by
Company: Responsible
Create or update contact
create or update a contact on Moskit CRMHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create or update contact
create or update a contact on Moskit CRMAction
Select responsible Required
Contact: Name
Contact: Email Required
Contact: CPF
Company: Name
Company: Email
Company: CNPJ
Contact: Position
Contact: Telephone
Contact: Observations
Company: Website
Company: Telephone
Company: Observations
Contact updates
Create or update deal
create or update a business on Moskit CRMHow it works:
Whenever something happens on the source app
1. A deal will be created/updated from a pipeline stage on Moskit CRM
2. A contact associated with the deal will be created/updated on Moskit CRM
3. A company associated with the deal will be created/updated on Moskit CRM
4. If desired, the created/updated deal can be assigned to a salesperson or distributed among registered salespeople on Moskit CRM (Round Robin)
All happening in a single automation! ✨
Create or update deal
create or update a business on Moskit CRMAction
Distribute new deal Required
Select sellers
Responsible
Deal Name Required
Company: Name
Contact: Name
Contact: Email
Amount
Expected date
Deal status
Closing date
Reason for loss
Update Main Company
Company: Email
Company: Telephone
Update Primary Contact
Contact: Telephone
Contact: Position
Product's name
Product SKU
Product quantity
Price of the product
Company: Website
Company: Observations
Contact: Observations
Contact updates
Didn't find your use case? Send suggestion.
Automate PagBank and Moskit CRM with Pluga integrations
Explore automation templates
For each approved payment on PagBank, create or update a contact on Moskit CRM
EXPLORE For each created payment on PagBank, create or update a business on Moskit CRM
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 + Moskit CRM
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 Moskit CRM
CRMMoskit CRM is a customer relationship management (CRM) platform that offers tools to organize contacts, track sales, automate tasks, and improve customer relationships.
Integrations with Moskit CRM Visit Moskit CRM