Automate PagBank with ZapSign

Unlock the superpowers of PagBank + ZapSign and automate your tasks without having to write a single line of code.

PagBank and ZapSign
your way

Check out the available triggers and actions in the automation of apps PagBank + ZapSign

PagBank-modal-icon

Approved payment

For each approved payment on PagBank

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

PagBank-icon

Approved payment

For each approved payment on PagBank

Trigger

Information from PagBank that can be used and sent to other apps.

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

PagBank-modal-icon

Refunded payment

For each refunded payment on PagBank

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

PagBank-icon

Refunded payment

For each refunded payment on PagBank

Trigger

Information from PagBank that can be used and sent to other apps.

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

PagBank-modal-icon

Declined payment

For each declined payment on PagBank

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

PagBank-icon

Declined payment

For each declined payment on PagBank

Trigger

Information from PagBank that can be used and sent to other apps.

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

PagBank-modal-icon

Disputed payment

For each disputed payment on PagBank

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

PagBank-icon

Disputed payment

For each disputed payment on PagBank

Trigger

Information from PagBank that can be used and sent to other apps.

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

PagBank-modal-icon

Created payment

For each created payment on PagBank

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

PagBank-icon

Created payment

For each created payment on PagBank

Trigger

Information from PagBank that can be used and sent to other apps.

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

ZapSign-modal-icon

Signed document

For each signed document on ZapSign

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

ZapSign-icon

Signed document

For each signed document on ZapSign

Trigger

Information from ZapSign that can be used and sent to other apps.

Subscriber name

Email

NO

Telephone number with area code

Contract signed at:

Qualification

Signature image link

Visa image link (heading)

Photo of the document

Photo on the back of the document

Selfie link

Selfie link 2

Shipping mode

Subscription URL

CPF do assinante

CNPJ do assinante

Document creator email

Contract name

Original contract file link

Signed contract file link

Contract created in:

ZapSign-modal-icon

Create document via template

create a document using a template on ZapSign

How it works:

Whenever something happens on the source app

All happening in a single automation! ✨

ZapSign-icon

Create document via template

create a document using a template on ZapSign

Action Premium

Fields in ZapSign that can receive information from other apps.

Send message on WhatsApp automatically

DDI of the signer's phone

Signatory's telephone number (with area code)

Frequency of sending reminders

Didn't find your use case? Send suggestion.

Automate PagBank and ZapSign
with Pluga integrations

Explore automation templates

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.

  • Trigger and source app of the automation

    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.

  • Action and destination app of the automation

    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.

  • Information mapping of the automation

    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.

  • Automation with multiple actions among more than two apps

    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 + ZapSign
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.

Automatic transfer of your contacts' information to other apps

Automating the transfer of your contact base (leads) information to other apps can greatly facilitate tasks that involve managing them.

At Pluga, you can do this with ease and also helps optimize the work of people, avoiding possible human errors.

Card with contact information being sent to other apps

Automate your sales tracking

With the help of Pluga's automations, you can put your business's sales control on autopilot. This way, tasks surrounding inventory, finance, and logistics can be more aligned and optimized, directly impacting your customer's satisfaction.

Data from a new sale being sent to a spreadsheet

Automated financial control

Dealing with finances requires a lot of attention. For this, integrating apps can be a great ally! With Pluga, you can connect your financial management software and payment methods to other apps to automate tasks involving the organization of your finances.

Data from a new charge being sent to an invoicing app

Reduce communication noise - and rework!

If your company uses any type of internal communication tool, it's possible to automate the routine of notifications and alerts within it.

At Pluga, for example, you can connect this software to your project management platform so that every time a task changes status, this is communicated in a channel. In other words, it increases productivity, reduces communication noise, and avoids possible rework.

Automatic notification in the internal communication app

Customized alerts for customers

Often, personalized communication is what will captivate a customer to keep them interested in your brand. But doing this manually is almost impossible. Using Pluga, you can send these notifications automatically without losing personalization.

Automatic message sent to the customer's WhatsApp
PagBank-icon

PagBank

Payment

PagBank (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
ZapSign-icon

ZapSign

Signatures

ZapSign is an electronic signature platform that allows sending, signing, and managing documents digitally. The platform helps save time, paper, and money without losing legal validity.

Integrations with ZapSign Visit ZapSign

Frequently Asked Questions

  • With Pluga, you can easily automate PagBank com ZapSign . Just follow these steps:

    • 1. Log in or sign up (for free) on Pluga and click on “Create automation”;
    • 2. Select the source app and trigger;
    • 3. Select the destination app and action;
    • 4. Make the necessary adjustments, specifying which data will be sent to one app to another.

  • By automating PagBank with ZapSign on Pluga, you can automate various manual tasks that reduce productivity for those who perform them, while also avoiding human errors. The best part is that the process is simple and doesn’t require typing a single line of code.

  • On Pluga, you can make several automations for free with the free plan. Additionally, you have the option to try all the features for 7 days at no cost to create automations between PagBank, ZapSign, and even other apps.

    We also offer three other plans, with prices ranging from $17 to $65 per month, which include premium automations and features, as well as a higher volume of events and automations. For companies with specific needs, we have the Enterprise plan, designed to offer customized solutions beyond the resources available in other plans.

    Check Pluga's pricing page for more details.