Advantages/Features

Understand Make's features

Use Make's scenarios, modules, filters, routes, Webhooks, and scheduling to automate flows between Asaas and other tools.

Choose the features according to the behavior needed in the scenario. For ready-made implementations, use the templates and guides in this section.

Main features

Feature	Use when you need to
Scenarios	Organize the entire automation flow
Modules	Execute actions or queries in a tool
Triggers	Start the scenario from an event
Filters	Allow or block the flow from continuing
Routes	Create different paths depending on the data
Webhooks	React to events sent by another system
Scheduling	Run tasks at defined times or intervals
Error handling	Define how the scenario should react to a failure
Execution history	Investigate scenario results and failures

Scenarios

A scenario represents an automation flow made up of connected modules.

Example:

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Receive data from Google Forms"] --> B["Record in Google Sheets"]
    B --> C["Execute action in Asaas"]
    C --> D["Send message on Slack"]

    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

Use scenarios when an operation needs to combine steps between Asaas and other systems.

Modules

Modules are the components executed within a scenario.

The official Asaas app in Make provides modules for operations such as:

creating and retrieving customers;
creating and updating charges;
creating subscriptions;
creating installments;
creating charges with Split;
getting a Pix QR Code;
querying Asaas resources;
making an authenticated call to the API.

When there is a native module for the operation, prefer using it. For resources not covered by the connector, consider the Make an API Call module.

Triggers and actions

The trigger starts the scenario. The action performs an operation after that start.

For example:

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Add row to spreadsheet"] --> B["Create customer in Asaas"]
    B --> C["Create charge"]
    C --> D["Send notification"]

    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 Asaas app in Make also provides the Watch Payments trigger for flows related to changes in charges.

Filters and routes

Use filters when the scenario should only continue if the data meets certain conditions.

Use routes when the process needs to follow different paths.

For example, before creating a charge, the scenario can check whether the customer has already been found:

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Look up the customer"] --> B{"Customer found?"}

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

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

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

    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 B decisao
    class C,D validacao
    class E sucesso
    class Sim respostaSim
    class Nao respostaNao

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

Filters can also be used to validate required data or to prevent a record from moving on to an inappropriate step.

Webhooks

Use Webhooks when the scenario needs to react automatically to events sent by Asaas.

This model is recommended, for example, for updating another system after a relevant change in charges or other resources.

When the goal is to track state changes, prefer Webhooks over scenarios that run periodic API queries.

Understand how Asaas Webhooks work.

See the available events.

Scheduling

Scheduling runs a scenario at defined times or intervals.

Use it for tasks that truly depend on periodic processing, such as:

importing data in batches;
generating reports;
running administrative routines;
processing a source that does not provide events.

Do not use scheduling with recurring queries just to discover changes that can be received via Webhook.

Error handling

Failures in a module can prevent the scenario from continuing.

Configure error handling according to the criticality of the flow and use the execution history to identify:

which module failed;
which data was processed;
which error was returned;
which steps were executed before the failure.

Before reprocessing a scenario that creates records in Asaas, confirm whether the previous operation was completed to avoid duplicates.

API rules still apply

Calls executed by Make are still subject to the Asaas API rules.

This includes:

authentication;
the API Key environment;
required fields;
rules of the resources used;
request and quota limits.

If the scenario makes many calls, see API limits.

Choose the next flow

Next steps

Updated 17 days ago

Did this page help you?