Connect Pagar.me with Olist ERP (Tiny ERP)

Unlock the superpowers of Pagar.me + Olist ERP (Tiny ERP) and automate your tasks without having to write a single line of code.

Pagar.me and Olist ERP (Tiny ERP)
your way

Check out the available triggers and actions in the automation of apps Pagar.me + Olist ERP (Tiny ERP)

Pagar.me-icon

Approved payment

For each approved payment on Pagar.me

Trigger

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

transaction id

tid of the acquirer

not as a buyer

status

código

status reason [only pagar.me 1.0]

flag code

buyer's response

Message from the acquirer

creation date

creation date (formatted - DD/MM/YYYY)

creation date (formatted - H:M:S)

creation date (formatted - DD/MM/YYYY - H:M:S)

update date

update date (formatted - DD/MM/YYYY)

update date (formatted - H:M:S)

update date (formatted - DD/MM/YYYY - H:M:S)

total amount (in cents)

total amount

total amount (formatted in R$)

amount captured (in cents)

captured amount

amount captured (formatted in R$)

Total amount of items (in cents)

cost (in cents) [only pagar.me 1.0]

cost [only pagar.me 1.0]

cost (formatted in R$) [only pagar.me 1.0]

refunded amount (in cents) [only pagar.me 1.0]

amount refunded [only pagar.me 1.0]

refunded amount (formatted in R$) [only pagar.me 1.0]

payment method

installments

ticket: link

bank slip: barcode

bank slip: expiration date

Subscription ID [only pagar.me 1.0]

customer telephone number (ddi)

customer phone number (ddd)

customer telephone number (number)

customer: document

customer: email

customer: name

address street

address: number

full address

address neighborhood

address: city

address: state

address: Zip Code

billing address: street

billing address: number

billing address: add-on

billing address: neighborhood

billing address: city

billing address: state

billing address: Zip Code

delivery address: street [only pagar.me 1.0]

delivery address: number [only pagar.me 1.0]

delivery address: complement [only pagar.me 1.0]

delivery address: neighborhood [only pagar.me 1.0]

delivery address: city [only pagar.me 1.0]

delivery address: state [only pagar.me 1.0]

delivery address: Zip Code [only pagar.me 1.0]

Shipping fee (in cents) [only pagar.me 1.0]

Shipping fee [only pagar.me 1.0]

Item SKU/ID

item title

unit price of items

quantity of items

title, price and quantity of items

Acquirer fee (in cents) [only pagar.me 1.0]

Acquirer fee [only pagar.me 1.0]

Acquirer fee (formatted in R$) [only pagar.me 1.0]

Advance fee (in cents) [only pagar.me 1.0]

Advance fee [only pagar.me 1.0]

Advance fee (formatted in R$) [only pagar.me 1.0]

payment link: id [only pagar.me 1.0]

payment link: name [only pagar.me 1.0]

card flag

List of IDs of sales intermediaries [only pagar.me 1.0]

List of amounts per sales intermediary [only pagar.me 1.0]

Pix: QR Code

Pix: Expiration Date

Pix: Name of the payer [only pagar.me 1.0]

Pix: Payer document [only pagar.me 1.0]

Pix: Payer document type [only pagar.me 1.0]

Pix: Name of the payer’s Bank [only pagar.me 1.0]

Pix: ISPB code of the payer's bank [only pagar.me 1.0]

Pix: Payer's bank branch [only pagar.me 1.0]

Pix: Payer's bank account number [only pagar.me 1.0]

Pagar.me-icon

Declined payment

For each declined payment on Pagar.me

Trigger

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

transaction id [only pagar.me 1.0]

tid of the acquirer

not as a buyer

status

código

status reason [only pagar.me 1.0]

flag code

buyer's response

Message from the acquirer

creation date

creation date (formatted - DD/MM/YYYY)

creation date (formatted - H:M:S)

creation date (formatted - DD/MM/YYYY - H:M:S)

update date

update date (formatted - DD/MM/YYYY)

update date (formatted - H:M:S)

update date (formatted - DD/MM/YYYY - H:M:S)

total amount (in cents)

total amount

total amount (formatted in R$)

amount captured (in cents)

captured amount

amount captured (formatted in R$)

Total amount of items (in cents)

cost (in cents) [only pagar.me 1.0]

cost [only pagar.me 1.0]

cost (formatted in R$) [only pagar.me 1.0]

refunded amount (in cents) [only pagar.me 1.0]

