FAQ - Make/Integromat

Find answers to the most common questions about authentication, Sandbox, modules, duplicates, Split, Webhooks, and failures in scenarios that use Asaas in Make.

To configure a complete flow, see the specific templates and guides in this section.

Is Make an official Asaas integration?

Yes.

The Asaas app in Make is maintained by Asaas and provides native modules for different operations, as well as the Make an API Call module for resources that need to be accessed directly through the API.

Does Make replace your own API integration?

It depends on the operation.

Make covers automation and orchestration scenarios between systems. Your own integration may be more suitable when you need:

• specific business rules;
• your own idempotency control;
• custom asynchronous processing;
• your own architecture and observability;
• more granular control over a high volume of requests.

How do I configure Production and Sandbox?

The connection must use the API Key corresponding to the selected environment.

In the templates in this section:

• Real corresponds to Production;
• Sandbox corresponds to the test environment.

Sandbox and Production accounts, data, and credentials are independent.

See how to create and manage API Keys.

Understand the Sandbox environment.

Which operations can I automate?

The Asaas app in Make has modules for operations related to customers, charges, subscriptions, installments, and other resources.

When there is no suitable module for the operation, use Make an API Call and follow the rules of the corresponding endpoint.

To learn about the features and when to use them, see Advantages and features.

Can I create charges from Google Sheets?

Yes.

The template in this section uses a new Google Sheets row as the start of the scenario and looks up the customer before creating the charge.

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Add row in Google Sheets"] --> B["Look up customer in Asaas"]
    B --> C{"Customer found?"}

    C --> Sim(("Yes"))
    C --> Nao(("No"))

    Sim --> D["Use the existing ID"]
    Nao --> E["Create the customer"]

    D --> F["Create the charge"]
    E --> F

    F --> G["Record the result"]

    classDef inicio fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:3px
    classDef decisao fill:#FEF3C7,stroke:#D97706,color:#78350F,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
    classDef respostaSim fill:#22C55E,stroke:#15803D,color:#FFFFFF,stroke-width:3px
    classDef respostaNao fill:#EF4444,stroke:#B91C1C,color:#FFFFFF,stroke-width:3px

    class A inicio
    class C decisao
    class B,D,E,F validacao
    class G sucesso
    class Sim respostaSim
    class Nao respostaNao

    linkStyle default stroke:#94A3B8,stroke-width:2px
    linkStyle 2 stroke:#22C55E,stroke-width:4px
    linkStyle 3 stroke:#EF4444,stroke-width:4px

Follow Create a one-time charge from a Google Sheets row.

Can I create subscriptions with Make?

Yes.

Asaas has a native module for creating subscriptions. The template in this section also allows you to create a subscription from Google Sheets and uses an API call for the adjustments required by the documented flow with Split.

After creation, Asaas generates new charges according to the configured recurrence.

Follow Create a subscription from a Google Sheets row.

Can I create installment payments with Make?

Yes.

Asaas has a native module for creating installment charges. The template in this section allows you to start the flow from Google Sheets and uses an API call for the adjustments required by the documented scenario with Split.

Follow Create an installment payment from a Google Sheets row.

Can I use Payment Split?

Yes.

Split can be used in charges, subscriptions, and installments, as long as the configuration respects the feature's rules.

How to configure the data depends on the module or template used. In some scenarios, it may be necessary to use Make an API Call.

See the Payment Split rules.

How do I avoid duplicate customers?

The API allows you to create more than one record for the same customer.

When the operation requires reusing the existing record:

• look up the customer before creating it;
• use the CPF/CNPJ or another identifier suitable for the scenario;
• store the ID returned by Asaas;
• reuse this ID in subsequent operations.

The prior lookup reduces duplicates but does not represent automatic idempotency.

How do I avoid duplicate charges, subscriptions, or installment payments?

Make does not guarantee automatic idempotency for scenarios.

Before reprocessing a row or event:

• record the ID returned by Asaas;
• use an operation reference;
• confirm whether the resource has already been created;
• configure filters when necessary;
• check the history of the failed execution.

What happens if a module fails?

A failure can interrupt the scenario after previous modules have already executed their actions.

For example:

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Detect new row"] --> B["Create the customer"]
    B --> C["Fail to create the charge"]
    C --> D["Interrupt the scenario"]

    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

In this case, the customer may have been created even though the charge was not completed.

Before running it again:

1. check the Make history;
2. identify the last completed module;
3. confirm which resources already exist in Asaas;
4. fix the cause of the failure;
5. only then re-run the flow.

Are Asaas notifications still sent?

Yes.

If the created operation is configured to use Asaas notifications, they continue to follow the rules of the corresponding account, customer, and charge.

Can I use Asaas Webhooks with Make?

Yes.

Use Webhooks when a scenario needs to react to changes that occur in Asaas, instead of running recurring queries to find out whether a state has changed.

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Event occurs in Asaas"] --> B["Send the Webhook"]
    B --> C["Receive the event in Make"]
    C --> D["Process the data"]
    D --> E["Execute the next action"]

    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

Asaas Webhooks use at least once delivery. If the scenario executes an action that cannot be repeated, use the event id to prevent duplicate processing.

To track charges, use the PAYMENT_* events. For the subscription life cycle, use the SUBSCRIPTION_* events.

• Understand how Webhooks work
• See the events for payments
• See the events for subscriptions

Is Make subject to the API limits?

Yes.

Calls made by Make modules are still subject to the Asaas API limits, rules, and validations.

When a limit is exceeded, the API may return HTTP 429 Too Many Requests.

See the API limits.

Common errors

What should I validate before using Production?

Next steps

• Go back to the Make overview
• Learn about Make's features
• Choose a template
• Understand how Webhooks work
• See the Payment Split rules