Skip to main content
Lixlog is a Brazilian freight and logistics platform. It quotes shipping across multiple carriers, books the collection at your warehouse and tracks the delivery through to the addressee. This connector brings that whole operation into your catalog: the shipments and their delivery status, the carrier tracking events, the collection requests, and the full history of freight quotes with every carrier option that was offered.

​
Configuring Lixlog as a Source

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

​
1. Add account access

You’ll need the API token of your Lixlog account. Generate it in the Lixlog panel; it starts with flx_. The following configurations are available:
  • API token: The API token of your Lixlog account. It is stored encrypted and is sent to Lixlog as a bearer token.
  • Initial sync date: (Advanced) The starting point for orders, pickups and freight quote history. Products, warehouses and carriers are always read in full. When left empty, orders and pickups load their entire history and freight quotes load the last 90 days.
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.
Lixlog only exposes tracking events one shipment at a time, so the Order Trackings stream makes one request per order. On accounts with a large order history the extraction takes considerably longer with this stream selected. Leave it unselected if you do not need the carrier’s event-by-event history.
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.
Orders and pickups change over their lifetime (an order created today is delivered days later), so INCREMENTAL keeps them up to date by their last update timestamp. Freight quotes are never edited after the fact, so their history only ever grows. Products, warehouses and carriers are small reference tables and are read in full on every run.
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 Lixlog and their corresponding fields:
The central table of the connector: one row per shipment, carrying the carrier that moves it, the warehouse it leaves from, the addressee it goes to, the invoice attached to it and the timestamps of each step of the delivery.It also carries the freight rate chosen for the shipment, flattened into the selected_rate_* columns. That block is what makes delivery SLA measurable: it holds the delivery time the carrier committed to and the date it promised, for essentially every order, where the only other estimate in this connector is the one some carriers volunteer in the tracking feed.
Tracking events reported by the carrier for each order. One row per event.
Collection requests placed with the carriers, one row per request.
Every freight quote Lixlog answered, with all the carrier options it returned. This is the freight-pricing history: what a shipment could have cost, next to what it did cost in the Orders stream.
Products registered in Lixlog, with the measurements freight is priced from. This is the table to check when a shipment is quoted heavier or bulkier than expected.
Shipping origins registered in the account.
Carriers available to the account.

​
Data Model

The following diagram illustrates the relationships between the core data streams in Lixlog. The arrows indicate the join keys that link the different entities, providing a clear overview of the logistics structure.

​
Implementation Notes

​
Data Quality Considerations

  • Nested Data: Some columns hold structured data that is stored as a JSON string, for example the items of an order, the packages of a product, or the carrier options of a quote. Use your warehouse’s JSON functions (JSON_EXTRACT, etc.) to expand them in a Query or Notebook.

​
API Limits & Performance

  • Tracking Events: Lixlog only exposes tracking events one shipment at a time, so the Order Trackings stream makes one request per order. On accounts with a large order history, this extraction takes considerably longer.
  • Pagination and Collection Limits: The Lixlog API (which runs on Rails/Pagy) handles pagination dynamically. When a request asks for a page beyond the end of a collection (e.g., page 2 of a 1-page result), it returns an HTTP 400 Bad Request instead of an empty page. The Nekt connector safely handles these page-overflow errors, gracefully interpreting them as the end of the collection rather than aborting the extraction run.
  • Dynamic Page Optimization: To speed up your extractions and prevent sending doomed out-of-bounds requests, the connector memorizes the maximum observed page size dynamically, stopping pagination early when a page is returned shorter than the known limit.

​
Skills for agents

Download Lixlog skills file

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