amount refunded [only pagar.me 1.0]

refunded amount (formatted in R$) [only pagar.me 1.0]

payment method

installments

bank slip: link

bank slip: barcode

bank slip: expiration date

Subscription ID [only pagar.me 1.0]

customer telephone number (ddi)

customer phone number (ddd)

customer telephone number (number)

customer: document

customer: email

customer: name

address street

address: number

full address

address neighborhood

address: city

address: state

address: Zip Code

billing address: street

billing address: number

billing address: add-on

billing address: neighborhood

billing address: city

billing address: state

billing address: Zip Code

delivery address: street [only pagar.me 1.0]

delivery address: number [only pagar.me 1.0]

delivery address: complement [only pagar.me 1.0]

delivery address: neighborhood [only pagar.me 1.0]

delivery address: city [only pagar.me 1.0]

delivery address: state [only pagar.me 1.0]

delivery address: Zip Code [only pagar.me 1.0]

Shipping fee (in cents) [only pagar.me 1.0]

Shipping fee [only pagar.me 1.0]

Item SKU/ID

item title

unit price of items

quantity of items

title, price and quantity of items

Purchaser fee (in cents) [only pagar.me 1.0]

Purchaser fee [only pagar.me 1.0]

Purchaser fee (formatted in R$) [only pagar.me 1.0]

Advance fee (in cents) [only pagar.me 1.0]

Advance fee [only pagar.me 1.0]

Advance fee (formatted in R$) [only pagar.me 1.0]

payment link: id [only pagar.me 1.0]

payment link: name [only pagar.me 1.0]

card flag

Olist ERP (Tiny ERP)-icon

Unpaid account will expire

For each new due account pay on Olist ERP (Tiny ERP)

Trigger

Information from Olist ERP (Tiny ERP) that can be used and sent to other apps.

Identification number

Date of issue

Due date

Amount

Balance

Document number

Supplier code

Provider's name

Supplier person type

Supplier's CPF or CNPJ

Supplier state registration

Supplier ID

Supplier address

Supplier address number

Supplier address supplement

Supplier neighborhood

Supplier Zip Code

Supplier city

Supplier UF

Supplier country

Supplier phone number

Supplier email

Historic

Category

Situation

Type of occurrence

Due date

Number of plots

Olist ERP (Tiny ERP)-icon

Added receivable account

For each added accounts receivable on Olist ERP (Tiny ERP)

Trigger

Information from Olist ERP (Tiny ERP) that can be used and sent to other apps.

Account receivable: ID

Account receivable: Issue date

Account receivable: Due date

Account receivable: Amount

Account receivable: Document number

Account receivable: Document series

Account receivable: Bank number

Account receivable: Competence

Customer: Code

Customer: Name

Customer: Type of person (in the format: 'F', 'J', or 'E')

Customer: Type of person in full (in the format: Individual, Legal Entity, Foreigner)

Customer: CPF or CNPJ

Customer: State registration

Customer: RG

Customer: Address

Customer: Address number

Customer: Address complement

Customer: Neighborhood

Customer: Zip Code

Customer: City

Customer: UF

Customer: Country

Customer: Telephone

Customer: Email

Account receivable: History

Account receivable: Category

Account receivable: Payment method

Account receivable: Payment method

Account receivable: Status

Account receivable: Occurrence (in the format: 'U', 'P', 'W', 'M', 'T', 'S', 'A')

Account receivable: Occurrence in words (in the format: 'Single', 'Instalments', 'Weekly', 'Monthly', 'Quarterly', 'Six-monthly', 'Annual')

Account receivable: Due date

Account receivable: Number of installments

Account receivable: Day of the week when the weekly installment is due

Account receivable: Account receivable balance

Pagar.me-icon

Created payment

For each created payment on Pagar.me

Trigger

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

transaction id

tid of the acquirer

not as a buyer

status

status reason [only pagar.me 1.0]

flag code

buyer's response

Message from the acquirer

creation date

creation date (formatted - DD/MM/YYYY)

creation date (formatted - H:M:S)

creation date (formatted - DD/MM/YYYY - H:M:S)

update date

update date (formatted - DD/MM/YYYY)

update date (formatted - H:M:S)

update date (formatted - DD/MM/YYYY - H:M:S)

total amount (in cents)

total amount

total amount (formatted in R$)

amount captured (in cents)

captured amount

amount captured (formatted in R$)

Total amount of items (in cents)

