Create an installment payment from a Google Sheets row
Create an installment payment from Google Sheets with Make
Use this template to create installment payments in Asaas from new rows added to Google Sheets.
The scenario looks up the customer before creation, registers them when needed, and creates the charges linked to the installment payment, including Payment Split when configured.
Before you begin
Have:
- a Make account;
- an active Asaas account;
- a valid API Key;
- a Google account with access to Google Drive;
- the template spreadsheet;
- the data needed to create the customer and the installment payment.
In Make, use:
- Real for Production;
- Sandbox for testing.
Sandbox and Production keys are different.
How it works
%%{init: {"flowchart": {"nodeSpacing": 18,"rankSpacing": 24,"diagramPadding": 4,"padding": 7}}}%%
flowchart TD
A["Add row in Google Sheets"] --> B["Look up customer in Asaas"]
B --> C{"Customer found?"}
C --> Sim(("Yes"))
C --> Nao(("No"))
Sim --> D["Use the existing ID"]
Nao --> E["Create the customer"]
D --> F["Create the installment payment"]
E --> F
F --> G["Generate the installments"]
G --> H["Validate the charges"]
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 C decisao
class B,D,E,F,G validacao
class H sucesso
class Sim respostaSim
class Nao respostaNao
linkStyle default stroke:#94A3B8,stroke-width:2px
linkStyle 2 stroke:#22C55E,stroke-width:4px
linkStyle 3 stroke:#EF4444,stroke-width:4px
When the installment payment is created, Asaas generates the charges corresponding to the installments. Each one has its own ID, due date, amount, and payment cycle.
1. Prepare the spreadsheet
Use the template spreadsheet and make a copy in your Google Drive.
The spreadsheet provides the data used by the scenario, such as:
| Information | Purpose |
|---|---|
| Customer name | Payer registration |
| CPF/CNPJ | Customer identification and lookup |
| Customer data | |
| Total amount | Installment payment amount |
| Number of installments | Number of installments |
| Initial due date | Due date of the first installment |
| Split data | Distribution of amounts |
| Internal reference | Integration control |
Example:
| Name | CPF/CNPJ | Amount | Installments | Due date |
|---|---|---|---|---|
| João Silva | 12345678909 | 1200,00 | 12 | 10/07/2026 |
If you change the spreadsheet structure, also review the fields mapped in the scenario.
2. Open the template
Access:
Create an installment charge with Asaas from a new Google Sheets row
If you do not have an account yet, sign up for Make.
After opening the template, click Start Guided Setup.
3. Connect Google Sheets
In the Google Sheets configuration:
- select Create a Connection;
- enter a name for the connection;
- authenticate your Google account;
- select the spreadsheet stored in Google Drive;
- configure the spreadsheet location.
The Google Sheets (Watch New Rows) module starts the scenario when it detects a new row.
4. Configure the Asaas connection
In the Environment field, select:
- Real for Production; or
- Sandbox for testing.
Then enter the API Key corresponding to the environment.
If you need to create or manage a credential, see API Keys.
AttentionInstallment payments created in Production may generate real notifications and charges to customers.
5. Review the modules
The template uses the following components:
| Module | Function |
|---|---|
| Google Sheets (Watch New Rows) | Starts the scenario when a new row is detected |
| Asaas - List customers | Checks whether the customer is already registered |
| Router | Directs the scenario according to the lookup result |
| Asaas - Create customer | Creates the record when the customer is not found |
| Asaas - Make an API Call | Allows creating the installment payment with the settings used by the template |
The current Asaas app in Make also has the Create an installment charge module. However, the template documented on this page uses Make an API Call for the adjustments required by the flow with Split.
6. Review the installment payment
Before running the scenario, confirm:
- customer;
- total amount;
- number of installments;
- initial due date;
- internal reference;
- Split configuration, when used.
In the Asaas API, an installment charge uses two or more installments. The amount can be defined by the total value of the operation or by the individual installment value.
For the complete rules, see Create an installment charge.
Split in installment payments
Split can be configured in different ways:
| Need | Field |
|---|---|
| Define the transfer for each installment | fixedValue |
| Define a total amount for the entire installment payment | totalFixedValue |
| Apply a percentage to each installment | percentualValue |
In a percentage Split, the calculation is made on the netValue of each installment.
7. Validate the scenario
Before using the Real environment:
- configure the connection in Sandbox;
- add a row with controlled data;
- confirm that the correct customer was found or created;
- validate the amount and number of installments;
- check the first due date;
- review the Split, when used;
- run the scenario;
- confirm the charges generated in Asaas.
Expected result
The row should result in an installment payment linked to the corresponding customer.
Asaas should generate the installment charges according to the configured number and amounts.
Before reprocessing a row, confirm whether the installment payment has already been created. Repeated executions can generate new installment payments.
Track the installments with Webhooks
Each installment has its own charge cycle.
Use the Events for payments to track payments received, due dates, refunds, and other status changes without making recurring API queries.
In events for charges that belong to an installment payment, the installment field identifies the originating installment payment.
When there is a Split, track:
PAYMENT_SPLIT_DONEThe event is fired individually for each settled Split. Since each installment has its own processing, an installment payment can generate different events as the installments are received.
Use additionalInfo.splitId to identify the corresponding Split.
Common errors
| Situation | What to check |
|---|---|
| Authentication failure | Environment and API Key |
| Customer not found | CPF/CNPJ and mapped data |
| Installment payment not created | Amount, number of installments, due date, and execution of the previous modules |
| Duplicate installment payment | Reprocessing of the same row and internal reference |
| Split mismatch | Configured distribution rule |
| Scenario stopped after spreadsheet change | Column structure and module mapping |
Check the Make execution history to identify the module where the failure occurred.
Next steps
Updated 14 days ago
