Order & project status lookup

Plan: Pro and Custom. Who's this for: anyone whose visitors ask "where is my order?" or "what is the status of my project?" — and who has a backend system that already knows the answer. Where this lives: AI Agents → Order Status Connector in your dashboard sidebar.

#TL;DR

Connect your existing order or project backend to your agent, and visitors can ask "where is order #1234?" in the chat. The agent calls your endpoint with the order reference, your endpoint replies with the status, and the agent reads it back to the visitor. We never store the order data — your backend stays the source of truth.

You need:

1. An HTTPS endpoint on your side that accepts a POST request and returns a tiny JSON response.
2. The Coffield.io dashboard for your tenant.
3. The Pro plan or higher.

#What problem does this solve?

Visitors constantly ask three questions you don't want to answer by hand:

"Where is my order?" "Has my project been scheduled?" "When is my technician arriving?"

These questions have one thing in common: the answer already exists in your backend. You don't need an AI to guess — you need it to look up the truth in your system and read it back.

That's exactly what the order status connector does.

#How does it work?

1. A visitor types "What's the status of order ORD-9842?" into your agent.
2. The agent recognizes that it needs to look up an order and calls your endpoint.
3. Your endpoint replies with a short JSON blob like {"ok": true, "status": "shipped", "summary": "Out for delivery — arrives Tuesday"}.
4. The agent reads it back in plain language: "Your order is out for delivery and should arrive Tuesday."

We sign every request with HMAC so you can prove it's really us. We never cache the response — every visitor question is a fresh lookup.

#How do I set this up?

1. Sign in to your dashboard.
2. Open AI Agents → Order Status Connector in the left navigation.
3. Click New Order Status Connector.
4. Pick the provider — for now, the only choice is Generic HTTPS endpoint (HMAC-signed).
5. Paste your endpoint URL (must start with https:// — http:// is blocked for safety).
6. (Recommended) Click the Generate button next to Signing secret to mint a 64-character secret. Copy it now — you'll paste it into your backend so your endpoint can verify our signature.
7. Choose what your endpoint can answer:
   • Order lookups — for retail / e-commerce style references (orders, shipments, deliveries)
   • Project lookups — for service-business references (jobs, projects, tickets)
8. Save.

That's it. Your agent will start using the connector on the next conversation.

#What does my endpoint need to return?

Your endpoint will receive a POST with this JSON body:

{
  "kind": "order",            // or "project"
  "reference": "ORD-9842",    // exactly what the visitor typed
  "context": {},              // optional verification data the visitor supplied (e.g. email, zip)
  "tenant_id": 42
}

Reply with one of two shapes — success or failure.

#Success response

{
  "ok": true,
  "status": "shipped",
  "summary": "Out for delivery — arrives Tuesday",
  "details": {
    "carrier": "UPS",
    "tracking": "1Z999AA10123456784"
  }
}

#Failure / "not found" response

{
  "ok": false,
  "error_code": "not_found",
  "message": "We can't find an order with that reference."
}

#How do I prove the request came from Coffield.io?

Every request we send carries an X-Coffield-Signature header. Verify it before trusting the body. Here's a six-line PHP example:

$body = file_get_contents('php://input');
$sig  = $_SERVER['HTTP_X_COFFIELD_SIGNATURE'] ?? '';
$expected = 'sha256=' . hash_hmac('sha256', $body, $YOUR_SIGNING_SECRET);

if (! hash_equals($expected, $sig)) {
    http_response_code(401); exit;
}

Same pattern works in Node, Python, Ruby — compute HMAC-SHA256(body, signing_secret), prefix with sha256=, and compare in constant time.

#What headers do you send?

#What if my endpoint is slow or down?

We give your endpoint an 8-second timeout (configurable). If we don't get a reply in that window, the agent tells the visitor "I wasn't able to look that up right now" and offers to take a message instead.

Every failure is logged on the connector's dashboard row (look for the Last failure reason column) so you can see what your endpoint actually returned.

#Which tiers can use this?

The order status connector requires the Pro plan or higher. Visitors on Starter and Growth tenants will get a friendly "this feature isn't enabled" response from the agent if they ask for an order lookup.

#Can I have more than one connector?

Today: one active connector per tenant. That keeps lookups predictable — every visitor question hits the same backend. If you have multiple backends, you can route inside your own endpoint based on the reference prefix (e.g. ORD-* vs PROJ-*).

#What if I don't have a backend API?

The order status connector assumes you already have a system that knows order status. If you don't — or if your data lives in spreadsheets, email threads, or a tool without a public API — please contact support. We may be able to suggest a no-code bridge (Zapier, Make.com) or queue it for a vendor-specific provider (Shopify, ServiceTitan, Jobber are on the roadmap).

#Related pages

• Outbound webhooks — push events out of Coffield.io to your tools (the opposite direction).
• External integrations & MCP tokens — let outside agents call into your workspace.
• HubSpot CRM (Pro) — one-click CRM connector.