Skip to main content
iRancho is a Brazilian livestock management software for beef and dairy cattle operations. The connector extracts your herd (animals, weighings, lot and pasture movements, deaths, breeding exposures and handling executions), your farm structure and assets (farms, subdivisions, improvements, machinery and refuelings), animal sales and cattle purchase slips, your finances (accounts, transactions, categories, cost centers and cost allocations), and your inputs, stock and feed (products, stock movements, feed formulas, batches and nutrition). With it you can analyze herd performance, costs and results in your Lakehouse.

Configuring iRancho as a Source

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

1. Add account access

iRancho authenticates with an integration token. To generate it:
  1. Log in to iRancho with a user of the account.
  2. Open Configurações (settings).
  3. Under Token de integração, click Gerar token and confirm.
  4. Copy the token.
iRancho warns that the integration token gives other systems access to read and change your account’s data. The Nekt connector only reads data. Deleting the token in iRancho (Excluir token) stops the connector from working until a new token is set.
The following configurations are available:
  • Integration Token: the token generated in iRancho. Required.
  • Start Date: the earliest date from which dated records are synced: animal movements, deaths, breeding exposures, handling executions, stock movements, financial transactions and cost allocations. Required. Every sync re-reads from this date, because iRancho lets you back-date, edit and delete these records, so an earlier date makes each sync longer. Registers such as animals, farms, products and sales are always synced in full.
  • Requests Per Minute: how fast the connector may call iRancho. The default is 120.
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.
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: every iRancho stream is FULL_TABLE: each sync replaces the table with what iRancho 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 iRancho and their corresponding fields. API reference: iRancho API.
Column names follow iRancho’s own field names (in Portuguese). Every table also has a raw_payload column with the whole record exactly as iRancho returned it, so information without a column of its own is still available. Lists and objects are stored as JSON text. Calendar dates are kept as the date shown in iRancho, and timestamps are converted to UTC.
Every animal of the account, active and inactive.Primary key: id_animal
Weighing history of every animal, one row per weighing.Primary key: record_key
Entries and exits of animals in lots, one row per movement. Read in date windows by movement date, from Start Date.Primary key: record_key
Moves of animals between subdivisions (pastures, pens), one row per move. Read in date windows by movement date, from Start Date.Primary key: record_key
Death records, read in date windows by death date, from Start Date.Primary key: record_key
Breeding exposures (natural mating, AI, FTAI, embryo transfer) of every animal whose exposure started on or after Start Date, with their pregnancy diagnosis and calving status.Primary key: id_exposicao_reprodutiva
Handling (manejo) executions registered in iRancho, one row per lane execution, with the animals handled stored as JSON. Read week by week by execution date, from Start Date.Primary key: record_key
Farms of the account.Primary key: id_fazenda
Subdivisions of every farm: pastures, pens and paddocks.Primary key: id_fazenda_subdivisao
Farm improvements such as buildings, fences and corrals.Primary key: id_benfeitoria
Machinery and vehicles, including deactivated ones.Primary key: id_maquinario
Fuel fills of every machine.Primary key: id_maquinario_abastecimento
Contacts: suppliers, buyers, producers and employees.Primary key: id_pessoa
Categories contacts are grouped in.Primary key: id_contato_categoria
Animal sales, all of them on every sync.Primary key: id_venda_animal
Animals sold in each sale, one row per animal, read from each sale’s detail.Primary key: id_venda_animal, id_animal
Cattle purchase slips (borderôs de compra).Primary key: id_bordero_digital
Financial accounts: cash, checking, savings, investment and credit card.Primary key: id_conta
Financial transactions of every account, read month by month from Start Date to 12 months ahead (future installments already exist). One row per installment, recurrence occurrence and account side of a transfer. Forecasts of recurrences that were not recorded yet are not extracted.Primary key: id_conta, id_transacao
Transaction categories.Primary key: id_categoria_transacao
Transaction subcategories.Primary key: id_subcategoria_transacao
Cost centers.Primary key: id_centro_custo
Activities within cost centers.Primary key: id_fin_atividade
Tags (markers) of financial transactions.Primary key: id_tag
Types of cost allocation.Primary key: id_tp_custo
Costs allocated to animals by accrual month, read month by month from Start Date. A recurring allocation appears once per month.Primary key: id_fin_competencia, dt_alocacao_custo
Products and inputs, active and inactive, with their current stock.Primary key: id_produto
Stock locations (warehouses) of each farm.Primary key: id_produto_estoque
Stock movements of every product (entries, exits, internal consumption, losses, sales, transfers), read month by month by movement date, from Start Date.Primary key: id_movimentacao_produto
Feed formulas (rations).Primary key: id_produto_formula
Feed batches mixed from formulas.Primary key: id_batida
Feed supplied to each subdivision per day.Primary key: id_nutricao
Lots (batches) animals are grouped in.Primary key: id
Cattle breeds.Primary key: id
Animal categories (calf, steer, bull, heifer, cow).Primary key: id
Animal sexes.Primary key: id
Types of weighing.Primary key: id
Product categories.Primary key: id
Product subcategories, with their category.Primary key: id, id_produto_categoria
Units of measure.Primary key: id