cost (in cents) [only pagar.me 1.0]

cost [only pagar.me 1.0]

cost (formatted in R$) [only pagar.me 1.0]

refunded amount (in cents) [only pagar.me 1.0]

amount refunded [only pagar.me 1.0]

refunded amount (formatted in R$) [only pagar.me 1.0]

payment method

installments

bank slip: link

bank slip: barcode

bank slip: expiration date

Subscription ID [only pagar.me 1.0]

customer telephone number (ddi)

customer phone number (ddd)

customer telephone number (number)

customer: document

customer: email

customer: name

address street

address: number

full address

address neighborhood

address: city

address: state

address: Zip Code

billing address: street

billing address: number

billing address: add-on

billing address: neighborhood

billing address: city

billing address: state

billing address: Zip Code

delivery address: street [only pagar.me 1.0]

delivery address: number [only pagar.me 1.0]

delivery address: complement [only pagar.me 1.0]

delivery address: neighborhood [only pagar.me 1.0]

delivery address: city [only pagar.me 1.0]

delivery address: state [only pagar.me 1.0]

delivery address: Zip Code [only pagar.me 1.0]

Shipping fee (in cents) [only pagar.me 1.0]

Shipping fee [only pagar.me 1.0]

Item SKU/ID

item title

unit price of items

quantity of items

title, price and quantity of items

Purchaser fee (in cents) [only pagar.me 1.0]

Purchaser fee [only pagar.me 1.0]

Purchaser fee (formatted in R$) [only pagar.me 1.0]

Advance fee (in cents) [only pagar.me 1.0]

Advance fee [only pagar.me 1.0]

Advance fee (formatted in R$) [only pagar.me 1.0]

payment link: id [only pagar.me 1.0]

payment link: name [only pagar.me 1.0]

card flag

Pix: QR Code

Pix: Expiration Date

Pix: Name of the payer [only pagar.me 1.0]

Pix: Payer document [only pagar.me 1.0]

Pix: Payer document type [only pagar.me 1.0]

Pix: Name of the payer’s Bank [only pagar.me 1.0]

Pix: ISPB code of the payer's bank [only pagar.me 1.0]

Pix: Payer's bank branch [only pagar.me 1.0]

Pix: Payer's bank account number [only pagar.me 1.0]

Pagar.me-icon

Created subscription

For each created subscription on Pagar.me

Trigger

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

Transaction: ID

Subscription: Creation date

Subscription: Creation date (format - DD/MM/YYYY)

Subscription: Creation hour (format - H:M:S)

Subscription: Creation date (format - DD/MM/YYYY - H:M:S)

Subscription: Update date

Subscription: Update date (format - DD/MM/YYYY)

Subscription: Update date (format - H:M:S)

Subscription: Update date (format - DD/MM/YYYY - H:M:S)

Subscribed: Total price (in cents)

Subscribed: Total price

Subscribed: Total price (format - R$)

Client: Telephone (DDI)

Client: Telephone (DDD)

Client: Telephone

Client: Document

Client: Email

Client: Name

Address: Street

Address: Number

Address: Complement

Address: Neighborhood

Address: City

Address: State

Address: CEP

Subscribed: Current period start

Subscribed: Current period start (format - DD/MM/YYYY)

Subscribed: Current period start (format - H:M:S)

Subscribed: Current period start (format - DD/MM/YYYY - H:M:S)

Subscribed: Current period end

Subscribed: Current period end (format - DD/MM/YYYY)

Subscribed: Current period end (format - H:M:S)

Subscribed: Current period end (format - DD/MM/YYYY - H:M:S)

Transaction: Payment method

Transaction: Card holder name

Transaction: Card brand

Subscribed: Metadata origin

Subscribed: Metadata internal name

Subscribed: Items description resume, separated by comma [only pagar.me 2.0]

Subscribed: Quantity items resume, separated by comma [only pagar.me 2.0]

Subscribed: Items price resume, separated by comma [only pagar.Me 2.0]

Subscribed: Description, price and quantity resume, separated by comma [only pagar.me 2.0]

Subscribed: Next billing dates [only pagar.me 2.0]

Subscribed: Next billing dates (format - DD/MM/YYYY) [only pagar.me 2.0]

Subscribed: Next billing dates (format - H:M:S) [only pagar.me 2.0]

Subscribed: Next billing dates (format - DD/MM/YYYY - H:M:S) [only pagar.Me 2.0]

