Make/Integromat

What is Make?


Automate Asaas with Make

Use Make to connect Asaas to spreadsheets, CRMs, forms, databases, and other tools through automation scenarios.

The integration provides native Asaas modules and, when needed, allows you to make authenticated calls directly to the API.

When to use

Consider Make when you need to:

  • create customers, charges, subscriptions, or installments from another system;
  • connect Asaas to spreadsheets, forms, or CRMs;
  • apply filters and routes between different steps of the automation;
  • execute actions in other tools based on financial data;
  • use ready-made templates as a starting point;
  • automate a flow without developing the entire integration orchestration.

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

Before you begin

Have:

  • an active Asaas account;
  • a Make account;
  • an Asaas API Key;
  • access to the other tools that will take part in the scenario;
  • permission to create the necessary connections in Make.

See how to create and manage API Keys.

📘

Important

When configuring the Asaas connection in Make, select the desired environment correctly, such as production or sandbox, and use the API Key corresponding to the selected environment.

How it works

In Make, each automation is called a scenario. The scenario connects modules responsible for receiving, processing, and sending data between tools.

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Receive an event"] --> B["Start the scenario"]
    B --> C["Validate and process the data"]
    C --> D["Execute action in Asaas"]
    D --> E["Send the result"]
    E --> F["Record the execution"]

    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,E validacao
    class F sucesso

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

A scenario can use:

FeatureUse
Asaas modulesExecute operations available directly in the integration
TriggersStart the scenario from a monitored event
FiltersDefine which data can proceed to the next step
RoutesCreate different paths within the same scenario
SchedulingDefines when the scenario will run
Error handlingDefines the flow's behavior when a module fails
Make an API CallAccesses Asaas API resources when needed

What can be automated

The current Asaas modules in Make allow you to work with resources such as:

  • customers;
  • charges;
  • subscriptions;
  • installments;
  • Payment Split;
  • Pix QR Code;
  • invoice issuance settings.

The availability of modules may change as the integration evolves. When a resource is not available as a native module, consider the Make an API Call module.

Choose where to continue

Want to learn about Make's features?

See Advantages and features.

This page presents scenarios, modules, filters, routes, scheduling, and error handling.

Want to start from a ready-made scenario?

See Templates.

Templates provide preconfigured scenarios that can be connected to your accounts and adapted to your operation's flow.

Want to create a charge from Google Sheets?

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

The scenario finds or creates the customer and then creates the charge in Asaas.

Want to create recurring charges?

Follow the guide Create a subscription from a Google Sheets row.

Use this flow when Asaas needs to generate recurring charges according to the subscription created.

Want to create an installment sale?

Follow the guide Create an installment payment from a Google Sheets row.

The scenario can find or create the customer before generating the installment payment.

Have a question or a scenario with an error?

See FAQ - Make/Integromat.

The FAQ provides guidance on environment, API Key, modules, duplicates, and execution failures.

Next steps


Did this page help you?