Assembly Atlas docs
Leads

Parts requests, email and webhooks

Parts without a store id, or a whole list of them, come to you as a parts request with part numbers, quantities and the serial number filled in. Have them emailed, or posted to Zapier, Slack or your CRM.

What customers send#

From any part, customers choose a quantity and Add to request, then send the list from the request tab with their name, email and, optionally, the serial number of their machine. Parts with a store id can go to your store instead; see Add to cart.

Every request is kept under Requests in the console, whatever else you set up.

Where requests go#

Under Settings → Where requests go:

  • Email them to: one address, such as parts@yourcompany.com. Reply to the email and your reply goes to the customer.
  • Webhook (Catalog, Integrated and Quoting plans): a URL that receives each request as JSON, for Zapier, Make, Slack, your CRM or your order system.
  • Email the person who sent the request a copy: on by default.
  • Email a summary of last month’s results on the 1st and Email the week’s missed sales on Mondays: both on by default, sent to the address above. See Results.

The same settings apply to quote requests, accepted quotes, warranty claims and dealer orders.

Webhook format#

Each request is sent once, as a POST with a JSON body. Your endpoint should answer with a 2xx status. If it doesn’t, the request is still in the console, and a warning at the top of Overview and Settings says the webhook failed, how often and when. Fix the address and choose Fixed it.

Parts request#

{
  "customer": "Acme Equipment",
  "license": "acme",
  "type": "parts-request",
  "request": {
    "id": "…",
    "created": "2026-10-26T14:03:11.000Z",
    "catalog": "deck-60",
    "catalogTitle": "60\" Mower Deck",
    "client": { "name": "Dana Ruiz", "email": "dana@example.com", "serial": "MD60-118204" },
    "lines": [
      { "partNumber": "AS1-1001", "name": "Main bracket", "qty": 2 },
      { "partNumber": "AS1-1003", "name": "M8 hex nut", "qty": 8 }
    ],
    "page": "https://yourcompany.com/parts/deck-60"
  }
}

Quote request#

"type": "quote", with the quote under "quote": its number (Q-0417-7KX2), the client’s name, email, company, phone, date needed and notes, each part with its estimate, the total as a low–high range, and the uploaded file’s name and size.

Quote accepted#

"type": "quote-accepted": the client accepted a quote you sent, so it’s an order. Carries "number", "quoteId", the "offer" they accepted (revision, lines with quantities and prices, total, valid-until date) and the "acceptance": their name and title, PO number, ship-to address, message and the PO file’s name (the file itself is in the console).

Changes asked on a quote#

"type": "quote-changes", with "number", "quoteId" and the client’s "message".

Warranty claim#

"type": "warranty-claim", with the claim under "claim": its number, the owner, serial number, dates, the parts and what happened. Photos stay in the console.

Dealer order#

"type": "dealer-order", with the order under "order": its number, the dealer’s company and email, PO number, ship-to, notes, and each line with part number, quantity and unit price, plus the total.

Zapier#

  1. Create a Zap with Webhooks by Zapier → Catch Hook as the trigger and copy its URL.
  2. Paste it into Webhook in Settings and save.
  3. Send a test parts request from one of your catalogs, then pick it in Zapier to map the fields.

For Slack, add a Send Channel Message step after the trigger.