🛠 How to set up your farm by chatting with UPí

With the UPí connector — upCampo's artificial intelligence — turned on in Claude or ChatGPT, the farm's records can be created by chatting. You write "I have fields T1 with 120 ha and T2 with 85 ha", UPí shows what it is going to save, you confirm and the two fields go into upCampo. It works for season, crop, variety, field and field map, planting, activity type, subtype, rain gauge, storage location, product class, product, supplier, equipment type, equipment, employee and opening inventory.

The same records can also be created through UPí on WhatsApp (see How to use UPí on WhatsApp), with the same phrases as in this article — including sending the spreadsheet, the PDF or the field map in the chat.

It is the same record used by the web portal screens: what goes in through the chat shows on the screen right away, and what was registered on the screen UPí can see. It serves two moments:

• Onboarding — upCampo creates the company, the farm and the first user; the rest of the base the farm builds itself through the chat, in the order UPí indicates.
• Day-to-day maintenance — adding a field, fixing a product name, deactivating an activity type that is no longer used.

The path, in four steps

1. Connect UPí with permission to post, using a user who has permission on the registration screens.
2. Ask what is missing: UPí checks the farm's progress and tells you the next step.
3. Dictate each stage, in order, and confirm what it shows before saving.
4. Fix and deactivate later, in the same chat, whenever you need to.

1️⃣ Before you start

2️⃣ How to start: ask what is missing

3️⃣ What to say at each stage

At every stage UPí shows the list of what it will save and asks for your confirmation first. You can dictate several items at once. The phrases below are examples — write it your own way.

Season

💬 "Register the 2026/27 season, from September 1, 2026 to August 31, 2027."

• Name, start and end are required. The period is how UPí knows which is the current season when you do not name one.
• The season applies to all of the company's farms.

Crop

💬 "My crops are soybean, corn and cotton."

• UPí brings the crop from the upCampo base, which already comes with the growth stages ready.
• A crop that does not exist in the base — a specific fruit crop, for example — is created with just the name and the type, Annual or Perennial.
• The crop applies to all of the company's farms.

Variety

💬 "In soybean I will plant M 8644 IPRO and Olimpo. The M 8644 cycle is 120 days."

• Each variety belongs to one crop. The same name can exist in different crops.
• Cycle in days and technology (IPRO, RR…) are optional.

Field

💬 "Fields: T1 with 120 ha, T2 with 85.5 ha and T3 with 60 ha, all in the Sede sector."

• Name and area, in hectares, are required — the area can be left out when the field comes with the map (see below). The sector is optional; a new sector is created on its own.
• A field name repeated on the farm is rejected.

Field map

The field map also goes in through the chat: by attaching the KML file or typing the points. On WhatsApp, send the KML or KMZ file or the shapefile in a .zip — see just below.

💬 "This is the farm's KML, save the map of each field." — with the file attached to the chat.
💬 "The map of T1 is: -12.500 -55.700; -12.500 -55.6954; -12.491 -55.6954; -12.491 -55.700."
💬 "Register field T5 with this map." — without stating the area: the map's area is used.

• The map can come with the field registration or later. Sending a new map replaces the previous one.
• UPí calculates the area from the map. A field with no area takes the map's area. A field that already has an area keeps it; if the registered area and the map's area differ by more than 5%, UPí saves the map and warns you, showing both — then it is up to you: if the map's area is right, ask it to fix the area.
• If the field does not yet have its point marked on the web portal map, the center of the field map becomes that point.
• The map shows in the web portal and in the apps, just like one imported through the Field screen.
• In Claude and ChatGPT you can use KML or the points as text. The shapefile goes through WhatsApp or through the web portal's Field screen.

The whole farm map through WhatsApp. Send the KML, KMZ or shapefile (a .zip with the .shp, .dbf and .prj) and say 💬 "this is the farm map, register the fields". UPí shows a preview before saving:

• how many fields are new and how many already exist and will only have the map and area replaced, the total area and the sectors;
• what was left out and why — pieces smaller than 0.1 ha and names repeated in the file;
• if the file does not include the field names, each one shows as "Field 1, 2…" with the area and a map link, and UPí asks for the names before saving.

With your "yes", UPí saves field by field. A shapefile in UTM or SAD69 is converted automatically; in another projection (polyconic, Albers), export it again in latitude/longitude or UTM.

The map is rejected when:

• it has fewer than 3 distinct points;
• the points do not form an area — check the order they were written in;
• latitude and longitude look swapped. Each point is latitude then longitude; a KML lists longitude first, but UPí converts that automatically.

Season planting

💬 "In the 2026/27 season T1 and T2 get soybean M 8644, and T3 gets corn."

• One planting per field in each season. If no area is given, the field's area is used.
• The planting date is optional — it can go in later, when you plant.
• One variety per field. A field with more than one variety in the same season is registered on the Season Planting screen, in the web portal.
• To change a planting's season, field or crop, deactivate the planting and register it again.

Activity type

💬 "The types I use are: planting, harvest, burndown, fungicide and topdressing. The harvest must require the machine."

