This page presents the main benefits and features of Make and how they can be used in integration flows with Asaas.

Make's resources allow you to build no-code automations, connect different systems and implement business rules using scenarios, filters and triggers.

When to use these features

Make resources are recommended for integrations that need to:

• automate repetitive processes;
• connect Asaas to external systems;
• create conditional flows without advanced development;
• synchronize data between platforms;
• reduce manual operations;
• create collection, notification or reconciliation processes.

Depending on the operation requirements, different Make features can be combined within the same scenario.

Benefits of Make

No-code automation

Allows complex integrations to be built without requiring advanced development.

This approach facilitates implementation for both technical users and business teams.

It is especially useful for:

• payment automation;
• form integrations;
• spreadsheet synchronization;
• automatic notifications;
• customer and payment creation.

Flexibility

Make offers hundreds of ready-to-use connectors for popular systems.

This allows Asaas to be connected to:

• CRMs;
• databases;
• ERPs;
• productivity applications;
• communication tools;
• form platforms.

Scalability

Scenarios can be used by small operations as well as large organizations with high volumes of data.

Flows can be expanded gradually according to business needs.

Efficiency

Automations reduce manual tasks, minimize operational errors and reduce the time spent on repetitive processes.

Monitoring and logs

Make provides execution history and detailed logs that help identify failures and troubleshoot integrations.

These records are especially important when operating in production environments.

Make Features

Scenarios

Scenarios represent automation flows.

They are composed of modules connected together and executed sequentially.

When to use

Scenarios should be used whenever processes between systems need to be automated.

Example:

Google Forms
↓
Google Sheets
↓
Asaas
↓
Slack

Connectors

Connectors are ready-made integrations between applications.

Make provides connectors for hundreds of systems, including Asaas.

When to use

Connectors are recommended whenever native support exists for the desired operation, reducing the need for manual API requests.

Examples:

• Google Sheets;
• Gmail;
• Slack;
• Telegram;
• HubSpot;
• Notion;
• MySQL.

Actions and triggers

Triggers start scenario execution.

Actions execute operations in connected systems.

When to use

They are used whenever an action should automatically occur in response to an event.

Example:

New spreadsheet row
↓
Create customer in Asaas
↓
Create charge
↓
Send email

Filters and conditions

Allow conditional logic to be added to a scenario.

When to use

Filters are recommended for:

• avoiding duplicate customers;
• separating different flows;
• validating required information;
• defining different paths for specific events.

Example:

Customer already exists?
↓
Yes → Create charge
No → Create customer → Create charge

Webhooks

Allow scenarios to start based on external events.

When to use

They are recommended when integrations need to react in real time.

Examples:

• payment confirmed;
• Pix received;
• overdue charge;
• canceled subscription.

Scheduling

Allows scenarios to run at specific times or periodic intervals.

When to use

Scheduling is recommended for:

• periodic synchronizations;
• automatic reports;
• financial reconciliations;
• data imports.

Important behaviors

When using Make resources, consider that:

• modules are executed according to the order defined in the scenario;
• failures in a module may interrupt execution;
• filters can alter data flow;
• integrations remain subject to Asaas API limits and rules;
• scenarios may generate multiple operations automatically;
• unhandled errors may interrupt entire processes.

Example

A typical flow may follow the model below:

Google Forms receives information
↓
Google Sheets stores the data
↓
Make detects a new row
↓
Search customer in Asaas
↓
Create customer if necessary
↓
Create charge
↓
Send Slack message

Operational impacts

Make scenarios can automatically execute operations within Asaas.

For this reason:

• invalid data may generate incorrect charges;
• poorly configured filters may create duplicate records;
• authentication failures may interrupt the flow;
• changes in external systems may affect the integration;
• high-scale operations require continuous monitoring.

Best practices

• Test scenarios before enabling them in Production.
• Use filters to avoid duplicates.
• Monitor execution logs.
• Configure error handling.
• Protect API Keys used by connections.
• Validate data before creating records in Asaas.
• Internally document critical scenarios.

Related content

To continue your implementation, refer to:

• 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;
• API Limits.