Asaas is a payment processing platform that specializes in managing subscriptions, recurring payments, and financial transactions. It provides tools for businesses to handle billing, payment collection, and financial data management through its API and dashboard interface.

​

1. Add your Asaas access

1. In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Asaas option from the list of connectors.

2. Click Next and you’ll be prompted to add your access.

• Access Token: The token to authenticate against the API service. For detailed instructions, check Asaas docs.
• Start Date: Records created or updated after the start date will be extracted from the source.
• Extract Full Payment Data: Whether to extract full payments data or not. If false, it will extract a summarized version of payments provided by the /lean/payments endpoint.

3. Click Next.

​

2. Select your Asaas streams

1. The next step is letting us know which streams you want to bring. A stream is an entity and you can select the whole entity (meaning all available attributes will come in each table) or only a subset of them.

   Tip: The stream can be found more easily by typing its name.

2. Click Next.

​

3. Configure your Asaas data streams

1. Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a name for each table (which will effectively contain the fetched data) and the type of sync.

• Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
• Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
• Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.

2. Click Next.

​

4. Configure your Asaas data source

1. Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.

2. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).

3. Optionally, you can define some additional settings (if available).

• Configure Delta Log Retention and determine for how log we should store old states of this table as it gets updated. Read more about this resource here.
• Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

​

Check your new source!

1. Click Next to finalize the setup. Once completed, you’ll receive confirmation that your new source is set up!

2. You can view your new source on the Sources page. Now, for you to be able to see it on your Catalog, you have to wait for the pipeline to run. You can now monitor it on the Sources page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your new table will appear in the Catalog section.

If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!