Facilita is a Brazilian CRM for real estate developers, land developers and agencies. The connector uses the Facilita Public API to extract your deals with their full details, custom fields and activity history, your sales funnels with their stages and statuses, your users and teams, your developments with their units, and your tasks and unit reservations. With it you can analyze your sales funnel, your inventory and your team’s performance in your Lakehouse.

Configuring Facilita as a Source

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

1. Add account access

Facilita gives access to your data through its Public API. The Public API is a feature of your Facilita plan: if it is not active in your account, ask Facilita to enable it. An administrator of your Facilita account generates the credentials in the Facilita panel. You need three values:

the instance: the exact name of your Facilita instance;
the API key;
the user token: the token of an administrator user.

The connector reads what the user of the token can see. Use the token of an administrator so that all deals, users and developments are extracted.

The following configurations are available:

Instance: the exact name of your Facilita instance. Required.
API Key: the Public API key generated in Facilita. Required.
User Token: the token of an administrator user, generated together with the API key. Required.
Start Date (advanced): the earliest last-update date of the deals read on the first sync. Later syncs continue from where the previous one stopped. Leave it empty to read the whole history. The other streams are always extracted in full.
Requests Per Minute (advanced): how fast the connector may call Facilita. The default is 45. Facilita allows 50 to 150 requests per minute depending on your plan; when Facilita asks the connector to slow down, it waits and continues automatically.

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.

Deal Details takes one request per deal. On the first sync of an account with many deals it makes the extraction noticeably longer (at the default pace, about 2,700 deals per hour); later syncs only read the deals that changed. Use Start Date to limit how far back the first sync goes.

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: deals and deal details are INCREMENTAL: each sync brings the deals that changed since the previous one. The other streams are FULL_TABLE: each sync replaces the table with what Facilita currently holds. Read more about Sync Types here.

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.

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

Below you’ll find all available data streams from Facilita and their corresponding fields. API reference: Facilita Public API.

Lists and objects are stored as JSON text, and timestamps are converted to UTC. Facilita has no list of customers: customer contact data comes with each deal, and the full customer record is in the customer column of Deal Details.

Deals

Deals (negócios) of your sales funnels, with their stage, value, customer contact and the people responsible. Incremental: each sync reads the deals updated since the previous one.Table: deals · Primary key: id · Sync: Incremental

Field	Type	Description
`id`	Integer	Unique identifier of the deal.
`customer_id`	Integer	Identifier of the customer the deal belongs to.
`cost`	Number	Value of the deal.
`funnel_id`	Integer	Identifier of the sales funnel the deal is in.
`funnel_name`	String	Name of the sales funnel the deal is in.
`funnel_stage_id`	Integer	Identifier of the funnel stage the deal is in.
`stage_name`	String	Name of the funnel stage the deal is in.
`funnel_stage_status_id`	Integer	Identifier of the status, within the stage, the deal is in.
`status_name`	String	Name of the status, within the stage, the deal is in.
`product_id`	Integer	Identifier of the development (empreendimento) of interest.
`product_name`	String	Name of the development (empreendimento) of interest.
`unity_id`	Integer	Identifier of the unit of interest in the development.
`customer_name`	String	Name of the customer.
`customer_email`	String	Email address of the customer.
`customer_phone`	String	Phone number of the customer.
`customer_mobile`	String	Mobile number of the customer.
`owner_id`	Integer	User id of the person responsible for the deal.
`owner_name`	String	Name of the person responsible for the deal.
`owner_email`	String	Email address of the person responsible for the deal.
`broker_id`	Integer	Broker (corretor) id responsible for the deal.
`manager_id`	Integer	Manager (gerente) id responsible for the deal.
`team_id`	Integer	Team (equipe) id responsible for the deal.
`sdr_id`	Integer	Pre-sales (SDR) id responsible for the deal.
`owners`	String (JSON)	Responsibility record of the deal, with owner, broker, manager, team and SDR (JSON object).
`created_at`	Datetime	When the deal was created (UTC).
`updated_at`	Datetime	When the deal was last updated (UTC), used as the incremental replication key.

