Starshipit

The Starshipit app connects Starshipit shipping and fulfilment to Sprigr Team. Agents can list unshipped and unmanifested orders, get carrier rates, buy and print labels, create and update orders, manifest carriers, track parcels, validate addresses, and record picking progress as order tags. An optional sync builds a private dispatch board that agents can search by status, carrier, service and destination, and tracking changes are emitted as events.

Note

Starshipit ships as a marketplace app with install-wide API-key authentication. There is no OAuth: an admin enters the Starshipit API key and subscription key at install time, and every agent with the app uses that credential. Anything that buys a label, voids, deletes, merges or manifests is confirmation-gated.

Prerequisites

• A Starshipit account. In Starshipit, open Settings > API to find the API key and subscription key.
• Admin or Owner role in your Sprigr Team organisation to install the app.

Installing and connecting

1. Install the app and enter the credentials

   Sign in to team.sprigr.com, open Apps in the sidebar, find Starshipit under Available, and click Install. The app asks for two required secrets, STARSHIPIT_API_KEY and STARSHIPIT_SUBSCRIPTION_KEY, before it will install. See Installing Apps.

2. Optional webhook token

   Set STARSHIPIT_WEBHOOK_TOKEN if you want the app to accept Starshipit status webhooks, and register the Starshipit webhook with the same bearer token. Leave it blank to rely on the 15-minute sync instead.

3. Turn on sync for the dispatch board

   Ask your agent to enable Starshipit sync. It runs the update_settings action. Until then search_shipments and the sync tools are no-ops; the live list and lookup actions work regardless.

4. Check the connection

   The app’s settings page shows the credential status (including “credentials set, but the connection test failed” if the keys are wrong) and recent activity. Ask your agent “How many orders are unshipped?” to confirm.

Try asking your agent

“How many orders are unshipped, and which carriers are they going with?”

“What are the rates to send order 10452 to Perth as a 2 kg satchel?”

“Tag order 10452 as PICKED into tote R8-S1.”

Sync, events and confirmation

• Dispatch board. With sync enabled, a backfill and then a 15-minute incremental sync project unshipped orders and recently shipped shipments into a private, faceted index. search_shipments filters it by status, carrier, service, destination country and stage, so “everything going to New Zealand with Aramex” is one query.
• Events. The sync emits starshipit.shipment.created, starshipit.tracking.updated and starshipit.order.delivered as a tracked parcel’s status advances, for workflows to act on.
• Confirmation before spending or destroying. Creating a shipment (which buys and prints the label), unshipping (voids the label), updating, deleting or merging orders, and creating a manifest all pause for your confirmation in the chat. Reads and tag writes never do.
• Reads are never turned into shipments. “Show me the unshipped orders” is answered with a list, never by shipping anything; a gated action only runs after you have approved the specific orders.

What agents can do

The main starshipit tool takes an action, with 22 actions:

• Read: list_unshipped, list_unmanifested, get_order, get_label, get_rates, get_tracking, get_tags, get_order_tags, list_delivery_services, validate_address, search_shipments.
• Write, not gated: create_order, assign_order, add_order_tags, delete_order_tags.
• Write, confirmation-gated: create_shipment (billable), unship_order, update_order, delete_order, merge_orders, create_manifest.
• Admin: update_settings to turn sync on or off.

Two narrower tools exist so a warehouse workflow can be granted only what it needs: starshipit_tags (read the account’s tags, add and remove tags on an order) and starshipit_shipping (rates, delivery services, create a shipment, re-read a label, unship). Neither can delete, merge, manifest or change settings.

Picking conventions already in use: PICKED, PICKED by <name>, and TOTE><bin> to record which tote an order was picked into. Starshipit truncates long tag values, so the meaningful part goes first.

Common use cases

• Morning dispatch check. “What is unshipped and what is unmanifested?” gives the team the day’s queue.
• Rate shopping. The agent compares carrier services and prices for an order before the label is bought.
• Pick-and-pack progress. As orders are picked, the agent tags them so the Starshipit desktop view shows what is done.
• Customer enquiry. “Where is order 10452?” returns the tracking events without opening Starshipit.
• Delivery notifications. A workflow on starshipit.order.delivered closes the loop in your support tool or CRM.

Troubleshooting

Credentials set, but the connection test failed The API key or subscription key is wrong or revoked. Update the app’s secrets from the Apps page with the values from Starshipit’s Settings > API.

search_shipments returns nothing Sync is off. Ask the agent to enable Starshipit sync and allow the first backfill to run.

An action is waiting for confirmation Buying a label, voiding, deleting, merging and manifesting pause until you confirm the specific orders in the chat.

Tags look cut off in Starshipit Starshipit truncates long tag values. Keep the meaningful part at the start.

Next steps

• Integrations Overview: See all available integrations.
• Shopify: Where most Starshipit orders originate.
• Workflows: React to tracking and delivery events.