An HTTP API column in any Clay table fires a personalized box per enriched row.
Any Clay table can ship boxes. Add an HTTP API column and each enriched row fires a Boxli send — recipient, box design, tracked landing pages, and handwritten note all mapped from your columns.
{
"first_name": "{{First Name}}",
"last_name": "{{Last Name}}",
"email": "{{Email}}",
"company": "{{Company}}",
"address_line_1": "{{Street}}",
"city": "{{City}}",
"state": "{{State}}",
"zip": "{{Zip}}",
"box_type_name": "ABM top target",
"landing_page_url": "https://yoursite.com/welcome/{{Email}}",
"message": "Hi {{First Name}} — loved your post.",
"external_id": "{{Clay Row ID}}"
}Clay’s own address enrichments map straight across: address_line to address_line_1, locality to city, admin_district to state, postal_code to zip. For a company that is the HQ or office address; Clay cannot supply home addresses. Optional fields worth knowing: box_type_name picks the design (required if you run several), message adds handwritten-note text, booking_url adds a second tracked QR, campaign_id groups sends, and email lets Boxli upsert the contact rather than duplicate it.
On each send, Boxli upserts the contact, pulls a box from inventory, generates the tracked QR and NFC codes, and queues pick-pack-ship. Delivery and engagement then stream back like any other send.
Every guide here lives in the in-app Help Center too — open Help in the sidebar.
Open Boxli