Back to documentation
Katana MRP: API to HubSpot
Overview of what information we get from the Katana Sales Orders and Customers API, and how it's written to HubSpot (Deals, Contacts, Companies).
Sales Orders → Deals
Each Sales Order in Katana becomes a Deal in HubSpot. Webhooks trigger real-time sync on creation or updates.
| Katana field | Description | HubSpot property | Notes |
|---|---|---|---|
| id | Unique Sales Order ID | katana_id | Used for ID link mapping |
| customer_id | Customer ID | katana_customer_id | Links to Contact/Company |
| order_no | Order number | dealname, katana_order_no | — |
| order_created_date | Creation date | katana_order_date | — |
| delivery_date | Planned delivery date | closedate, katana_delivery_date | — |
| picked_date | Picked/packed date | katana_picked_date | — |
| location_id | Shipping location ID | katana_location_id | — |
| status | Order status | katana_status | — |
| currency | Currency | deal_currency_code, katana_currency | — |
| conversion_rate | Currency conversion rate | katana_conversion_rate | — |
| conversion_date | Conversion rate date | katana_conversion_date | — |
| invoicing_status | Invoicing status | katana_invoicing_status | — |
| total | Order total (incl. taxes) | amount, katana_total | — |
| total_in_base_currency | Total in base currency | katana_total_base_currency | — |
| additional_info | Additional notes | description, katana_additional_info | — |
| customer_ref | Customer reference | katana_customer_ref | — |
| ecommerce_order_type | E-commerce platform | katana_ecommerce_type | — |
| ecommerce_store_name | E-commerce store name | katana_ecommerce_store | — |
| ecommerce_order_id | E-commerce order ID | katana_ecommerce_order_id | — |
| product_availability | Product availability status | katana_product_availability | — |
| product_expected_date | Product expected date | katana_product_expected_date | — |
| ingredient_availability | Ingredient availability status | katana_ingredient_availability | — |
| ingredient_expected_date | Ingredient expected date | katana_ingredient_expected_date | — |
| production_status | Production status | katana_production_status | — |
| created_at | Created timestamp | katana_created_at | — |
| updated_at | Updated timestamp | katana_updated_at | — |
Customers → Contacts & Companies
Customer data from Katana is synced as Contacts. For business customers, a Company is also created.
| Katana field | Description | HubSpot property | Notes |
|---|---|---|---|
| id | Unique customer ID | katana_customer_id | — |
| name | Customer name | firstname, lastname / company name | — |
| Email address | — | ||
| phone | Phone number (E.164 format) | phone | Normalized to international format |
| addresses[] | Address details | address, city, zip, country | — |
| default_address.country | Country (for phone number prefix) | — | — |
HubSpot objects
For each Sales Order, a Deal, Contact and optionally Company are created and linked together.
| Object | Fields | Purpose |
|---|---|---|
| Deal | dealname, amount, closedate, pipeline, dealstage + alle katana_* | One Deal per Sales Order; linked to Contact and Company. |
| Contact | email, phone, firstname, lastname, katana_customer_id | One Contact per customer; matching on email or phone number. |
| Company | name, katana_customer_id, domain | Company for business customers; linked to Contact. |
Processing flow
Katana webhooks trigger sync. Sales Order data is fetched, customer data is synced as Contact/Company, and the Deal is created or updated with all relevant properties.