Ongoing + nShift
Everything you need to connect Ongoing and nShift: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- Connect in about 20 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Ongoing
- Open the Ongoing API access setup
- Create or confirm the dedicated API user
- Copy the API username and password
- Confirm any client or goods owner identifiers
- Paste the credentials into Junipeer
- about 10 minutes
Prepare nShift
- Log in to nShift Delivery
- Open API keys
- Create a new key
- Enter the key details
- Save and copy the generated values
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Ongoing (2)
| Setting | What it controls | Key |
|---|---|---|
| Exclude Orders created before this date | Pick a date to skip older orders. | stdintegration_filter_ongoing_order_created_date |
| Goods owner | Choose which Ongoing goods owner this integration works with. | ongoing_goods_owner_id |
Settings for nShift (17)
| Setting | What it controls | Key |
|---|---|---|
| Add Return Label | Decide whether a return label should be added when this carrier is used. | add_return_label |
| Create Stored Shipment | Decide whether shipments should be created as stored shipments in nShift. | nshift_create_stored_shipments |
| Customer Attribute for AGENT (Service Point, Utlämningsställe) | Enter the name of the customer attribute that holds the agent (service point) code. | nshift_customer_attribute_agent |
| Customer Attribute for Door Code | Enter the name of the customer attribute that holds the door code. | nshift_customer_attribute_door_code |
| Default Nshift Sender ID | Enter the nShift Sender ID that your deliveries should be sent from by default. | nshift_default_sender_id |
| E-mail Notifications | Decide whether the carrier should send e-mail notifications about the shipment to the end customer. | use_email_notification |
| Enable Pickup Location | Decide whether the end customer can collect their delivery at a pickup location. | use_agent_code |
| Enable Testmode in Nshift | Decide whether shipments should be created in test mode in nShift. | nshift_test_mode_enabled |
Show all 17 settings
| Setting | What it controls | Key |
|---|---|---|
| Letter Notification | Decide whether the carrier should send a letter (avi) about the shipment to the end customer. | use_letter_notification |
| Map article attributes with addons | Connect product (article) attributes with shipping addons. | article_attribute_map |
| Minimum parcel weight | Enter the minimum weight of your parcels, in grams (g). | shipment_minimum_weight |
| Nshift Password or Secret ID | Enter your nShift password or secret ID. | nshift_password |
| Nshift Sender ID Mapper | Use a specific nShift Sender ID for shipments from a specific warehouse. | nshift_map_sender_ids |
| Nshift Shipping Carrier | Choose the nShift carrier service to use for shipments with this shipping method. | supplier_id |
| Nshift Username / ID | Enter your nShift username or ID. | nshift_username |
| SMS Notifications | Decide whether the carrier should send SMS notifications about the shipment to the end customer. | use_sms_notification |
| Shipping method Settings | Add specific shipping settings for different shipping methods. | supplier_map_settings |
Did this page help you?