Olist ERP (Tiny ERP)-icon

Included new customer or supplier

When a new customer or supplier is included on Olist ERP (Tiny ERP)

Trigger

Information from Olist ERP (Tiny ERP) that can be used and sent to other apps.

Identification number

code

Name or company name

Kind of person

Date of birth

Sex

Fancy name

CPF or CNPJ

RG

State registration

Municipal registration

Landline

Cell phone

Profession

Address

Address number

Address complement

Neighborhood

POCKET

City

UF

Contact email

Situation

Creation date

Observations about contact

Pagar.me-icon

Refunded payment

For each refunded payment on Pagar.me

Trigger

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

transaction id

tid of the acquirer

not as a buyer

status

status reason [only pagar.me 1.0]

flag code

buyer's response

Message from the acquirer

creation date

creation date (formatted - DD/MM/YYYY)

creation date (formatted - H:M:S)

creation date (formatted - DD/MM/YYYY - H:M:S)

update date

update date (formatted - DD/MM/YYYY)

update date (formatted - H:M:S)

update date (formatted - DD/MM/YYYY - H:M:S)

total amount (in cents)

total amount

total amount (formatted in R$)

amount captured (in cents)

captured amount

amount captured (formatted in R$)

Total amount of items (in cents)

cost (in cents) [only pagar.me 1.0]

cost [only pagar.me 1.0]

cost (formatted in R$) [only pagar.me 1.0]

refunded amount (in cents) [only pagar.me 1.0]

amount refunded [only pagar.me 1.0]

refunded amount (formatted in R$) [only pagar.me 1.0]

payment method

installments

bank slip: link

bank slip: barcode

bank slip: expiration date

Subscription ID [only pagar.me 1.0]

customer telephone number (ddi)

customer phone number (ddd)

customer telephone number (number)

customer: document

customer: email

customer: name

address street

address: number

full address

address neighborhood

address: city

address: state

address: Zip Code

billing address: street

billing address: number

billing address: add-on

billing address: neighborhood

billing address: city

billing address: state

billing address: Zip Code

delivery address: street [only pagar.me 1.0]

delivery address: number [only pagar.me 1.0]

delivery address: complement [only pagar.me 1.0]

delivery address: neighborhood [only pagar.me 1.0]

delivery address: city [only pagar.me 1.0]

delivery address: state [only pagar.me 1.0]

delivery address: Zip Code [only pagar.me 1.0]

Shipping fee (in cents) [only pagar.me 1.0]

Shipping fee [only pagar.me 1.0]

Item SKU/ID

item title

unit price of items

quantity of items

title, price and quantity of items

Purchaser fee (in cents) [only pagar.me 1.0]

Purchaser fee [only pagar.me 1.0]

Purchaser fee (formatted in R$) [only pagar.me 1.0]

Advance fee (in cents) [only pagar.me 1.0]

Advance fee [only pagar.me 1.0]

Advance fee (formatted in R$) [only pagar.me 1.0]

payment link: id [only pagar.me 1.0]

payment link: name [only pagar.me 1.0]

card flag

Pix: QR Code

Pix: Expiration Date

Pix: Name of the payer [only pagar.me 1.0]

Pix: Payer document [only pagar.me 1.0]

Pix: Payer document type [only pagar.me 1.0]

Pix: Name of the payer’s Bank [only pagar.me 1.0]

Pix: ISPB code of the payer's bank [only pagar.me 1.0]

Pix: Payer's bank branch [only pagar.me 1.0]

Pix: Payer's bank account number [only pagar.me 1.0]

Olist ERP (Tiny ERP)-icon

Included new order

For each new order added on Olist ERP (Tiny ERP)

Trigger

Information from Olist ERP (Tiny ERP) that can be used and sent to other apps.

Identification number

Order number

Request Date

Forecast date

Description of payment condition

Form of payment

Payment method

Number of installments

Carrier name

Responsible for shipping

Shipping method

Cost of shipping

Discount

Total amount of products

Purchase order number

Seller identification number

Observation

Internal observation

Order tracking code

Order tracking URL

Identifier of the invoice referenced by the sale

Name of the deposit linked by the sale

Order status

Total amount

Total amount (comma separated)

ecommerce order number

Order markers (Description)

Order installments

Order item list

Order seller name

Name of the e-commerce

Order number in e-commerce

Description of the sales channel linked to e-commerce

Customer code

Customer name

Customer's trade name

Customer person type

