BaseLinker MCP integration for AI agents.
Connect AI agents to BaseLinker through 6 structured actions, including list inventories, list inventory products, and list inventory warehouses. Review auth…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BaseLinker integration exposes
The BaseLinker Agent App exposes 6 provider-backed actions for productivity and data work. Its current contract lets an authorized agent list inventory catalogs available in baselinker storage, list basic product data from a baselinker inventory catalog, and list warehouses available in baselinker inventories. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BaseLinker account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BaseLinker capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_inventoriesREADList inventory catalogs available in BaseLinker storage.
list_inventory_productsREADList basic product data from a BaseLinker inventory catalog.
INPUTS: inventory_id / filter_id / filter_category_id / filter_ean / filter_sku
list_inventory_warehousesREADList warehouses available in BaseLinker inventories.
list_order_eventsREADList recent BaseLinker order events from the order journal.
INPUTS: last_log_id / logs_types / order_id
list_order_statusesREADList order statuses configured in the BaseLinker order manager.
list_ordersREADList BaseLinker orders using official order manager filters, returning up to 100 orders.
INPUTS: order_id / date_confirmed_from / date_from / id_from / get_unconfirmed_orders
INPUT CONTRACTS
Know what the action needs before it runs.
list_inventory_products
inventory_idREQUIRED- Inventory catalog ID returned by list_inventories.
filter_idOPTIONAL- Product ID filter.
filter_category_idOPTIONAL- Category ID filter.
filter_eanOPTIONAL- Product EAN filter.
filter_skuOPTIONAL- Product SKU filter.
list_order_events
last_log_idOPTIONAL- Log ID from which events should be retrieved.
logs_typesOPTIONAL- Event type IDs to include.
order_idOPTIONAL- Order identifier used to filter events.
list_orders
order_idOPTIONAL- Order identifier. When provided, only this order is returned.
date_confirmed_fromOPTIONAL- Unix timestamp value accepted by BaseLinker.
date_fromOPTIONAL- Unix timestamp value accepted by BaseLinker.
id_fromOPTIONAL- Order ID from which subsequent orders are collected.
get_unconfirmed_ordersOPTIONAL- Whether to include unconfirmed orders.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Inventories
List inventory catalogs available in BaseLinker storage. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_inventoriesVerify with List Inventory Products
List basic product data from a BaseLinker inventory catalog. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_inventory_productsSAFETY BOUNDARY
Operate BaseLinker with explicit limits
- Authorize BaseLinker with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned BaseLinker data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BaseLinker rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BaseLinker task completed successfully.
CONNECTION MODEL
API key
BaseLinker API token sent with the X-BLToken header. Generate it in BaseLinker under Account & other > My account > API: https://api.baselinker.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BaseLinker.