• UPí starts from the upCampo base templates — soil preparation, planting, fertilization, application, harvest… —, picks the one that matches each name and saves them all at once. The template brings the behavior ready (whether it is planting, harvest, application); the name is the one you gave.
• You can ask for the work order execution to require equipment, an employee or times.
• Without an activity type you cannot post a work order — that is why it comes right after planting.

Subtype

The subtype is the Short Identification (Subtype) field of the work order: the subdivision of the activity type, such as the 1st and 2nd fungicide application. In the web portal menu, the screen is Short ID (Subtype).

💬 "For the Fungicide type I use the subtypes 1st application, 2nd application and 3rd application; for Burndown, pre-planting and post-harvest."

• Each subtype can apply to one or more activity types.
• The stage (from 1 - Before planting to 8 - Other) and the For requisition flag are optional.
• A subtype already used in a work order cannot be renamed, because the order stores the name: register a new one. It also cannot be deactivated while it is in a work order, schedule or treatment.

Rain gauge

💬 "I have the Sede rain gauge, which covers T1 and T2, and the Fundo rain gauge, which covers T3."

• Each rain gauge carries the list of fields it covers.
• A field covered by two rain gauges is accepted, but UPí warns you: when posting rainfall on that field, it will ask which rain gauge.

Storage location

💬 "The locations are Crop Protection Warehouse and Fertilizer Shed."

• Silos and fuel stations are registered on the Storage Location screen, in the web portal.

Product class

💬 "Classes: Herbicide, Fungicide, Insecticide, Fertilizer and Seed."

• UPí makes suggestions based on the classes in the upCampo base, but the class is yours.
• The class type is one of these: Fuel, Part, Lubricants, Input, Service or Other. Crop protection products, fertilizer and seed are Input.

Product

💬 "Products: Roundup Original in liters, Herbicide class; urea in kilos, Fertilizer class."

• Name and unit are required. The unit can be given by its code (L, KG, UN, sc, TON…) or by its name (liter, kilo).
• UPí checks the upCampo base to suggest the unit, class and spelling of the name — but the product is yours: it saves what you confirm.
• A repeated product code is rejected.

Supplier

💬 "Supplier Agro Insumos Ltda, CNPJ 12.345.678/0001-95, from Sorriso-MT."

• The supplier is saved as an Entity.
• The CPF or CNPJ (Brazilian individual and company tax IDs) can be dictated with or without dots; it is saved without punctuation. The new CNPJ, with letters, is accepted.
• A document repeated in the company is rejected.

Equipment type

💬 "The machine types I have are tractor, harvester, sprayer and truck."

• It is the record of the web portal's Fleet Classification screen.
• UPí suggests the names from the upCampo base, but the type is yours.
• The abbreviation is optional. With it — "TR" for Tractor, for example —, the code of the equipment of that type becomes TR0001, TR0002…

Equipment

💬 "John Deere 6110J tractor, plate ABC1D23, year 2019, diesel, 200-liter tank, hour meter currently at 4,520 hours."
💬 "Implements: Jumil 12-row planter and leveling disk harrow."

• It is the record of the web portal's Fleet / Farm Assets screen.
• A machine is created with an hour meter — or an odometer, if it is a road vehicle — and ready for fueling and work orders.
• An implement is created with no meter and outside fueling.
• Today's hour meter or odometer reading is only informational: the first fueling is what updates it.
• A plate repeated on the farm is rejected. Two pieces of equipment with the same name need different plates or codes.

Employee

💬 "Employees: João Silva, tractor driver; Pedro Souza, harvester operator; Maria Lima, sprayer operator."

• It is the record of the web portal's Employee/Operator screen.
• The name is required; role, hourly rate, phone and email are optional.
• A name repeated on the farm is rejected — the name is how UPí finds the employee later, when posting the execution of an order or a fueling.
• The team, which groups employees, is still put together in the web portal.

Opening inventory

💬 "Opening inventory in the Crop Protection Warehouse: 200 liters of Roundup at R$ 32.50 per liter."

• It goes in as a Standalone inbound in Movement, with the description "Opening inventory".
• Only with the product and location already registered, and with each product's unit cost — that is what forms the inventory's average cost.
• Lot and expiration date do not go in through the chat yet: a product controlled by lot has its opening inventory posted in the web portal.

4️⃣ Fixing and deactivating later

5️⃣ When UPí refuses

6️⃣ What is still done in the web portal

The chat asks for the essentials of each record. Whatever is left out is done on the screen:

• a field with more than one variety in the same season — Season Planting;
• silos and fuel stations — Storage Location;
• inventory of products with lot and expiration date — Movement;
• teams (putting the team together with the employees) — Team —, and pests, which do not go in through the chat yet;
• field map by shapefile (.shp) in Claude and ChatGPT — on WhatsApp it goes in, or through the Field screen;
• any field the chat does not ask for — the nozzle and flow rate setup of the activity type, and so on.

UPí also works on WhatsApp and answers about the whole farm — see what else it does at meet UPí.

❓ Frequently asked questions