Importing to Toolio:
You can push files directly from your data warehouse into Toolio via SFTP into Toolio's Azure Storage.
Requirements
To setup Automated CSV Feeds, you will need to attain the following information from your Customer Success manager.
Connection String (username@hostname)
Password
Storage Container/Import Folder
Please keep in mind that the protocol must be SFTP and Port should be set to 22 when transferring the data.
File Naming Convention
Filenames sent to Toolio should follow the naming convention below:
{prefix}_{epoch time}.csvWhere, prefix refers to the data model and is followed by epoch time in seconds. Below are the different prefixes for the different data models
Prefixes
Data Model | Prefix |
Product | products |
Inventory | inventory |
Sale | sales |
Purchase Order | purchase_orders |
Receipt (if applicable) | receipts |
Bookings | bookings |
Bundles | bundles |
Location | location |
Transfer Order | transfer_order |
Examples
products_1588799741.csv
inventory_1588799764.csv
File Format
Encoding
Your CSV files must use UTF-8 encoding.
Header Line
First line in the file has to be the header line. Toolio uses header names to match values to Toolio data models. For each data model, header names will match either a core field already defined on the Toolio data models or a custom attribute that have been previously defined on the Toolio platform.
For example, for the Product Data model, you can use the header names, product_id or variant_id since these are core fields, but to pass in category as a field name, it first has to be configured as a custom attribute on Toolio.
Input Lines
Each line following the header line is an input line and should include all values in the order specified in the header line.
Data Model Format
Please see the Data Model Format document.
Exporting from Toolio:
Use the following parameters to configure the SFTP export from Toolio to an external storage destination.
Hostname
Username
PW
Port
Folder path (optional)
FAQs
Why Did My SFTP Connection Suddenly Fail With a Host Key Error?
Toolio's SFTP endpoint runs on Azure Blob Storage, and Microsoft rotates the underlying SSH host keys periodically as a standard security practice. When the host key rotates, a client that only trusts the previous key will refuse to connect, often with an error like "REMOTE HOST IDENTIFICATION HAS CHANGED" or "host key verification failed." Scheduled or unattended jobs are most affected, since there is no one present to accept the new key.
This is expected behavior on the client side, not an outage. Microsoft publishes both the current and the upcoming host keys in advance, along with their expiry dates, here: Host keys for SFTP support for Azure Blob Storage.
How Do I Prevent Host Key Errors From Breaking My Scheduled Jobs?
Pre-load both the current and the next host key into your client's known_hosts file. Because both keys are published ahead of time, you can add both entries in advance. When Azure rotates the key, either key validates, so the connection keeps working and you can leave strict host key checking fully enabled.
Removing the endpoint from known_hosts and re-accepting the new key on connect also works, but it is less secure, since it trusts whatever key is presented at that moment. Pre-loading both published keys avoids that trade-off. Always verify a new fingerprint against Microsoft's published list before trusting it.
If you need the exact current and upcoming fingerprints for your endpoint, contact your Customer Success Manager.
How Do I Get Notified When an Import Is Missing?
Set up Data Alerts so your team is notified promptly when an expected import does not arrive, rather than discovering it after the fact. This catches interrupted feeds from a host key change or any other cause.