Connect Pagar.me with RD Station CRM

Unlock the superpowers of Pagar.me + RD Station CRM and automate your tasks without having to write a single line of code.

Pagar.me and RD Station CRM
your way

Check out the available triggers and actions in the integration of apps Pagar.me + RD Station CRM and build your automation

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

RD Station CRM-icon

Lost opportunity

For each closed deal lost on RD Station CRM

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Deal's ID

Opportunity Name

Responsible user

Email of the responsible user

Sales pipeline

Sales pipeline stage

Contact name

Contact position

Contact email

Contact phone

Contact's birthday

Campaign Name

Source Name

Reason for Loss

Company Name

Company's adress

Company user id number

Company username

Company URL

Organization segments (comma separated)

Seller team ID (separated by comma)

Organization contact emails (comma separated)

Opportunity tasks (separated by commas and line breaks)

Opportunity notes (separated by commas and line breaks)

Last opportunity note

Company ID

Product names (separated by commas)

Product descriptions (comma separated)

Product IDs (separated by commas)

Product quantities (separated by comma)

Product prices (separated by comma)

Product names, descriptions, quantities and prices (separated by commas)

Gross total of products

Full discount

Unique Amount

Recurring Amount

Total amount

Qualification

Opportunity Win

Paused Trading

Creation date

Closing date

Estimated closing date

Created At in the format 'yyyy-mm-dd'

Created At in the format 'dd/mm/yyyy'

Creation date formatted in 'yyyy-mm-dd HH:mm:ss'

Closed At in the format 'yyyy-mm-dd'

Closed At in the format 'dd/mm/yyyy'

Closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Prediction date in the format 'yyyy-mm-dd'

Prediction date in the format 'dd/mm/yyyy'

Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Date and time the opportunity entered the selected Stage

Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'

Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'

RD Station CRM-icon

For every task created

For each task created on RD Station CRM

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Task ID

Task type

Task subject

Task-related opportunity name

Task-related opportunity pipeline stage name

Task-related opportunity creation date

Total opportunity amount related to the task

Task date and time

Task's date and time (BR timezone)

Task date

Task time

Task notes

Task completion date

Name of the company related to the task

Address of the company related to the task

Names of contacts related to the task (separated by commas)

Job titles of contacts related to the task, separated by commas

Emails from contacts related to the task, separated by a comma and vertical bar

Contact emails related to the task, separated by commas

Telephone numbers of contacts related to the task, separated by commas

Names, positions, emails and telephone numbers of contacts related to the task, separated by commas

Name of users related to the task

Email of users related to the task

Task completion status

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]

RD Station CRM-icon

Opportunity marked as sale

For each opportunity marked as sale on RD Station CRM

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Deal's ID

Opportunity Name

Responsible User

Responsible User Email

Sales pipeline

Sales Pipeline Stage

Contact name

Contact Position

Contact Email

Contact Phone

Contact's Birthday

Campaign Name

Source Name

Reason for Loss

Company Name

Company's adress

Company user id number

Company username

Company URL

Company segments (comma separated)

Seller team ID (separated by comma)

Organization contact emails (comma separated)

Opportunity tasks (separated by commas and line breaks)

Opportunity notes (separated by commas and line breaks)

Last opportunity note

Company ID

Product names (separated by comma)

Product descriptions (comma separated)

Product IDs (separated by comma)

Product quantities (separated by comma)

Product prices (separated by comma)

Product names, descriptions, quantities and prices (separated by commas)

Gross total of products

Full discount

Unique Amount

Recurring Amount

Total Amount

Qualification

Negotiation Wins

Paused Trading

Creation date

Closing date

Estimated closing date

Created At in the format 'yyyy-mm-dd'

Created At in the format 'dd/mm/yyyy'

Creation date formatted in 'yyyy-mm-dd HH:mm:ss'

Closed At in the format 'yyyy-mm-dd'

Closed At in the format 'dd/mm/yyyy'

Closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Prediction date in the format 'yyyy-mm-dd'

Prediction date in the format 'dd/mm/yyyy'

Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Date and time the opportunity entered the selected Stage

Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'

Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'

RD Station CRM-icon

Created contact

For each created contact on RD Station CRM

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Contact ID

Contact name

Contact position

Contact's birthday

Contact Linkedin

Contact-related opportunities

Contact emails (separated by comma)

Contact phone numbers (separated by comma)

First contact phone number

Organization of contact

Contact organization website

Address of the contact organization

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]

RD Station CRM-icon

Created opportunity

For each opportunity created on RD Station CRM

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Deal's ID

Opportunity Name

Responsible User

Responsible User Email

Sales pipeline

Sales pipeline stage

Contact name

Contact Position

Contact Email

Contact Phone

Contact's Birthday

Campaign Name

Source Name

Reason for Loss

Company Name

Company's adress

Company user id number

Company username

Company URL

Company segments (comma separated)

Seller team ID (separated by comma)

Organization contact emails (comma separated)

Opportunity tasks (separated by commas and line breaks)

