Pluga
What is Pluga?
Use Pluga to connect Asaas to other tools and automate processes without building your own integration.
Automations can send data to Asaas, such as when creating charges, or use Asaas information in spreadsheets, CRMs, ERPs, and other compatible tools.
How it works
Pluga automations are based on a trigger, which starts the flow, and an action, executed in the destination tool.
%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
A["Event in the source tool"] --> B["Pluga identifies the trigger"]
B --> C["Map the data"]
C --> D["Execute the action"]
D --> E["Update the destination tool"]
classDef inicio fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:3px
classDef validacao fill:#E0F2FE,stroke:#0284C7,color:#0C4A6E,stroke-width:2px
classDef sucesso fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:3px
class A inicio
class B,C,D validacao
class E sucesso
linkStyle default stroke:#94A3B8,stroke-width:2px
Some examples:
| Source | Action |
|---|---|
| New sale in another tool | Create a charge in Asaas |
| Status change of a charge in Asaas | Send the data to another tool |
| Charge received in Asaas | Record the data in a spreadsheet |
| Financial event in Asaas | Notify a team in a compatible tool |
The availability of each trigger, action, and field depends on the template offered by Pluga.
When to use Pluga or the API
| Need | Approach |
|---|---|
| Automate an available flow without writing code | Pluga |
| Connect Asaas to a tool already supported by Pluga | Pluga |
| Create charges from spreadsheets, CRMs, or other systems | Pluga, if a compatible template exists |
| Configure Split without building your own integration | Pluga, when the template offers the feature |
| Implement specific business rules | Asaas API |
| Control queues, logs, retries, and idempotency | Asaas API |
| Process high volume with your own architecture | Asaas API |
| Use features not available in Pluga templates | Asaas API |
Before choosing Pluga, confirm that the connector has the trigger, action, and fields required for your operation.
Before creating an automation
You will need:
- an active Asaas account;
- a Pluga account;
- access to the tool that will be connected;
- permission to use an API key from the Asaas account;
- a definition of the event that will start the automation;
- a definition of the data that will be sent between the tools.
AttentionThe API key allows operations to be performed on the Asaas account.
Store and use this credential securely. Avoid sharing it in open channels, public spreadsheets, messages, or places without access control.
Whenever possible, use an identifiable key for the integration, such as API Key - Pluga.
Data input and output
Asaas can act as the source or the destination of the automation.
| Direction | Example |
|---|---|
| Input into Asaas | Create a charge from a sale, form, spreadsheet, or record from another system |
| Output from Asaas | Send charge information to a spreadsheet, CRM, ERP, or communication tool |
The required fields depend on the chosen automation.
ImportantThe fields available for mapping may vary according to the automation template selected in Pluga.
Before activating the flow, check that all required fields for the desired action have been filled in correctly.
When the automation creates records in Asaas, use an identifier from the source, such as the order number or sale ID, whenever the template allows it. This makes reconciliation easier and helps identify reprocessing.
Choose where to continue
I want to create my first automation
See Introduction - Pluga.
This page presents the prerequisites, automation components, field mapping, and configuration flow in Pluga.
I want to create charges with Split
See Asaas Split on Pluga.
The guide shows how to create charges with split rules between different recipients using a Pluga automation.
I have a question or an automation returned an error
See FAQ - Pluga.
The FAQ provides guidance on:
- API Key;
- Sandbox;
- mapping;
- duplicates;
- execution failures;
- feature availability;
- Split.
ImportantThe availability of tools, triggers, actions, and automation templates is defined by Pluga.
To see the complete, up-to-date list of integrations available for Asaas, visit the Asaas page on Pluga.
Next steps
Updated 20 days ago
