Automate your inventory with n8n

n8n connects Foundry to everything else you run — Slack, Sheets, email, your own services — with workflows you own. No Foundry-specific install required: everything on this page works with n8n's built-in nodes, on n8n Cloud or self-hosted.

Three ways in — combine them freely

  • AI agents — hand an n8n AI Agent the Foundry MCP server and let it work the catalog in plain English
  • Partner API — call any documented endpoint from an HTTP Request node
  • Webhooks — start workflows the moment something happens in Foundry, no polling
1

Create an API key

All three paths authenticate with the same credential: a Foundry API key, sent as a Bearer token. Create one in Foundry under Settings → API Keys → Create API Key and grant only the permissions your workflows need — a read-only key for reporting, webhooks.manage only if you'll create webhook subscriptions, and so on. A key is bound to exactly one organization.

In n8n, store it once as a Header Auth credential — header name Authorization, value Bearer fims_your_key_here — and reuse it across nodes.

2

Give an AI Agent your catalog

Foundry ships a hosted MCP server, and n8n's MCP Client Tool node speaks to it directly. Attach it to an AI Agent node and the agent can search, audit, and edit products, variants, BOMs, bundles, and custom fields — the same 33 tools Claude uses.

Setup

  • 1. Add an AI Agent node and, under its tools, an MCP Client Tool
  • 2. Endpoint: https://mcp.foundryims.com/mcp (HTTP streamable transport)
  • 3. Authentication: Header Auth with your Authorization: Bearer fims_… credential

The agent only reaches what the key's permissions allow — a read-only key makes the whole toolset read-only. Every write lands in Foundry's normal activity log.

3

Call the Partner API directly

For deterministic workflows — no AI in the loop — use n8n's HTTP Request node against the Partner API. Products, variants, stock, orders, purchase orders, invoices, bundles, and custom fields are all covered by the Partner API reference.

The shape of every call

  • • Base URL: https://api.foundryims.com/api/v1
  • • Auth: the same Header Auth credential from step 1
  • • List endpoints page with limit and offset query params
  • • Rate limit: 300 requests per minute per key — batch or paginate rather than fan out
4

Trigger workflows from Foundry events

Foundry POSTs signed events to any HTTPS endpoint, and an n8n Webhook node is exactly that. Start the workflow with a Webhook node, copy its production URL, then subscribe it to the events you care about:

curl -X POST https://api.foundryims.com/api/v1/webhooks \
  -H "Authorization: Bearer fims_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "n8n order flow",
        "url": "https://your-n8n.example.com/webhook/abc123",
        "events": ["order.created", "order.shipped"]
      }'

Save the secret immediately

The response includes the endpoint's signing secret (whsec_*) — only on creation. Store it in n8n as a credential or variable and use a Code node to verify the X-Foundry-Signature header (HMAC-SHA256), so a stray POST to your webhook URL can't impersonate Foundry. Full event catalog, payload shapes, and a verification snippet live in the webhooks reference.

Respond fast, then work

Set the Webhook node to respond immediately rather than at workflow end. Foundry retries failed deliveries eight times, but an endpoint that fails five deliveries in a row is automatically disabled — a long-running workflow that times out the response will eventually switch its own trigger off.

5

Workflows worth building

order.created

New order lands from any channel → post the order number, channel, and line count to a Slack channel or append it to a Google Sheet.

inventory.availability_changed

Availability drops below your threshold → open a task, email the buyer, or draft a purchase order line in another system.

import.completed

A supplier feed finishes → check the skipped-row count and alert someone only when it is not zero, instead of eyeballing every import.

variant.cost_changed

A vendor cost moves → recompute margin against the live channel price and flag anything that fell below target.

purchase_order.status_changed

A PO is received → notify the warehouse channel and log the receipt against your own dashboard.

AI agent (no trigger)

A nightly agent walks the catalog for variants missing a UPC or image and emails one consolidated report.

Not a Foundry customer yet? Book a demo. Building something and hit a wall? Email support — real workflows decide what we build next.