Skip to main content
CasaSoft is a Brazilian property-management ERP for real-estate agencies, delivered in the cloud as cloudSLIM. It runs the whole rental operation: the property portfolio and its owners, the tenant contracts and the guarantees backing them, the charges billed every month, the municipal property tax, the brokerage deals, and the agency’s own service tickets and filed documents. This connector brings that operation into your catalog.

Configuring CasaSoft as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the CasaSoft option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need a cloudSLIM user and the company code of your account. Ask CasaSoft support for a user dedicated to the integration rather than reusing a person’s login, so the extraction keeps working when people join or leave and its access can be reviewed on its own. The following configurations are available:
  • User: The Identificação used to sign in to cloudSLIM, usually an email address.
  • Password: The password of that user. It is stored encrypted.
  • Company code: The Empresa code of your account, a number such as 1930. It is the same code you type when signing in, and it selects which company’s data is read.
  • Start date: (Advanced) The earliest date to read, for the four streams CasaSoft lets us filter. See the note below on which ones. Leave it empty to load the whole history.
The Start date applies to four streams only: Tickets, Non-conformities, Property Tax (IPTU) and Charges. Everything else is always read in full, for two different reasons. Properties, tenants, owners and their insurance can only be filtered by a status or signature date, so filtering on one would leave out records registered years ago that are still active today. Documents and Brokerage Deals cannot be filtered at all. CasaSoft’s own date filter on those two endpoints returns a server error instead of data (see Known CasaSoft limitations below).Charges is the one stream where the start date really decides how much data you get. CasaSoft serves that ledger one month at a time and refuses an open-ended request, so the connector walks month by month from your start date to the current month. With the field left empty it loads the last 12 months rather than the whole history. Set a start date to go further back.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
CasaSoft exposes the same entity through more than one endpoint, each carrying a different set of columns: Properties, Properties (base view) and Properties (detailed view) describe the same properties, and so do the two Owners streams and the two Surety Bonds streams. Pick the view that carries the columns you need rather than all of them; selecting several means reading the same records more than once.
Selecting a stream your cloudSLIM plan does not include will fail the extraction rather than silently produce an empty table. If a run fails saying CasaSoft refused access to a stream, unselect that stream or ask CasaSoft to release the module for the integration user.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, 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.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • 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: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data, which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data, which is good if, for example, you don’t want to have deleted data in your catalog.
Every CasaSoft stream is a full table sync. None of the CasaSoft endpoints exposes a “last modified” column, so there is nothing an incremental sync could reliably use: a contract edited months after it was signed would never come back. Reading each collection in full on every run is what keeps the tables faithful to what is in cloudSLIM right now.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. 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). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long 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.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Available streams

Fields by stream

Below you’ll find all available data streams from CasaSoft and their corresponding fields:
Every property the agency manages, with the commercial terms agreed with its owner.Endpoint: /imoveis · Primary key: id
The same properties, seen through the endpoint that carries the utility accounts and the current tenant instead of the commercial terms.Endpoint: /imoveis/base · Primary key: id
The same properties, enriched with the building the unit belongs to and the staff assigned to it.Endpoint: /imoveis/detalhes · Primary key: id
Fire insurance policies contracted for the managed properties.Endpoint: /imoveis/seguroincendio · Primary key: id
One row per rental contract: who rents, which property, on what terms.Endpoint: /inquilinos · Primary key: id
The same contracts, plus the surety bond backing them and any payment agreement negotiated with the tenant.Endpoint: /inquilinos/detalhes · Primary key: id
Contracts that were closed, with the reason and who handled it.Endpoint: /inquilinos/contratos/baixados · Primary key: referencia, data_baixa
The same bonds as the Surety Bonds stream, reached through the tenant endpoint.Endpoint: /inquilinos/fiancas/seguro · Primary key: id
Property owners, with their contact details, payout terms and tax settings.Endpoint: /proprietarios · Primary key: id
The same owners, seen through the endpoint that carries nationality and occupation instead of the payout terms.Endpoint: /proprietarios/base · Primary key: id
Surety bonds (seguro fianca) contracted to guarantee rental contracts.Endpoint: /fiancaSeguros · Primary key: id
Municipal property tax records tied to the managed properties. Honours the source’s start date.Endpoint: /iptus · Primary key: id
Brokerage deals closed by the agency, with the commission and how it is collected. Always read in full. CasaSoft’s date filter on this endpoint returns a server error.Endpoint: /intermediacoes · Primary key: id
The agency’s ledger: every charge and credit posted against a contract in a given month. Read one month per request, from the source’s start date to the current month.Endpoint: /lancamentos · Primary key: id
The templates behind repeated charges: what is billed every month, to whom, over which period.Endpoint: /TaxaFixas · Primary key: id
Support tickets opened with the agency. Honours the source’s start date.Endpoint: /tickets · Primary key: id
Non-conformity records (RNCs) from the agency’s quality process. Honours the source’s start date.Endpoint: /rncs · Primary key: id
Index of the documents filed in cloudSLIM.Endpoint: /geds · Primary key: id

Implementation Notes

API Limitations and Error Handling

  • Document files are not extracted: The geds stream carries the index; the base64 payload cloudSLIM ships with it is dropped to prevent huge data loads.
  • Server Overloads: cloudSLIM sometimes reports its own overload as a 500 server error rather than a typical 429 rate limit (e.g., Maximum number of concurrent connections exceeded). The connector recognizes this and backs off for at least 30 seconds before retrying, avoiding competition for scarce connections. The extraction waits and carries on; no data is lost, but the run takes longer. If this happens frequently, ask CasaSoft to raise the connection limit for the integration user, or schedule the source outside office hours.
  • Repeated Server Errors: cloudSLIM answers 500 for both genuine hiccups and for endpoints that build invalid SQL. The connector treats any 5xx error as transient initially. However, if the API returns three consecutive identical error bodies (that are not overload messages), the stream stops immediately. This fast-fails a broken request instead of spending the entire retry budget on the same error. The consecutive failure tally resets upon any successful request.
  • Request timeout: A single page request is given 60 seconds to complete instead of the SDK’s default of 5 minutes. Across a full extraction of a real company, the slowest healthy cloudSLIM response measured 1.4 seconds, so a request that is still pending after five minutes is dead rather than slow. The shorter timeout stops the retry budget (up to 8 attempts) from being spent on dead requests, so a failing stream surfaces in minutes instead of sitting silent for around forty.

Skills for agents

Download CasaSoft skills file

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