Integration

Order Sender integration

Order Sender Business is an order-collection app for sales agents and wholesale networks (Italy). With this API an agent can export orders, quotes, customers, prospects, customer addresses, suppliers, products, price lists, discounts, payment conditions and invoice documents as JSON, import customer addresses, price lists, discounts, payment conditions, customer price list assignments and invoice documents in bulk, delete records by code, and schedule a bulk import of price lists or discounts from a remote CSV file. Field names are the vendor's Italian ones (codice = code, nome = name, fornitore = supplier, cliente = customer, prezzo = price, sconto = discount). Not exposed: the agent commission tables (pay rates), the access-check route (no body), IBAN, personal tax codes (codice fiscale), agent contact details and commission values in exports, and the import of customers, prospects, suppliers and products (JSON or CSV): those records carry the withheld IBAN, tax code and commission fields, and the docs do not say whether an import of an existing code replaces the whole record, so an import could blank values the agent cannot see. Authentication is the company code (cod) and an API token generated in the Order Sender Business back office (API section, API Management), both sent as query parameters.

Connect Order Sender How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Order Sender.Built from the 30 Order Sender tools below, on the connection you add once.

What you can do with Order Sender

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Discounts, 4 operations

delete_discountsDelete discountsPOSTPermanently deletes discounts, each identified by the key fields given in items (see list_discounts). Answers result ok or ko.
import_discountsImport discountsPOSTImports discounts in bulk from an array of JSON records; changes the account's data. The docs do not say how a record whose code already exists, or a field left out of a record, is handled.
import_discounts_from_csvImport discounts from csvGETSchedules a background import of discounts from a CSV file at file_uri (no header row) and answers result ok at once; the outcome (imported, errors, duplicates) is POSTed to the cb callback URL. Writes data.
list_discountsList discountsGETExports all discounts of the Order Sender account as JSON records (Italian field names).

Customer addresses, 3 operations

delete_customer_addressesDelete customer addressesPOSTPermanently deletes customer addresses, each identified by the key fields given in items (see list_customer_addresses). Answers result ok or ko.
import_customer_addressesImport customer addressesPOSTImports customer addresses in bulk from an array of JSON records; changes the account's data. The docs do not say how a record whose code already exists, or a field left out of a record, is handled.
list_customer_addressesList customer addressesGETExports all customer addresses of the Order Sender account as JSON records (Italian field names).

Customer price lists, 3 operations

delete_customer_price_listsDelete customer price listsPOSTPermanently deletes customer price lists, each identified by the key fields given in items (see list_customer_price_lists). Answers result ok or ko.
import_customer_price_listsImport customer price listsPOSTAssigns price lists to customers in bulk; a record matching codice_clienti + codice_listini (+ codice_fornitori) is updated, otherwise inserted. Changes the account's data.
list_customer_price_listsList customer price listsGETExports all customer price lists of the Order Sender account as JSON records (Italian field names).

Invoice documents, 3 operations

delete_invoice_documentsDelete invoice documentsPOSTPermanently deletes invoice documents, each identified by the key fields given in items (see list_invoice_documents). Answers result ok or ko.
import_invoice_documentsImport invoice documentsPOSTInserts or updates invoice documents (situazione amministrativa) in bulk; a record matching codice_fornitori + codice_clienti + numero_fattura is updated, otherwise inserted. Changes the account's data.
list_invoice_documentsList invoice documentsGETExports all invoice documents of the Order Sender account as JSON records (Italian field names).

Payment conditions, 3 operations

delete_payment_conditionsDelete payment conditionsPOSTPermanently deletes payment conditions, each identified by the key fields given in items (see list_payment_conditions). Answers result ok or ko.
import_payment_conditionsImport payment conditionsPOSTImports payment conditions in bulk from an array of JSON records; changes the account's data. The docs do not say how a record whose code already exists, or a field left out of a record, is handled.
list_payment_conditionsList payment conditionsGETExports all payment conditions of the Order Sender account as JSON records (Italian field names).

Price lists, 3 operations

import_price_listsImport price listsPOSTImports price lists in bulk from an array of JSON records; changes the account's data. The docs do not say how a record whose code already exists, or a field left out of a record, is handled.
import_price_lists_from_csvImport price lists from csvGETSchedules a background import of price lists from a CSV file at file_uri (no header row) and answers result ok at once; the outcome (imported, errors, duplicates) is POSTed to the cb callback URL. Writes data.
list_price_listsList price listsGETExports all price lists of the Order Sender account as JSON records (Italian field names).

Customer payment conditions, 2 operations

import_customer_payment_conditionsImport customer payment conditionsPOSTImports customer payment conditions in bulk from an array of JSON records; changes the account's data. The docs do not say how a record whose code already exists, or a field left out of a record, is handled.
list_customer_payment_conditionsList customer payment conditionsGETExports all customer payment conditions of the Order Sender account as JSON records (Italian field names).

Customers, 2 operations

delete_customersDelete customersPOSTPermanently deletes customers, each identified by the key fields given in items (see list_customers). Answers result ok or ko.
list_customersList customersGETExports all customers of the Order Sender account as JSON records (Italian field names).

Products, 2 operations

delete_productsDelete productsPOSTPermanently deletes products, each identified by the key fields given in items (see list_products). Answers result ok or ko.
list_productsList productsGETExports all products of the Order Sender account as JSON records (Italian field names).

Prospects, 2 operations

delete_prospectsDelete prospectsPOSTPermanently deletes prospects, each identified by the key fields given in items (see list_prospects). Answers result ok or ko.
list_prospectsList prospectsGETExports all prospects of the Order Sender account as JSON records (Italian field names).

Orders, 1 operation

list_ordersList ordersGETExports orders as JSON records: header (numero, data_invio, payment and delivery terms), customer, destination, supplier, agent name and article lines (codice, quantita, prezzo, sconto). Filter by dates, numbers, ids or fornitore.

Quotes, 1 operation

list_quotesList quotesGETExports quotes (preventivi) as JSON records, same layout as list_orders: header, customer, destination, supplier, agent name and article lines. Filter by date range, number range, ids or fornitore.

Suppliers, 1 operation

list_suppliersList suppliersGETExports all suppliers of the Order Sender account as JSON records (Italian field names).

Use Order Sender from Claude Code, Cursor or Codex

Connect Order Sender in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Order Sender operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Order Sender

Create your workspace
Sign up free. Nothing to install.
Connect Order Sender once
Add your Order Sender connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.