Deal Details

The full record of each deal read by Deals in the same sync: name, sale date, the custom fields filled on the deal, payment conditions and the activity history. Read with one request per deal, only for the deals that changed. Requires the Deals stream.Table: deal_details · Primary key: id · Sync: Incremental

Field	Type	Description
`id`	Integer	Unique identifier of the deal.
`name`	String	Name of the deal.
`cost`	Number	Value of the deal.
`observations`	String	Free-text notes on the deal.
`customer_id`	Integer	Identifier of the customer the deal belongs to.
`product_id`	Integer	Identifier of the development (empreendimento) of interest.
`unity_id`	Integer	Identifier of the unit of interest in the development.
`funnel_id`	Integer	Identifier of the sales funnel the deal is in, when Facilita sends it.
`funnel_stage_id`	Integer	Identifier of the funnel stage the deal is in.
`stage_name`	String	Name of the funnel stage the deal is in.
`funnel_stage_status_id`	Integer	Identifier of the status, within the stage, the deal is in.
`status_name`	String	Name of the status, within the stage, the deal is in.
`origin_id`	Integer	Identifier of the lead origin of the deal.
`channel_id`	Integer	Identifier of the channel the deal came from.
`queue`	String	Whether the deal came through the lead distribution queue.
`allow_fill`	Boolean	Whether the deal’s form can be filled in.
`simulator_analysis`	Boolean	Whether the deal has a financing simulation under analysis.
`proposal_status_erp`	String	Status of the deal’s proposal in the integrated ERP.
`proposal_provider_erp`	String	ERP the deal’s proposal was sent to.
`proposal_identifier_erp`	String	Identifier of the deal’s proposal in the integrated ERP.
`idle_color_id`	Integer	Identifier of the idleness rule currently matching the deal.
`idle_color_name`	String	Name of the idleness rule currently matching the deal.
`custom_fields`	String (JSON)	Custom fields of the deal with their filled values: group, field id, name, slug, type, value and repeater rows (JSON array).
`payment`	String (JSON)	Payment conditions configured for the deal (JSON array).
`procedure`	String (JSON)	Procedures (stage actions) of the deal (JSON array).
`options`	String (JSON)	Additional options of the deal (JSON).
`data`	String (JSON)	Additional data of the deal (JSON).
`customer`	String (JSON)	Customer of the deal with contact, documents, origin and owners (JSON object).
`owners`	String (JSON)	Responsibility record of the deal, with owner, broker, manager, team and SDR (JSON object).
`product`	String (JSON)	Development (empreendimento) of interest (JSON object).
`unity`	String (JSON)	Unit of interest in the development (JSON object).
`stage`	String (JSON)	Funnel stage the deal is in (JSON object).
`status`	String (JSON)	Status, within the stage, the deal is in (JSON object).
`tasks`	String (JSON)	Tasks linked to the deal (JSON array).
`tags`	String (JSON)	Tags of the deal (JSON array).
`historical`	String (JSON)	Activity history of the deal: stage changes, service records and system events (JSON array).
`reserves`	String (JSON)	Unit reservations made for the deal (JSON array).
`simulation`	String (JSON)	Financing simulations of the deal (JSON array).
`files`	String (JSON)	Files attached to the deal (JSON array).
`created_at`	Datetime	When the deal was created (UTC).
`updated_at`	Datetime	When the deal was last updated (UTC), used as the incremental replication key.
`moved_at`	Datetime	When the deal last moved between stages (UTC).
`saled_at`	Datetime	When the deal was marked as sold (UTC).
`deleted_at`	Datetime	When the deal was deleted (UTC).

Funnels

