Make/Integromat

What is Make?

Make, formerly known as Integromat, is an integration platform as a service (iPaaS) that allows applications and services to be connected through automated workflows without requiring advanced development.

With Make, it is possible to create automations called scenarios, which move data between systems, process information and execute actions automatically.

The integration between Make and Asaas allows Asaas resources to be connected to spreadsheets, CRMs, databases, messaging systems, forms, ERPs and productivity platforms.

When to use

The Make integration is recommended when your operation needs to automate processes involving Asaas without building a custom integration.

Common scenarios include:

creating charges from spreadsheet rows;
automatically registering customers in Asaas;
creating subscriptions or installment payments;
sending notifications to Slack, Telegram or email;
synchronizing information between Asaas and CRMs;
connecting forms, spreadsheets and databases to Asaas resources;
creating internal reconciliation, monitoring or collection flows.

This integration is especially useful for operations that want to quickly validate processes, automate repetitive tasks or connect Asaas to tools already used by the business.

How the integration works

In Make, every automation is built through a scenario.

A scenario usually contains:

an initial trigger, such as a new spreadsheet row;
intermediate modules for querying, creating or updating data;
filters and conditional routes;
actions executed in Asaas or other connected systems.

A typical flow follows the structure below:

An event occurs in an external system
↓
Make starts the scenario
↓
Data is processed and validated
↓
Make executes an action in Asaas
↓
Result is sent to another system
↓
Scenario execution is recorded

Requirements

Before using Make with Asaas, you must have:

an active Asaas account;
an active Make account;
an Asaas API Key;
access to the systems connected to the scenario;
permissions to create connections in Make;
a clear definition of the data that will be sent to Asaas.

📘
Important
When configuring the Asaas connection in Make, correctly select the desired environment, such as Production or Sandbox, and use the API Key corresponding to the selected environment.

Resources that can be automated

Make can automate several operations involving Asaas, such as:

customer creation;
customer lookup;
charge creation;
split charge creation;
subscription creation;
installment payment creation;
notifications;
integrations with spreadsheets, forms, CRMs and databases.

Depending on the resource used, specific modules or direct API calls may be required.

Important parameters and settings

During scenario creation, some fields directly affect integration behavior:

Configuration	Purpose
API Key	Credential used to connect Make to Asaas
Environment	Defines whether the integration uses Production or Sandbox
Asaas Module	Defines which operation will be executed
Required fields	Required information for customers, charges, subscriptions or installment payments
Filters and Routes	Determine which path the scenario will follow
Scheduling	Defines when the scenario runs
Error handling	Defines how failures are treated

Important behaviors

When using Make with Asaas, consider that:

scenarios execute modules according to their configured order;
failures in a module may interrupt the scenario;
missing required data may prevent customer, charge or subscription creation;
incorrectly configured routes may send information to the wrong path;
requests executed by Make remain subject to Asaas API limits and rules;
integrations should avoid duplicate customers and charges;
Make execution logs should be monitored to identify failures.

Example flow

A common scenario creates charges in Asaas from a new row added to Google Sheets:

New row added to Google Sheets
↓
Make identifies row data
↓
Make checks whether the customer already exists
↓
If customer exists, existing ID is used
↓
If customer does not exist, a new customer is created
↓
Make creates the charge in Asaas
↓
Make logs or notifies the operation result

This flow can be adapted for forms, CRMs, databases and other connected systems.

Best practices

Use the API Key corresponding to the correct environment.
Test scenarios in Sandbox before using Production.
Validate required fields before creating records.
Use filters to avoid duplicate customers and charges.
Monitor execution logs.
Configure error handling for temporary failures.
Avoid exposing API Keys in public fields or logs.
Periodically review active scenarios.

Common errors

Invalid API Key

This may occur when the key is incorrect or does not match the selected environment.

Duplicate customer

This may occur when customers are created without checking whether they already exist.

Missing required fields

This may occur when forms or spreadsheets do not contain all required information.

Interrupted scenario

This may occur when a module fails and error handling is not configured.

Incorrect environment

This may occur when a Production API Key is used in Sandbox or vice versa.

Operational impacts

Scenarios configured in Make may automatically execute operations in Asaas.

Therefore, changes in spreadsheets, forms, CRMs or databases may create customers, charges, subscriptions or other financial operations.

Before activating a scenario in Production, it is recommended to validate:

data sources;
required fields;
duplicate prevention rules;
configured environment;
error handling behavior;
execution logs;
permissions of connected accounts.

Most used integrations

Through Make, Asaas can be integrated with more than 500 systems.

Some frequently used integrations include:

To view the complete list of systems available in Make, click here.

Next steps

To continue your implementation, refer to the following pages:

Features and Benefits;
Templates;
Create a one-time charge from a Google Sheets row;
Create a subscription from a Google Sheets row;
Create an installment payment from a Google Sheets row;
API Authentication;
Webhooks.