Integrate Asaas with n8n

Use the official Asaas node in n8n to execute API operations in visual workflows and connect financial processes to other systems.

To get started, install the node and configure an Asaas credential in the environment that will be used.

When to use

Use the Asaas node when you need to:

• create and manage customers;
• issue and retrieve charges;
• create subscriptions and installments;
• work with Pix;
• retrieve commercial or financial data;
• manage notifications;
• integrate Asaas with ERPs, CRMs, e-commerce stores, and other applications;
• react to Asaas events via Webhooks.

Consider a direct API integration when you need your own control over architecture, concurrency, retries, idempotency, or business rules that do not fit well into visual workflows.

Choose how to integrate

The node uses the official Asaas API. Therefore, the same rules for authentication, validation, limits, and resource behavior still apply.

Available resources

The node organizes operations by resource, such as:

• Customers;
• Payments;
• Subscriptions;
• Installments;
• Pix (Cash-in);
• Notifications;
• Commercial data;
• Financial data;
• Webhooks.

New operations may be added as new versions of the node are released.

Before you begin

Have:

• an Asaas account in Sandbox or Production;
• an API Key from the same environment;
• a compatible n8n installation;
• a compatible Node.js version;
• the official Asaas node installed.

See Installation to check the supported versions, install the @asaasbr/n8n-nodes-asaas package, and configure the Asaas API credential.

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

See how to create and manage API Keys.

How it works

Each workflow combines a trigger, the nodes needed to process the data, and the actions that will be executed in Asaas or other systems.

A charge flow can follow this structure:

%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
    A["Receive the order"] --> B["Prepare the data"]
    B --> C["Find or create the customer"]
    C --> D["Create the charge"]
    D --> E["Store the ID"]
    E --> F["Receive events via Webhook"]
    F --> G["Update the source system"]

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

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

When configuring an Asaas node, choose:

Use the response of each operation to direct the next steps and store the IDs needed to reuse the resources in the workflow.

Track changes with Webhooks

Creating a resource does not necessarily end the financial flow.

To track payments received, due dates, refunds, or other state changes, prefer Webhooks over recurring API queries.

n8n can receive the event and continue the workflow based on the data sent by Asaas.

• Understand how Webhooks work
• See the events for payments

When processing events, keep in mind that Asaas Webhooks use at least once delivery. Store the event id to avoid running the same business rule again.

Before using Production

Validate the complete workflow in Sandbox before switching credentials.

Confirm in particular:

• the selected resource and operation;
• field mapping;
• response handling;
• storage of the returned IDs;
• behavior when a node fails;
• handling of duplicate executions;
• receipt of the necessary Webhooks.

Operations executed in Production can create real customers, charges, subscriptions, and other transactions.

Next steps

• Install and configure the official Asaas node
• Create and manage your API keys
• Test your integration in Sandbox
• Understand how Webhooks work
• See the API limits
• See the API Reference