> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bubblav.com/llms.txt
> Use this file to discover all available pages before exploring further.

# nShift

> Track nShift shipments by tracking number or order number in chat

Connect an nShift Portal API client so customers can track shipments in chat by tracking number or order number. BubblaV adds two chatbot tools; nothing is installed on your site through nShift. It works with any carrier your nShift account connects.

## Why Connect nShift?

> **Track by Tracking Number**
>
> Look up a parcel by its tracking number: carrier, status, estimated delivery, pickup point, recent events, and a tracking link.

> **Track by Order Number**
>
> Find the shipments for an order. The customer verifies the order with the delivery postal code or the email used for the order.

> **Any Carrier**
>
> Covers shipments booked through nShift in the last 30 days, whichever carrier delivers them.

## Prerequisites

* A BubblaV website with edit access
* An nShift Portal account where you can create an API client

## Setup Steps

**1. Create an API client**

In nShift Portal, go to **Settings** → **API Configuration** → **Clients** → **Add**. Tick the **Portal Shipment Data API** scope, then copy the **Client ID** and **Client Secret**.

**2. Connect nShift**

Go to **Dashboard** → your website → **Integrations** → **Built-in Integrations** → **nShift** → **Connect**. Paste the **Client ID** and **Client Secret**.

**3. Optional: add a public tracking profile ID**

In nShift, open **Track** → **Settings** → **Public T\&T URL** and copy the UUID after `public-profile=`. Paste it into **Public tracking profile ID (optional)**. When nShift returns no tracking link for a shipment, the chatbot shares a link to your public tracking page instead.

**4. BubblaV adds the tools**

BubblaV validates the credentials with a live call and adds the two nShift tools to your chatbot.

**5. Test**

Ask the chatbot with a real tracking number, then with a real order number and postal code.

## Available Tools After Connection

| Tool | Parameters and Behavior | Example Query |
| - | - | - |
| `nshift_track_shipment` | Required `tracking_number` (8–40 letters/digits). Returns carrier, status, estimated delivery, pickup point, up to 5 recent events, and a tracking link. | "Where is my parcel 00370733741693409071?" with a real number |
| `nshift_track_order` | Required `order_number`, plus the delivery `postal_code` or `customer_email`. At least one must match the receiver, otherwise the chatbot answers that no shipment was found, without revealing that the order exists. | "Track order 10234, postal code 114 55" |

Both tools cover shipments booked in the last 30 days.

## Test Your Integration

Try these queries in your storefront chat:

* "Where is my parcel 00370733741693409071?" — replace the number with a real tracking number from a recent shipment.
* "Track order 10234, my postal code is 114 55" — use a real order number and the receiver's postal code.

## Troubleshooting

> **nShift rejected these credentials**
>
> Check the **Client ID** and **Client Secret**, and that the API client is enabled with the **Portal Shipment Data API** scope. Create a new client in **Settings** → **API Configuration** → **Clients** if needed, then connect again.

> **Shipment not found**
>
> Only shipments booked in the last 30 days are found. A shipment booked a moment ago may not have been transmitted to nShift yet, or the number may carry a typo.

> **Order lookup is refused**
>
> The postal code or email must match the receiver on the shipment. Ask the customer for the delivery postal code or the email used for the order, exactly as entered at checkout.

> **The chatbot gives no tracking link**
>
> nShift does not always return a tracking link. Add the **Public tracking profile ID**: click **Disconnect** on the nShift card, then **Connect** again and fill in the optional field. Use the same path to replace the Client Secret or the profile ID.

> **Tools are missing after connecting**
>
> If BubblaV shows **Connected, but the chatbot tools were not added**, or tools are missing, open the integration's **Configure** page and click **Sync Tools**. Then check that the nShift tools are enabled.

> [!NOTE]
>
> **Security**: Your Client Secret is stored encrypted, and the tools only read data. Receiver names, addresses, email, and phone numbers are never shown in the chat; only the pickup point (a business location) is shared. Order lookups need a matching postal code or email.

## Next Steps

> **[Customize Your Widget](https://docs.bubblav.com/user-guide/widget-design.md)**
>
> Match the chat widget to your storefront's appearance.

> **[Test Your Chatbot](https://docs.bubblav.com/user-guide/testing.md)**
>
> Check tracking answers and your configured website knowledge.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.