Customer CPF or CNPJ

Customer state registration

Customer ID

Customer address

Customer address number

Customer address complement

Customer neighborhood

Customer Zip Code

Customer city

Customer UF

Customer phone

Customer email

Name of delivery recipient

Type of delivery person

CPF or CNPJ for delivery

Delivery address

Delivery address number

Delivery address complement

Delivery neighborhood

Delivery Zip Code

Delivery city

UF delivery

Delivery phone

Summary of items (Description - Quantity). Separated by semicolons.

Summary of items (Description - Quantity). Separated by semicolons.

Resumo dos itens (Descrição - Quantidade). Separado por vírgula

Resumo dos itens (Descrição - SKU - Quantidade). Separado por vírgula

Description of items separated by commas

Quantity of items separated by comma

Unit amount of items separated by commas

Comma-separated item SKUs

Olist ERP (Tiny ERP)-icon

Achieved status

When an order reaches a certain status on Olist ERP (Tiny ERP)

Trigger

Information from Olist ERP (Tiny ERP) that can be used and sent to other apps.

Identification number

Sales order number in Tiny

Date of sale

Expected delivery date

Payment terms

Method of receipt

Payment method

Number of installments

Carrier name

Responsible for shipping

Shipping method

Cost of shipping

Discount

Total amount of products

Sale details: Order number

Seller identification number

Observation

Internal observation

Order tracking code

Order tracking URL

Identifier of the invoice referenced by the sale

Name of the deposit linked to the sale

Order status

Total amount

Total amount (comma separated)

ecommerce order number

Order markers (Description)

Order installments

Order item list

Seller's name

Nome do ecommerce

Código do pedido do ecommerce

Descrição do canal de venda do ecommerce

Customer code

Customer name

Customer's trade name

Customer person type

Customer CPF/CNPJ

Customer state registration

Customer ID

Customer address

Customer address number

Customer address complement

Customer address neighborhood

Customer address Zip Code

City of customer address

UF of the customer's address

Customer phone

Customer email

Name of delivery recipient

Type of delivery person

Delivery CPF/CNPJ

Delivery address

Delivery address number

Delivery address complement

Delivery address neighborhood

Delivery address Zip Code

City of delivery address

State of delivery address

Delivery phone

Summary of items (Description - Quantity). Separated by semicolon

Summary of items (Description - Quantity - Amount). Separated by comma

Summary of items (Description - Quantity). Separated by comma

Resumo dos itens (Descrição - SKU - Quantidade). Separado por ponto e vírgula

Description of items separated by commas

Quantity of items separated by comma

Unit amount of items separated by commas

Comma-separated item SKUs

Pagar.me-icon

Create customer

create a customer on Pagar.me

Action

Fields in Pagar.me that can receive information from other apps.

Customer: Name Required

Customer: Email Required

Customer: CPF/CNPJ

Address: Street Required

Address: Number Required

Address: Additional information

Address:neighborhood Required

Address: City

Address: State

Address: Country

Address: Zip Code Required

Customer: Area code of the phone Required

Customer: Telephone Required

Customer: International dialing code

Olist ERP (Tiny ERP)-icon

Include accounts receivable

include an account receivable on Olist ERP (Tiny ERP)

Action

Fields in Olist ERP (Tiny ERP) that can receive information from other apps.

Due date Required

Amount Required

Mark bill as received

Date of issue

Document number

Customer name Required

Customer person type

Customer CPF or CNPJ

Customer state registration

Customer ID

Customer address

Customer address number

Customer address complement

Customer neighborhood

Customer Zip Code

Customer city

Customer UF

Customer country

Customer phone

Customer email

Historic

Category selection mode

Category

Category

Method of receipt

Type of occurrence

Due date

Number of installments

Olist ERP (Tiny ERP)-icon

Create sales order (single item)

create a sales order on Olist ERP (Tiny ERP)

Action Premium

Fields in Olist ERP (Tiny ERP) that can receive information from other apps.

Order date

Order predicted date

Customer name Required

Item Description Required

Item code

Item unit Required

Item Quantity Required

Item unit price Required

Item type Required

Item origin Required

Installment period

Número de parcelas

Gap between installments

Forma de recebimento das parcelas do pedido.

Customer person type

Nome fantasia do cliente

Customer CPF or CNPJ

Código do cliente

Customer state registration

Customer address

Customer address number

Customer address complement

Customer neighborhood

Customer Zip Code

Customer city

Customer UF

