Jetimob
NicoChat now connects directly to the Jetimob real estate system, allowing you to automate all customer service, property acquisition and property management in a practical and intelligent way.
Jetimob is a complete platform for real estate agencies and brokers, bringing together in a single system the sales and rentals CRM, rental management, the real estate website and several features that make your business's day-to-day easier.
With the integration with NicoChat, you can turn this structure into a powerful tool for conversation automation, lead capture and lead qualification.
Note
From now on, you can list active properties, get the details of a property (including photos) and create leads directly in Jetimob's CRM — all straight from the NicoChat flow. Integration base: the official Jetimob API (api.jetimob.com).
How to get the credentials
In the Jetimob panel, under Integrações → Chaves API, there are three keys available. In the NicoApp's internal flow, only two of them are actually used by the available actions:
- Chave Webservice — this is the key used by the two property query actions (Consultar imóveis Ativos and Consultar Detalhes de um Imóvel), which call
GET https://api.jetimob.com/webservice/{'{'}chave_webservice{'}'}/imoveis. It is the read credential for the property catalog. - Chave Privada — this is the key used by the Criar Lead action, which calls
POST https://api.jetimob.com/leads/{'{'}chave_privada{'}'}. It is the credential that authorizes writing to Jetimob's CRM (lead creation), which is why it is treated as more sensitive than the read one.
Attention
Chave Pública: none of the three actions currently available in the NicoApp references this key. It can be kept for other uses within Jetimob itself (website, portals), but it is not required for this NicoApp to work in the current version.
When installing the Jetimob NicoApp, paste the Chave Webservice and the Chave Privada into the configuration fields — that is what authenticates the calls described above.
Limitations
Note
Jetimob does not publish, in its help documentation, a fixed rate limit figure (requests per minute/hour) for the public API. What Jetimob's own help center recommends, when guiding website/portal integrations, is a synchronization frequency: a full catalog load every 30 minutes and a complementary load (new items/changes) every 5 minutes. Treat these intervals as good practice so as not to overload the API, even though they are not a documented technical limit.
- Response size: the Consultar imóveis Ativos action can return many properties at once; internally the NicoApp splits the list into blocks of up to ~19,000 characters to respect the NicoChat/WhatsApp message size limit — this is a limitation of the messaging channel, not of the Jetimob API.
- API errors: if Jetimob rejects a call (invalid key, insufficient permission, non-existent property, etc.), the action follows the block's error path — use it to handle the failure in the flow.
What the NicoApp does
Action
What it does
Main inputs
Outputs
Consultar imóveis Ativos
Lists the active properties of the Jetimob account (
GET /webservice/{'{'}chave{'}'}/imoveis)None (uses only the Chave Webservice)
Summary list per property: id, code, type, neighborhood, city, price, bedrooms, en-suites, bathrooms, total area, listing title. Does not include photos.
Consultar Detalhes de um Imóvel
Fetches the complete data of a specific property by its ID/code
Property ID (code returned by the listing)
Images/photos, listing title, sale price, private area, total area, garages, bathrooms, en-suites, bedrooms, notes
Criar Lead
Sends a lead to Jetimob's CRM (
POST /leads/{'{'}chave_privada{'}'})Required: full_name, email, phone, property_contract (contract type: sale/rental).
About the contact/lead: message, source, subject, tags, tag, responsible, temperature.
About the property: property_code, prospecting_supply_id, country_code.
Tracking/UTMs: utm_id, utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, fbclid, url, url_utm.
Internal assignment: agency_id, team_id, campaign.
Empty, null or zeroed fields are discarded automatically before sending — you only need to fill in what the conversation actually collected.
About the contact/lead: message, source, subject, tags, tag, responsible, temperature.
About the property: property_code, prospecting_supply_id, country_code.
Tracking/UTMs: utm_id, utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, fbclid, url, url_utm.
Internal assignment: agency_id, team_id, campaign.
Empty, null or zeroed fields are discarded automatically before sending — you only need to fill in what the conversation actually collected.
Confirmation that the lead was created in Jetimob's CRM
Recommended flow: lead capture and qualification
- Consultar imóveis Ativos → the flow presents the summary list (without photos) so the contact can choose a property of interest.
- Consultar Detalhes de um Imóvel by the chosen ID → the flow sends the photos, the price, the area and the other characteristics.
- If the contact shows interest, collect Name, Email and Phone and call Criar Lead, filling
property_codewith the property that was queried andsource/subjectwith the origin channel (e.g. WhatsApp/NicoChat) — this way the lead already arrives qualified in Jetimob's CRM.
Tips and notes
- Photos only in Details: the listing (Consultar imóveis Ativos) returns only summary data — name, price, location, numeric characteristics. The photos/images only come in the action Consultar Detalhes de um Imóvel. Always call Details before sending images to the contact.
- Chained ID: the property ID/code returned by Consultar imóveis Ativos feeds both Consultar Detalhes de um Imóvel and the
property_codefield of Criar Lead — store it in a flow variable as soon as the contact chooses the property. - Two credentials, two purposes: the Chave Webservice only reads properties; the Chave Privada only writes leads. Handle the Chave Privada with more care — it is the one that writes data to Jetimob's CRM.
- Criar Lead fields: fill in only what makes sense for the conversation. Blank fields are removed automatically before sending, so there is no need to "force" values for UTMs, gclid/fbclid, agency or team when that information is not available.