Opportunity notes (separated by commas and line breaks)

Last opportunity note

Company ID

Product names (separated by commas)

Product descriptions (comma separated)

Product IDs (separated by commas)

Product quantities (separated by comma)

Product prices (separated by comma)

Product Names, Descriptions, Quantities and Prices (separated by comma)

Total Gross Products

Total Discount

Unique amount

Recurring amount

Total amount

Qualification

Opportunity Win

Paused Opportunity

Creation date

Closing date

Closing Forecast

Created At in the format 'yyyy-mm-dd'

Created At in the format 'dd/mm/yyyy'

Creation date formatted in 'yyyy-mm-dd HH:mm:ss'

Closed At in the format 'yyyy-mm-dd'

Closed At in the format 'dd/mm/yyyy'

Closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Prediction date in the format 'yyyy-mm-dd'

Prediction date in the format 'dd/mm/yyyy'

Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Date and time the opportunity entered the selected Stage

Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'

Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'

RD Station CRM-icon

Opportunity moved to specific stage in pipeline

For each opportunity moved to a certain stage in the RD Station CRM funnel

Trigger

Information from RD Station CRM that can be used and sent to other apps.

Deal's ID

Opportunity Name

Responsible user name

Email of the responsible user

Sales pipeline

Sales pipeline stage

Contact name

Contact position

Contact Email

Contact Phone

Contact's Birthday

Campaign Name

Source Name

Reason for Loss

Company Name

Company's adress

Company user id number

Company username

Company URL

Company segments (comma separated)

Seller team ID (separated by comma)

Organization contact emails (comma separated)

Opportunity tasks (separated by commas and line breaks)

Opportunity notes (separated by commas and line breaks)

Last opportunity note

Company ID

Product names (separated by comma)

Product descriptions (comma separated)

Product IDs (separated by comma)

Product quantities (separated by commas)

Product prices (separated by comma)

Product names, descriptions, quantities and prices (separated by commas)

Gross total of products

Full discount

Unique amount

Recurring amount

Total amount

Qualification

Negotiation Wins

Paused Trading

Creation date

Closing date

Estimated closing date

Created At in the format 'yyyy-mm-dd'

Created At in the format 'dd/mm/yyyy'

Creation date formatted in 'yyyy-mm-dd HH:mm:ss'

Closed At in the format 'yyyy-mm-dd'

Closed At in the format 'dd/mm/yyyy'

Closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Prediction date in the format 'yyyy-mm-dd'

Prediction date in the format 'dd/mm/yyyy'

Forecast closing date formatted in 'yyyy-mm-dd HH:mm:ss'

Date and time the opportunity entered the selected Stage

Date on which the opportunity entered the selected stage formatted as 'yyyy-mm-dd'

Date on which the opportunity entered the selected stage formatted as 'dd/mm/yyyy'

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: City

Address: State

Address: Country

Address: Zip Code Required

Customer: Area code of the phone Required

Customer: Telephone Required

Customer: International dialing code

RD Station CRM-icon

Create or update contact

create or update a contact on RD Station CRM

Action

Fields in RD Station CRM that can receive information from other apps.

Contact name Required

Update contact based on

Contact Email

Contact Phone

Contact Position

Organization Name

Organization URL

Contact's Birthday

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

RD Station CRM-icon

Create or update company

create or update a company on RD Station CRM

Action

Fields in RD Station CRM that can receive information from other apps.

Company Name Required

Company URL

Company Summary

RD Station CRM-icon

Create or update opportunity

create/update an opportunity on RD Station CRM

Action

Fields in RD Station CRM that can receive information from other apps.

Distribute new deals

Select sellers

Team that will receive opportunities

Email of the Responsible

Atualização de oportunidades

Deal owner update logic

Update criteria for negotiations

Opportunity name Required

Deal forecast date

Opportunity Qualification

Opportunity status

Contact updates

Company/Customer Name

Company website URL

Contact name Required

Contact Phone

Contact Email

Contact Position

Source Name

Name of the Campaign/Marketing Action

Product/Service Name

Product/service description

Product/Service Price

Product/Service Quantity

Product discount type

Product discount

Task Subject

Task date

Task type

Assignment Notes

Opportunity Note

Didn't find your use case? Send suggestion.

Automate Pagar.me and RD Station CRM
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 integration

    What is the integration 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 integration

    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 integration 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 integration

    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 integration between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.

  • Integrations 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.

Integrate Pagar.me + RD Station 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.

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 integrations, 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
RD Station CRM-icon

RD Station CRM

CRM

RD Station CRM is the CRM module of the RD Station platform. It offers tools for customer relationship management, sales automation, analytics, and integration with other digital marketing apps.

Integrations with RD Station CRM Visit RD Station CRM

Frequently Asked Questions

  • With Pluga, you can easily integrate Pagar.me com RD Station CRM . 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 integrating Pagar.me with RD Station CRM 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 integrations for free with the free plan. Additionally, you have the option to try all the features for 7 days at no cost to create integrations between Pagar.me, RD Station CRM, 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.