Customer country

Customer phone

Customer email

Order markers

How to receive the order

Payment method

Lista de preços do pedido

Carrier name

Shipping on account

Cost of shipping

Shipping method

Shipping method

Discount amount

Other expenses

Purchase order number

Order observation

Internal order observation

Order status

Seller selection method

Order seller

Order seller

Order identification number in e-commerce

Platform sending the order

Name of the intermediary

CNPJ of the transaction intermediary

CNPJ of the intermediary's payment institution

Name of the nature of operation

Pagar.me-icon

Generate billing

generate a billing on Pagar.me

Action

Fields in Pagar.me that can receive information from other apps.

Payment method Required

Payment deadline Required

Amount Required

Customer email Required

Customer name

Customer Type Required

CPF/CNPJ (Individual Person Registry/National Legal Entity Registry) Required

Description

Notify customer of billing

Olist ERP (Tiny ERP)-icon

Include accounts payable

include an account payable on Olist ERP (Tiny ERP)

Action

Fields in Olist ERP (Tiny ERP) that can receive information from other apps.

Maturity Required

Amount Required

Date of issue

Document number

Provider's name Required

Supplier person type

Supplier's CPF or CNPJ

Código do fornecedor

Supplier state registration

Supplier ID

Supplier address

Supplier address number

Supplier address supplement

Supplier neighborhood

Supplier Zip Code

Supplier city

Supplier UF

Supplier country

Supplier phone number

Supplier email

Historic

Category selection mode

Category

Category

Type of occurrence

Due date

Number of installments

Olist ERP (Tiny ERP)-icon

Include or update customer/vendor

include or update a customer/supplier on Olist ERP (Tiny ERP)

Action

Fields in Olist ERP (Tiny ERP) that can receive information from other apps.

Type Required

Name or business name of the Contact Required

Situation Required

Fantasy name

Kind of person

Nome fantasia do cliente

CPF or CNPJ

Código do contato

Legal Entity: state registration

RG

Legal Entity: municipal registration

Type of deal

Address

Address number

Address complement

Neighborhood

Zip Code

City

UF

Foreign: Country

Billing address

Billing address number

Address billing add-on

Billing district

Billing Zip Code

Billing city

Billing UF

Contact phone

Fax

Contact cell phone

Contact email

Email to send nfe

Web site

Legal Entity: Tax regime code

Individual and Foreigner in Brazil: Marital status

Individual and Foreigner in Brazil: Profession

Individual and Foreigner in Brazil: Sex

Individual and Foreigner in Brazil: Date of birth

Individual and Foreigner in Brazil: Birthplace

Individual and Foreigner in Brazil: Father’s name

Individual and Foreigner in Brazil: Father's CPF

Individual and Foreigner in Brazil: Mother’s name

Individual and Foreigner in Brazil: Mother's CPF

Credit limit

General observations

Olist ERP (Tiny ERP)-icon

Add NFS-e

add an NFS-e on Olist ERP (Tiny ERP)

Action

Fields in Olist ERP (Tiny ERP) that can receive information from other apps.

customer name Required

customer cpf/cnpj

customer address

customer address number

add the customer's address

neighborhood of the customer's address

customer address Zip Code

city of customer address

uf of customer address

customer phone

customer email

service description Required

service amount Required

Deduct ISS (ISS Withheld) Required

Didn't find your use case? Send suggestion.

Automate Pagar.me and Olist ERP (Tiny ERP)
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 Pagar.me + Olist ERP (Tiny ERP)
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
Pagar.me-icon

Pagar.me

Payment

Pagar.me is an online payment platform offering solutions for businesses to receive payments via credit card, payslip, bank transfer, and other payment methods.

Integrations with Pagar.me Visit Pagar.me
Olist ERP (Tiny ERP)-icon

Olist ERP (Tiny ERP)

ERP

Olist ERP is an ideal management system for micro or small businesses due to its modularity and intuitiveness. It enables automation of sales, invoice issuance, and efficient management of products, listings, and inventory.

Integrations with Olist ERP (Tiny ERP) Visit Olist ERP (Tiny ERP)

Frequently Asked Questions

  • With Pluga, you can easily automate Pagar.me com Olist ERP (Tiny ERP) . 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 Pagar.me with Olist ERP (Tiny ERP) 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 Pagar.me, Olist ERP (Tiny ERP), and even other apps.

    We also offer three other plans, with prices ranging from $17 to $71 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.