n8n / Implementation guide

n8n restock alerts for medical device distributors

Medical Device Distributors can use n8n, HubSpot CRM and approved Zapier Links to coordinate account-level restock tasks, with Claude summarizing verified consumption patterns. Keep clinical and patient data out of sales alerts unless a separately justified and compliant process authorizes it. Hospital inventory feeds are an additional dependency: purchase history alone does not prove the facility’s on-hand stock.

Tools: n8n; Claude 3.5 Sonnet, HubSpot CRM, Zapier Links
01

The industry-specific problem

Field reps forget periodic inventory checks, but an automatic reorder based on last month’s purchase can ship the wrong device size or overlook expiring lots. Sales opportunity and verified replenishment need different statuses.

02

Step-by-step workflow

  1. Obtain an authorized hospital inventory or consumption feed, or clearly label CRM purchase-history estimates.
  2. Normalize SKU, facility, unit of measure and lot/expiry data in n8n; avoid patient-level information.
  3. Use a supported Claude model to summarize demand changes and questions for the rep, replacing the retired Claude 3.5 Sonnet ID.
  4. Create a HubSpot task with source date, stock certainty and account owner. Use Zapier Links only for an approved authenticated bridge, not exposed patient payloads.
  5. Require a rep or authorized purchasing contact to verify the need before releasing an order; handle consignment and recalled lots separately.
03

Visual workflow

Authorized stock feed OR purchase-history estimate → n8n SKU/lot checks
→ Claude pattern summary → HubSpot account task → approved Zapier bridge
→ rep verification → replenishment decision
04

Specific configuration example

This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.

// n8n Code node: estimated consumption is not on-hand stock
const facility = $json;
return [{ json: { hubspotCompanyId: facility.hubspot_company_id,
  sku: facility.sku, sourceObservedAt: facility.source_timestamp,
  stockStatus: facility.inventory_feed_verified ? "observed" : "estimate",
  repTaskRequired: facility.below_reorder_point || facility.expiry_review_due,
  autoOrderAllowed: false, includePatientData: false,
  bridgeRef: facility.approved_zapier_route_id } }];
05

Outcome to measure

Illustrative planning metrics only. Not verified client results.

Track verified stockout risks identified and rep follow-through before reorder deadlines. Illustratively, five timely verified restock opportunities is useful activity evidence; revenue follows only from actual approved orders.

06

Compared with manual work or other tools

ERP reorder points are stronger when inventory is reliable. n8n adds CRM follow-through for field sales, but cannot replace the hospital’s purchasing authorization or device traceability.

07

Work with Imperio Automation

Have Imperio map your authorized inventory signals and build rep-reviewed HubSpot restock alerts.

Scope this workflow
08

Frequently asked questions

Can purchase history tell us current hospital stock?

Only as an explicitly uncertain estimate; obtain an authorized inventory source for observed stock.

Can alerts contain patient procedure details?

Avoid patient data in ordinary sales tasks; any exceptional use needs separate authorization and safeguards.

Can the workflow ship substitutes automatically?

No. Device equivalence, purchasing authorization and applicable traceability requirements need review.

09

Technical and regulatory references