Skip to content
Slipmill

HTTP module

Make.com packing slips. JSON in, PDF out.

A Make HTTP module can POST packing-slip JSON to Slipmill. Header x-sm-key. JSON in, US Letter application/pdf out.

Get a Slipmill keyRead the schema

Make (some desks still say Integromat) already maps the order. The missing piece is a packing slip that is not another HTML module. Slipmill prints from the JSON you built. HTTP module. POST /v1/render. Header x-sm-key.

Set the URL to the mill. Method POST. Headers: x-sm-key and Content-Type application/json. Body is the packing-slip or invoice schema. The module receives application/pdf. Save it, email it, or hand it to the printer step you already run.

This is not a Make app listing. There is no official Slipmill module. Any scenario that can set a header can print. You keep the shop, the warehouse hook, or the sheet as the trigger. Make maps. The mill prints.

We do not buy postage. We do not file customs. We do not calculate tax. invoice uses integer cents and tax_cents as sent if you need a bill. packing-slip is the box insert: SKU, qty, ship-to.

Two locked templates we own. You do not maintain CSS inside a Make aggregator. You do not upload HTML. Starter proves the module. Paid plans drop the footer.

n8n and Zapier share the same HTTP shape and have their own pages. Distinct intros. Same mill. Get a key and POST.

Make scenarios that already parse a webhook can map the mill fields in a Set Multiple Variables module, then hand JSON to HTTP. Do not build an HTML invoice in a text aggregator and hope a renderer lives on the other side. The mill owns the plate.

Retries count. If Make repeats a failed bundle, you spend another render. Handle errors in the scenario. Starter and Pro stop at the included cap. Scale meters overage. Public names stay Starter, Pro, and Scale.

Integromat was the old name. The HTTP module is the same idea: URL, headers, body, binary response. Save as invoice.pdf or packing-slip.pdf. Print it or attach it. Do not ask the mill to talk to a carrier or to file a customs form.

POST from an HTTP module

Make already mapped the order. The mill does not need a special connector. Use an HTTP module. Method POST. URL https://slipmill.com/v1/render. Header x-sm-key. Content-Type application/json. Body: template packing-slip or invoice, brand, and data.

The response is application/pdf, US Letter, synchronous. One request is one document. Save the bytes. Print them or attach them. Two locked templates we own. We do not ship the box. We do not buy postage.

curl

curl -X POST https://slipmill.com/v1/render \
  -H "x-sm-key: YOUR_SLIPMILL_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "packing-slip",
    "brand": {
      "name": "Northline Goods",
      "accent": "#9E2A22",
      "address": "18 Mercer Street, Hoboken, NJ 07030"
    },
    "data": {
      "order_id": "NL-10428",
      "date": "2026-08-31",
      "ship_to": {
        "name": "Cedar & Pine Outfitters",
        "address": "440 Warehouse Ave, Dock 3",
        "city": "Newark",
        "region": "NJ",
        "postal": "07105",
        "country": "US"
      },
      "from": {
        "name": "Northline Goods",
        "address": "18 Mercer Street, Hoboken, NJ 07030"
      },
      "items": [
        { "sku": "TOTE-12", "name": "Canvas tote — natural", "qty": 12 }
      ]
    }
  }' \
  --output packing-slip.pdf

Questions

Yes. The product is Make. The module is HTTP. Header x-sm-key. POST /v1/render.