Create a one-time charge from a Google Sheets row

This template allows you to automate charge creation in Asaas based on new rows added to a Google Sheets spreadsheet.

Whenever a new row is added to the spreadsheet monitored by Make, the scenario can locate or create the customer in Asaas and automatically generate a charge, including payment split configuration when necessary.

This model is recommended for operations that want to centralize information in spreadsheets and automate financial processes without requiring custom development.

When to use

This template is recommended for:

• automatic charge creation from forms or spreadsheets;
• operations that use Google Sheets as the data source;
• processes that require payment split;
• integrations without custom development;
• automations that use Make as the primary platform.

Dependencies

Before configuring the template, it is necessary to:

• have a Make account;
• have an active Asaas account;
• have a valid API Key;
• have a Google account;
• have access to Google Drive;
• use the template spreadsheet;
• have the required customer and charge information.

📘

Important

The environment selected in Make must match the API Key being used. Sandbox keys only work in the Sandbox environment, and Production keys only work in the Real environment.

Integration flow

The scenario follows the flow below:

New row in Google Sheets
↓
Make identifies the data
↓
Search customer in Asaas
↓
Customer exists?
↓
Yes → Create charge
No → Create customer → Create charge
↓
Charge created with split

Important rules

For charges to be created correctly, consider that:

• the customer must contain valid information;
• charge values must be valid;
• payment splits must follow the account configuration rules;
• duplicate customers are avoided through a previous search using CPF/CNPJ;
• changes to the spreadsheet structure may require adjustments to the scenario;
• charges created in the Real environment have real financial effects.

Important parameters

The spreadsheet used by the scenario must contain the information required to create resources.

Typical fields include:

📘

Important

The spreadsheet structure can be customized according to the needs of the integration.

Template configuration

To start building the flow, download the template spreadsheet available here and upload it to your Google Drive.

If preferred, you can simply create a copy of the spreadsheet.

Step 1

Access the Make template by clicking here.

Step 2

If you do not yet have a Make account, create one at:

https://www.make.com/en/register

After opening the template, click Start Guided Setup.

Step 3

Connect your Google account.

Select Create a Connection, provide a connection name and authenticate with your Google account.

Step 4

Select the spreadsheet stored in Google Drive.

Step 5

Specify the spreadsheet location and complete the Google Sheets module configuration.

Step 6

Configure the connection with Asaas.

In the Environment field, select:

• Real (Production); or
• Sandbox.

Then provide your API Key.

Once this process is completed, the scenario will be ready for use.

Example usage

A common flow is:

Google Forms
↓
Google Sheets
↓
Make
↓
Asaas
↓
Charge created
↓
Slack notification

Additional modules can be added according to specific requirements.

Important behaviors

Execution occurs sequentially.

During processing:

• Make checks whether the customer already exists;
• if the customer does not exist, it will be created;
• only after the customer is found or created will the charge be generated;
• failures in intermediate modules interrupt the flow;
• repeated calls may create new charges if additional validations are not implemented.

🚧

Attention

The scenario does not automatically implement idempotency. It is recommended to use internal references or additional validations to avoid duplicate charges.

Modules used in the integration

Google Sheets (Watch New Rows)

Monitors new rows added to the spreadsheet and starts the scenario execution.

Asaas - List Customers

Checks whether the customer is already registered in Asaas.

Asaas - Create Customer

Creates the customer when it does not yet exist.

Asaas - Create Charge with Split

Creates the charge using the configured split information.

Asaas - Make an API Call

Allows the use of additional Asaas API endpoints.

Documentation:

https://docs.asaas.com/

Router

Controls the scenario flow.

Path 1

Customer already exists:

Google Sheets
↓
Search customer
↓
Create charge

Path 2

Customer does not exist:

Google Sheets
↓
Create customer
↓
Create charge

Operational impacts

When using the Real environment:

• real charges will be created;
• notifications may be sent to customers;
• financial splits will be processed normally;
• incorrect changes may generate unintended charges.

For this reason, it is recommended to validate the scenario in Sandbox before deploying it.

Best practices

• Start by testing in Sandbox.
• Use a dedicated spreadsheet for the scenario.
• Avoid changing the spreadsheet structure without reviewing the modules.
• Monitor Make logs.
• Implement validations to prevent duplicates.
• Use internal references for tracking.
• Periodically review the scenario behavior.

Related content

• Make Templates;
• Make Features and Benefits;
• Create Customers;
• Create Charges;
• Payment Splits;
• Webhooks;
• API Limits.