Sales funnels configured in your account. Extracted in full on every sync.Table: funnels · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the funnel.
`name`	String	Name of the funnel.
`slug`	String	URL-friendly name of the funnel.
`description`	String	Description of the funnel.
`situation`	String	Situation of the funnel (enabled, disabled).
`main`	Boolean	Whether this is the account’s main funnel.
`stages`	String (JSON)	Stages of the funnel, as returned with it (JSON array).
`created_at`	Datetime	When the funnel was created (UTC).
`updated_at`	Datetime	When the funnel was last updated (UTC).
`deleted_at`	Datetime	When the funnel was deleted (UTC).

Funnel Stages

Stages (etapas) of the sales funnel. Join id with deals.funnel_stage_id.Table: funnel_stages · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the stage.
`funnel_id`	Integer	Identifier of the funnel the stage belongs to, when Facilita sends it.
`name`	String	Name shown in the funnel.
`position`	Integer	Display order within its parent.
`allow_fill`	Boolean	Whether deals in it can have their form filled in.
`privacy`	String	Visibility rule (public, private, public_private, private_public).
`idleness`	String (JSON)	Idleness configuration (JSON).
`permissions`	String (JSON)	Users allowed to see it, when restricted (JSON object).
`options`	String (JSON)	Additional options (JSON).
`win_probability`	String	Win probability setting of the stage.

Funnel Stage Statuses

Statuses inside each funnel stage. Join id with deals.funnel_stage_status_id.Table: funnel_stage_statuses · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the status.
`funnel_stage_id`	Integer	Identifier of the stage the status belongs to.
`name`	String	Name shown in the funnel.
`position`	Integer	Display order within its parent.
`allow_fill`	Boolean	Whether deals in it can have their form filled in.
`privacy`	String	Visibility rule (public, private, public_private, private_public).
`idleness`	String (JSON)	Idleness configuration (JSON).
`permissions`	String (JSON)	Users allowed to see it, when restricted (JSON object).
`options`	String (JSON)	Additional options (JSON).

Idle Rules

Idleness rules (ociosidades): how long a deal may stay still in a stage before it is flagged.Table: idle_rules · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the idleness rule.
`name`	String	Name of the idleness rule.
`color`	String	Color shown on deals matching the rule (hex).
`day`	Integer	Days without update that trigger the rule, for day-based rules.
`funnel_stage_id`	Integer	Stage the rule applies to.
`funnel_stage_status_id`	Integer	Status the rule applies to, when restricted to one.
`time_start`	Integer	Start of the idle time range the rule covers, in minutes.
`time_end`	Integer	End of the idle time range the rule covers, in minutes.
`created_at`	Datetime	When the rule was created (UTC).
`updated_at`	Datetime	When the rule was last updated (UTC).

Users

Users of your account, with their access group and their links to teams, managers and brokers.Table: users · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the user.
`first_name`	String	Name of the user.
`email`	String	Email address of the user.
`phone`	String	Phone number of the user.
`cpf`	String	CPF (Brazilian individual taxpayer id) of the user.
`creci`	String	CRECI (real estate broker license) of the user.
`photo`	String	Path of the user’s profile photo.
`group`	String	Access group of the user (admin, manager, broker, supervisor or a custom profile).
`manager_id`	Integer	Manager id of the user, when the user is a manager.
`manager_team_id`	Integer	Team the user manages, when the user is a manager.
`manager_team_name`	String	Name of the team the user manages.
`broker_id`	Integer	Broker id of the user, when the user is a broker.
`broker_manager_id`	Integer	Manager id the broker reports to.
`broker_team_id`	Integer	Team the broker belongs to.
`broker_team_name`	String	Name of the team the broker belongs to.
`supervisor_id`	Integer	Supervisor id of the user, when the user is a supervisor.
`supervisor_team_id`	Integer	Team the user supervises.
`supervisor_team_name`	String	Name of the team the user supervises.

Teams

Sales teams (equipes).Table: teams · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the team.
`name`	String	Name of the team.

