Widgets

A widget is a small Nash component — a live map, an arrival-time chip, a delivery list, a delivery-details panel — that you drop into your own website. It shows your customers live delivery information served by Nash, on a page you own and brand, instead of sending them somewhere else to check on an order.

A widget doesn't replace Nash's hosted customer tracking page — the link customers get in a tracking notification. A widget is a separate, operator-hosted component that lives on your own site and needs your own setup (an origin allowlist and a backend credential) before it will render. Nash dispatches the order and feeds the widget live status; the provider or your own fleet still performs the delivery.

Where you find it

Widgets live under Settings ▸ Connections ▸ Widgets, on a page subtitled Embeddable Nash components for your own site.

Note

You'll need organization-management permissions to open and edit Widgets. If you don't see it in your settings, ask an admin in your organization.

What you can embed today

The widget catalog lists five entries, but only one is ready to drop into a page right now:

• Live Map is the only widget with a copy-paste embed snippet today — turn it on, allow your origin, issue a credential, and you have a working embed.
• ETA Chip, Delivery List, and Delivery Details can be switched on and saved, but none of them produce a snippet yet — there's nothing to paste into your page for them.
• Nash Agent isn't part of this catalog at all. Its embeds are set up per agent, on that agent's own Embed tab — see what Nash Agent is.

The catalog also shows a few roadmap ideas as plain name chips with no switch. None of those are built yet.

What a widget needs before it serves

Three things have to be true at once before a widget will render on your site: it's turned on in the catalog, your page's exact origin is allowed, and your backend holds a credential it can exchange for a short-lived embed session. Nash can also temporarily pause a widget on its side — your own on/off setting stays untouched, but the widget won't serve until Nash lifts the pause. The mechanics of all three pieces, and how a credential becomes a session, are covered in how widgets work.

What you can do

• How widgets work — the concepts: the three things that gate a widget, how a credential becomes a short-lived session, and how a widget differs from the tracking page.
• Embed a Nash widget on your site — the four-step setup, start to finish, with a link to each step.
• Turn widgets on and off — the catalog, what each widget embeds, and the Nash pause.
• Allow the sites that can embed your widgets — add and remove the exact origins allowed to embed.
• Issue and manage embed credentials — issue, rotate, revoke, and rename the backend secrets a session is minted against.
• Widgets settings reference — every control, status, and rule on the page.