Skip to main content
Asaas is a payment processing platform focused on billing, recurring subscriptions, and financial operations. This connector extracts customer, payment, transfer, subscription, and financial transaction data from your Asaas account into your Nekt Catalog.

​
Configuring Asaas as a Source

In the Sources tab, click the “Add source” button in the top-right corner, then select Asaas from the list of connectors. Click Next and add your access details.

​
1. Add account access

The following configuration fields are available:
  • Access Token: Token used to authenticate against the Asaas API. For details, check Asaas authentication documentation.
  • Start Date: The earliest record date to sync.
  • Extract Full Payment Data: Controls which payments endpoint is used:
    • Enabled (true): extracts from /payments with the full payments schema.
    • Disabled (false): extracts from /lean/payments with a reduced payments schema.
After configuring access, click Next.

​
2. Select streams

Choose which streams you want to sync. For faster extractions, select only the streams you need.
Tip: You can search streams by name.
Select the streams and click Next.

​
3. Configure data streams

Customize how data should appear in your Catalog, including layer, table naming, and sync type.
  • Layer: Select the destination layer where extracted tables will be created.
  • Table name: Use the suggested name or customize it. You can also apply a prefix to all tables.
  • Sync Type: Choose between INCREMENTAL and FULL_TABLE.
When you’re done, click Next.

​
4. Configure data source

Add a clear description for this source so your team can identify it easily. To define your Trigger, choose how often data should be extracted (for example, daily, weekly, or at fixed times). Optionally, configure additional settings:
  • Delta Log Retention, which controls how long old table states are kept. Learn more here.
  • Additional Full Sync, to periodically complement incremental runs with a complete refresh.
When you are ready, click Next to finalize setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, trigger a run manually from the source actions.
To see data in the Catalog, at least one source run must complete successfully.

​
Streams and Fields

Below are the currently available streams in the Asaas connector and their main fields.
Customer profile and billing identity information from the /customers endpoint.Key Fields:
  • id - Unique customer identifier
  • name - Customer name
  • email - Customer email
  • phone - Landline phone number
  • mobile_phone - Mobile phone number
  • cpf_cnpj - Customer tax document
  • person_type - Person type classification
  • date_created - Customer creation timestamp
  • deleted - Whether the customer is deleted
Address and Registration Fields:
  • address, address_number, complement, province
  • city, city_name, state, country, postal_code
  • municipal_inscription, state_inscription
Operational Fields:
  • external_reference
  • notification_disabled
  • observations
  • foreign_customer
  • company
  • can_delete, cannot_be_deleted_reason
  • can_edit, cannot_edit_reason
Payment records. The stream endpoint and some fields depend on Extract Full Payment Data.Behavior by Configuration:
  • true - Uses /payments (full schema)
  • false - Uses /lean/payments (short schema)
Common Fields (both modes):
  • id - Unique payment identifier
  • date_created
  • value, net_value, original_value, interest_value
  • billing_type, status
  • due_date, original_due_date, payment_date
  • description
  • installment_number
  • external_reference
  • anticipated, anticipable
  • deleted
  • transaction_receipt_url
  • discount, fine, interest
  • postal_service
Short Schema (/lean/payments) Additional Fields:
  • customer_id
  • subscription_id
  • installment_id
  • payment_link_id
  • pix_transaction_id
  • confirmed_date
  • customer_payment_date
  • credit_date
  • duplicated_payment_id
Full Schema (/payments) Additional Fields:
  • customer
  • subscription
  • installment
  • payment_link
  • credit_card
  • pix_transaction
  • pix_qr_code_id
  • confirmed_date
  • client_payment_date
  • invoice_url, invoice_number
  • credit_date, estimated_credit_date
  • last_invoice_viewed_date, last_bank_slip_viewed_date
  • nosso_numero, bank_slip_url
  • split
  • days_after_due_date_to_registration_cancellation
  • chargeback
  • refunds
Recurring subscription contracts from the /subscriptions endpoint.Key Fields:
  • id - Unique subscription identifier
  • customer - Related customer ID
  • payment_link - Related payment link ID
  • billing_type - Billing method
  • cycle - Recurrence cycle
  • status - Subscription status
  • value, gross_value
  • next_due_date, end_date
  • date_created
  • description
  • external_reference
  • max_payments
  • deleted
Financial Detail Fields:
  • discount
  • fine
  • interest
  • split
  • credit_card
  • send_payment_by_postal_service
Financial account movement records from /financialTransactions.Key Fields:
  • id - Unique transaction identifier
  • date - Transaction date (replication key)
  • type - Transaction type
  • value - Transaction amount
  • balance - Account balance after movement
  • description
Reference Fields:
  • payment_id
  • split_id
  • transfer_id
  • anticipation_id
  • bill_id
  • invoice_id
  • payment_dunning_id
  • pix_transaction_id
  • credit_bureau_report_id
Transfer operations and settlement details from the /transfers endpoint.Key Fields:
  • id - Unique transfer identifier
  • type - Transfer type
  • status - Transfer status
  • value, net_value
  • transfer_fee
  • date_created
  • schedule_date, effective_date
  • authorized
  • fail_reason
  • external_reference
  • transaction_receipt_url
  • operation_type
  • description
  • recurring
  • end_to_end_identifier
  • bank_account

​
Implementation Notes

​
Data Freshness and Sync

  • transactions uses date as replication key and is fetched in monthly windows from the configured start_date.
  • Other streams are available for standard source sync configuration and can be run as INCREMENTAL or FULL_TABLE in Nekt.

​
Payments Schema Selection

  • Enable Extract Full Payment Data for the complete payments payload (/payments).
  • Disable it for a lighter and faster extraction using /lean/payments.

​
Skills for agents

Download Asaas skills file

Asaas connector documentation as plain markdown, for use in AI agent contexts.