Developments

Developments (empreendimentos) registered in your account, with their settings and unit summary.Table: products · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the development.
`name`	String	Name of the development.
`code`	String	Internal code of the development.
`status`	String	Status of the development (active, inactive).
`quantity`	Integer	Number of units of the development.
`address`	String	Street address of the development.
`neighborhood_id`	Integer	Identifier of the neighborhood of the development.
`city`	String	City of the development.
`uf`	String	State (UF) of the development.
`cep`	String	Postal code (CEP) of the development.
`availability_id`	Integer	Identifier of the development’s availability (unit inventory).
`availability_name`	String	Name of the development’s availability.
`availability_type`	String	Layout of the availability (vertical for towers, horizontal for lots).
`availability_summary`	String (JSON)	Number of units per situation, e.g. available and reserved (JSON object).
`cover_id`	Integer	Identifier of the cover image.
`file_id`	Integer	Identifier of the main file.
`infos`	String (JSON)	Development settings: blocks, stages, reservation and simulation rules (JSON object).
`availability`	String (JSON)	Availability of the development with its settings (JSON object).
`custom_fields`	String (JSON)	Custom fields of the development (JSON object).
`files_json`	String (JSON)	Files of the development (JSON).
`google_maps`	String (JSON)	Map location of the development (JSON).
`items`	String (JSON)	Items (amenities) of the development (JSON array).
`cover`	String (JSON)	Cover image of the development (JSON object).
`created_at`	Datetime	When the development was created (UTC).
`updated_at`	Datetime	When the development was last updated (UTC).

Availability Units

Units of each development (apartments, lots, houses), with price and commercial situation. Read for every development that has an availability. Requires the Developments stream.Table: availability_units · Primary key: id · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the unit.
`availability_id`	Integer	Identifier of the availability the unit belongs to.
`product_id`	Integer	Identifier of the development the unit belongs to.
`number`	String	Number of the unit.
`block`	String	Block or tower of the unit.
`floor`	String	Floor of the unit.
`stage`	String	Construction stage of the unit.
`area`	Number	Area of the unit, in square meters.
`cost`	Number	Price of the unit.
`garage`	String	Parking spaces of the unit.
`situation`	String	Commercial situation of the unit (available, pre-reserve, reserved, reserved-permanetly, sale, unavailable).
`status`	String	Status of the unit record (active, inactive).
`observations`	String	Notes on the unit.
`integration_id`	String	Identifier of the unit in an integrated ERP.
`coord_x`	Number	Horizontal position of the unit on the development map.
`coord_y`	Number	Vertical position of the unit on the development map.
`pos_x`	Integer	Column of the unit in the availability grid.
`pos_y`	Integer	Row of the unit in the availability grid.
`infos`	String (JSON)	Additional unit information, such as the typology (JSON object).
`table_data`	String (JSON)	Sales table data of the unit (JSON).
`reserves`	String (JSON)	Reservations of the unit, without the embedded deal (JSON array).
`created_at`	Datetime	When the unit was created (UTC).
`updated_at`	Datetime	When the unit was last updated (UTC).

Tasks

Tasks (calls, e-mails, visits, WhatsApp, chats and notes), one row per task and user linked to it.Table: tasks · Primary key: task_id, user_id, user_mode · Sync: Full table

Field	Type	Description
`task_id`	Integer	Unique identifier of the task.
`user_id`	Integer	User linked to the task.
`user_mode`	String	Role of the user in the task (e.g. owner).
`task_title`	String	Title of the task.
`task_type`	String	Type of the task (mail, call, whatsapp, visit, observation, chat).
`task_status`	String	Status of the task (open, closed).
`task_for_date`	Date	Date the task is scheduled for.
`task_for_hour`	String	Time of day the task is scheduled for (HH:MM:SS).
`task_repeat`	String	Repetition setting of the task.
`task_notes`	String	Notes of the task.
`deal_id`	Integer	Deal the task belongs to.
`customer_id`	Integer	Customer the task belongs to.
`customer_name`	String	Name of the customer the task belongs to.
`task_created_at`	Datetime	When the task was created (UTC).
`task_updated_at`	Datetime	When the task was last updated (UTC).
`user_created_at`	Datetime	When the user was linked to the task (UTC).
`user_updated_at`	Datetime	When the user’s link to the task was last updated (UTC).

