Connect Pagar.me with Omie CRM
Unlock the superpowers of Pagar.me + Omie CRM and automate your tasks without having to write a single line of code.
Pagar.me and Omie CRM
your way
Check out the available triggers and actions in the automation of apps Pagar.me + Omie CRM
Approved payment
For each approved payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved payment
For each approved payment on Pagar.meTrigger
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]
Declined payment
For each declined payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Declined payment
For each declined payment on Pagar.meTrigger
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
Opportunity with cancelled status
For each cancelled opportunity on Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity with cancelled status
For each cancelled opportunity on Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone
Seller's phone
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact observation
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account Notes
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account State
Account Fax DDD
account phone number
Account's e-mail
Fax to account
Account phone
Account website
Closing forecast
Solution description
Account Vertical
Seller's name
Seller's email
Opportunity with a lost status
For each opportunity lost in the Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity with a lost status
For each opportunity lost in the Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone
Seller's phone
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact notes
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account observation
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account State
Account Fax DDD
DDD Account phone number
Account's e-mail
Fax to account
Account phone
Account website
Expected closing year
Solution description
Account Vertical
Seller's name
Seller's email
Created payment
For each created payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on Pagar.meTrigger
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]
Created subscription
For each created subscription on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each created subscription on Pagar.meTrigger
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]
Opportunity with a won status
For each conquered opportunity in the Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity with a won status
For each conquered opportunity in the Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone (with area code)
Seller's telephone number (with area code)
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact notes
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account observation
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account State
Account Fax DDD
account phone number
Account's e-mail
Fax to account
Account phone
Account website
Expected closing year
Solution description
Account Vertical
Seller's name
Seller's email
Opportunity with a suspended status
For each opportunity suspended in the Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity with a suspended status
For each opportunity suspended in the Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone
Seller's phone
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact notes
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account observation
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account state
Account Fax DDD
account phone number
Account's e-mail
Fax to account
Account phone
Account website
Expected closing year
Solution description
Account Vertical
Seller's name
Seller's email
Refunded payment
For each refunded payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refunded payment
For each refunded payment on Pagar.meTrigger
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]
Opportunity moved to a specific stage
For each moved opportunity to a certain phase in the Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Opportunity moved to a specific stage
For each moved opportunity to a certain phase in the Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone
Seller's phone
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact notes
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account observation
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account state
Account Fax DDD
account phone number
Account's e-mail
Fax to account
Account phone
Account website
Expected closing year
Solution description
Account Vertical
Seller's name
Seller's email
Included opportunity
For each opportunity created in the Omie CRM moduleHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Included opportunity
For each opportunity created in the Omie CRM moduleTrigger
Description of the opportunity
Opportunity email
Observation
Completion date
Lead prospecting date
Negotiation date
Qualification date
Date from proposal
Presentation date
Account code
Contact code
Opportunity code
Origin code
Solution code
Expected closing month
Months of contact
Amount of products
Recurrence amount
Amount of services
Temperature
Ticket
Current phase
Reason for conclusion
Seller's name
Seller's email
Seller's cell phone
Seller's phone
Origin of the opportunity
Contact position
Contact name
Contact last name
Contact's date of birth
Contact notes
Contact email
contact's mobile area code 1
Contact's cell phone 1
contact telephone area code
Contact phone
Contact website
Contact neighborhood
Contact Zip Code
Contact city
Contact complement
Contact address
Contact country
Contact State
Account document (CPF or CNPJ)
Account name
Tags da conta (separadas por vírgula)
Account observation
Account registration date
Account expiration date
Account neighborhood
Account Zip Code
Account city
Account supplement
Account address
Account country
Account State
Account Fax DDD
account phone number
Account's e-mail
Fax to account
Account phone
Account website
Expected closing year
Solution description
Account Vertical
Seller's name
Seller's email
Create customer
create a customer on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Create customer
create a customer on Pagar.meAction
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
Create or update opportunity
create or update an opportunity on Omie CRM moduleHow it works:
Whenever something happens on the source app
1. An deal will be created/updated on Omie CRM
2. A person associated with this deal will be created/updated on Omie CRM
All happening in a single automation! ✨
Create or update opportunity
create or update an opportunity on Omie CRM moduleAction
Distribute new opportunities Required
Select sellers
Seller's email
Atualização de oportunidades
Origin of the opportunity Required
Opportunity Solution Required
Description of the opportunity Required
Account name Required
Account's e-mail Required
Account document
Contact name Required
Contact last name
Contact email Required
Contact position
Contact's date of birth
Contact address
Complementing the contact address
Contact Zip Code
Contact neighborhood
Contact city
Contact state
Contact country
contact's cell phone area code
Contact cell phone
Contact website
Account registration date
Account due date
Account address
Account neighborhood
Account Zip Code
Account city
Account state
Account country
Account telephone area code
Account phone
Account website
Opportunity observation
Task date
Task time
Select to send notification by email
Select task activity
Task description
Ticket: Products amount
Ticket: Services amount
Ticket: Recurring amount
Ticket: Months in contract
Competitors
Involved people: pre-sale
Generate billing
generate a billing on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate billing
generate a billing on Pagar.meAction
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
Create or update contact
create or update a contact on Omie CRM moduleHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create or update contact
create or update a contact on Omie CRM moduleAction
Account name Required
Account's e-mail Required
Account document
Contact name Required
Contact last name
Contact email Required
Contact position
Contact's date of birth
Contact address
Complementing the contact address
Contact Zip Code
Contact neighborhood
Contact city
Contact state
Contact country
Contact's cell phone area code
Contact cell phone
Contact website
Account registration date
Account due date
Account address
Account neighborhood
Account Zip Code
Account city
Account state
Account country
Account telephone area code
Account phone
Account website
Didn't find your use case? Send suggestion.
Automate Pagar.me and Omie CRM with Pluga integrations
Explore automation templates
For each created payment on Pagar.me, create or update an opportunity on Omie's CRM module
EXPLORE For each approved payment on Pagar.me, create or update an opportunity on Omie's CRM module
EXPLORE For each declined payment on Pagar.me, create or update an opportunity on Omie's CRM module
EXPLORE For each refunded payment on Pagar.me, create or update an opportunity on Omie's CRM module
EXPLORE For each created payment on Pagar.me, create or update a contact on Omie's CRM module
EXPLORE For each approved payment on Pagar.me, create or update a contact on Omie's CRM module
EXPLORE For each declined payment on Pagar.me, create or update a contact on Omie's CRM module
EXPLORE For each refunded payment on Pagar.me, create or update a contact on Omie's CRM module
EXPLORE For each subscribed created on Pagar.me, create or update an opportunity on Omie's CRM module
EXPLORE For each subscribed created on Pagar.me, create or update a contact on Omie's CRM module
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 Pagar.me + Omie 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. 
Pagar.me
PaymentPagar.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 Omie CRM
CRMOmie CRM is part of the Omie platform, offering customer relationship management tools, sales automation, lead tracking, and analytics for businesses.
Integrations with Omie CRM Visit Omie CRM