DiscordStatus
Guias / Guides

FAQ - Pluga

Find answers to the most common questions about authentication, Sandbox, field mapping, duplicates, automation execution, and Split in the integration between Asaas and Pluga.

To create an automation, see Introduction - Pluga.

How does an automation work in Pluga?

Automations are based on a trigger and an action.

%%{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["Execute the action"]
    C --> D["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 validacao
    class D sucesso

    linkStyle default stroke:#94A3B8,stroke-width:2px

The availability of tools, triggers, actions, and fields is defined by Pluga and may vary according to the chosen automation template.

🚧

Attention

Before activating an automation in production, run tests with controlled data and validate that the records created in Asaas match the expected behavior.

Do I need to know how to code to use the integration?

No.

Pluga lets you create automations without writing code. Even so, you need to understand which data will be sent between the tools and review:

  • trigger;
  • action;
  • filters;
  • required fields;
  • mapping;
  • connected Asaas account.

For advanced rules, high volume, your own control of queues, retries, logs, or idempotency, consider a direct integration with the Asaas API.

Which accounts do I need?

Usually, you need:

  • an active Asaas account;
  • a Pluga account;
  • access to the tool that will be connected;
  • permission to connect the accounts involved;
  • a valid Asaas API key, when required by the template.

In automations with Split, the recipients also need Asaas accounts able to receive the amounts.

Where do I find the API key?

Create and manage credentials through the Asaas web interface.

See API Keys.

🚧

Attention

The API key allows operations to be performed on the Asaas account.

Store this credential securely and avoid sharing it in open channels, public spreadsheets, or messages without access control.

Can I use the same API key in more than one automation?

Yes.

The same key can be used in more than one automation, as long as it remains valid and belongs to the correct Asaas account.

Use a name that makes the credential easy to identify, for example:

API Key - Pluga

If the key is disabled, expired, or deleted, the automations that depend on it will stop authenticating until the credential is updated.

Is it possible to use Sandbox?

It depends on the automation template and the connection method provided by Pluga.

Always confirm which account and environment are being used before validating the flow.

🚧

Recommendation

If there is no dedicated Sandbox flow in the chosen automation, run controlled tests with low amounts and fictitious data before activating the flow in production.

Which automations can I create?

Availability depends on the connected tool and the templates offered by Pluga.

Flows may include, for example:

  • creating a charge in Asaas from another tool;
  • sending charge information to spreadsheets, CRMs, or ERPs;
  • executing actions based on changes related to charges;
  • creating or updating records in other systems;
  • using Split when the template offers this setting.

Features available in the Asaas API are not necessarily available in all Pluga templates.

Which fields do I need to map to create a charge?

The fields vary according to the automation.

Review in particular:

  • customer name and identification;
  • email and phone;
  • amount;
  • due date;
  • description;
  • payment method;
  • sale or order reference.
📘

Best practice

Whenever possible, use an identifier from the source tool, such as the order number or sale ID.

This data makes reconciliation easier and helps identify whether a charge has already been created.

If a required field is missing, invalid, or in an incompatible format, the action may fail.

Check the Pluga execution history to identify the step where the error occurred and review the mapping before reprocessing the event.

Does changing the mapping modify records that were already created?

No.

Changes to the mapping only affect new executions of the automation.

Charges, customers, or other records already created in Asaas are not updated automatically when the Pluga configuration is changed.

🚧

Important

After changing an automation, run a new test to validate that the data is still being sent correctly.

How do I avoid duplicate charges?

Avoid reprocessing the same event without checking the result of the previous execution.

When the template allows it:

  • use an external reference or order ID;
  • keep a control column or field;
  • record the ID returned by Asaas;
  • review filters and triggers;
  • check the Pluga execution history before resending data.

Example:

ordergenerateChargeasaasChargeIdstatus
1001Yespay_000000000001Created
1002NoPending

Is it possible to use Split through Pluga?

Yes, when the chosen automation template provides this feature.

The configuration may require:

  • the recipient's walletId;
  • fixed amount or percentage;
  • charge data;
  • customer data.

See Asaas Split on Pluga to configure the flow.

Is the Split calculated on the gross value?

No.

The Split percentage is calculated on the net value of the charge (netValue), after the applicable fees.

📘

Example

If a charge has a gross value of R$ 100.00, but the net value after fees is R$ 97.00, a 50% split will be calculated on R$ 97.00.

See Payment Split for the complete rules.

What should I validate in the walletId?

Before activating the automation, confirm that each walletId:

  • belongs to the expected recipient;
  • does not belong to the issuing account itself;
  • is associated with an Asaas account able to participate in the Split.

The net amount that is not directed to other recipients remains in the account that created the charge.

Can I change the Split after the charge has been created?

Asaas allows you to update the Split configuration of existing charges according to the charge's status and rules.

After confirmation, there are specific conditions for allowing the change.

Whether this update can be performed directly through Pluga depends on the actions offered by the template used.

See Update existing payment to check the API rules.

What happens when a charge with Split is refunded?

The transfers related to the Split also take part in the refund flow.

Take this movement into account when reconciling between:

  • issuing account;
  • recipients;
  • Asaas;
  • tool connected through Pluga.

For specific Split rules, see Payment Split.

Is the automation executed immediately?

Do not assume instant execution is guaranteed.

The time depends on:

  • the trigger;
  • the source tool;
  • Pluga;
  • the destination tool.

Validate the actual behavior before creating processes that depend on an immediate response.

How do I identify a failure?

First check the Pluga execution history or log.

Check:

  • whether the automation is active;
  • whether the trigger was fired;
  • whether the filters allowed the execution;
  • whether the credential is still valid;
  • whether the required fields were sent;
  • which error was returned during the action.

Common errors

SituationWhat to check
Charge not createdRequired fields, data sent, and API key
Charge created with incorrect dataMapping between source and destination
Automation not executedTrigger, filters, and automation status
Duplicate chargeReprocessing of the same event
Authentication failureValidity and origin of the API key
Split not appliedTemplate used, Split fields, and walletId
Discrepancy between systemsAutomation history and possible execution delays

Next steps

Updated 2 days ago

Did this page help you?