Reservations

Unit reservations, with the unit, the customer, the deal and the users involved.Table: reserves · Primary key: id_reserve · Sync: Full table

Field	Type	Description
`id_reserve`	Integer	Unique identifier of the reservation.
`status_reserve`	String	Status of the reservation (e.g. reserved, canceled).
`unity_id`	Integer	Unit reserved.
`unit_number`	String	Number of the unit reserved.
`unit_block`	String	Block or tower of the unit reserved.
`product_id`	Integer	Development the reserved unit belongs to.
`product_name`	String	Name of the development the reserved unit belongs to.
`product_status`	String	Status of the development the reserved unit belongs to.
`deal_id`	Integer	Deal the reservation was made for.
`customer_id`	Integer	Customer the reservation was made for.
`customer_name`	String	Name of the customer.
`customer_email`	String	Email address of the customer.
`customer_phone`	String	Phone number of the customer.
`customer_mobile`	String	Mobile number of the customer.
`customer_origin`	String	Origin of the customer.
`requestered_user_id`	Integer	User who requested the reservation.
`requestered_user_name`	String	Name of the user who requested the reservation.
`managed_user_id`	Integer	User who manages the reservation.
`managed_user_name`	String	Name of the user who manages the reservation.
`reserved_user_id`	Integer	User the unit is reserved for.
`reserved_user_name`	String	Name of the user the unit is reserved for.
`reserved_group_id`	Integer	Access group of the user the unit is reserved for.
`reserved_group`	String	Name of the access group of the user the unit is reserved for.
`expired`	Boolean	Whether the reservation has expired.
`expire_date`	String	Expiration date set for the reservation.
`expire_time`	String	Reservation duration or expiration time (HH:MM:SS).
`order_reservation_expiration_date`	Datetime	When the reservation expires or expired (UTC).
`reason`	String	Reason given when the reservation was canceled.
`observations`	String	Notes on the reservation.
`infos`	String (JSON)	Additional reservation information (JSON).
`unit`	String (JSON)	Unit reserved, with its availability (JSON object).
`reserve_created_at`	Datetime	When the reservation was created (UTC).
`reserve_updated_at`	Datetime	When the reservation was last updated (UTC).
`deleted_at`	Datetime	When the reservation was deleted (UTC).

Custom Fields

Definitions of the custom fields of deals, developments, units, teams and users. The values filled on each deal are in the custom_fields column of Deal Details.Table: custom_fields · Primary key: id, entity_type · Sync: Full table

Field	Type	Description
`id`	Integer	Unique identifier of the custom field.
`entity_type`	String	What the field belongs to: Deal_Main (deals), Product_Main (developments), Availability_Units (units), Team or User.
`name`	String	Label of the custom field.
`slug`	String	Machine name of the custom field.
`type`	String	Input type of the field (text, select, date, email, tel, file, textarea, repeater…).
`position`	Integer	Display order of the field.
`placeholder`	String	Placeholder text of the field.
`required`	Boolean	Whether the field is mandatory.
`default`	String	Default value of the field.
`limit`	Integer	Maximum length of the value.
`validation`	String (JSON)	Validation rule of the field (JSON).
`options`	String (JSON)	Field options, including the choices of select fields (JSON object).
`repeater`	String (JSON)	Sub-fields of a repeater field (JSON array).

Get started

Context

Activate

Workspace

Resources

Facilita as a data source

Configuring Facilita as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

​Configuring Facilita as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

Configuring Facilita as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields