Connect QLS

This guide walks you through connecting the QLS Fulfilment and Parcel Service API to your Engaige agent. Once set up, your agent can look up orders, retrieve shipment status directly during customer conversations.

Step 1: Create an HTTP Integration

The HTTP Integration stores your connection to the QLS API, including the base URL and authentication credentials. You configure this once, and all your QLS actions share it.

1. In your Engaige dashboard, go to Setting and Integrations in the left sidebar.

2. Click Enable Integration and give the integration a name.

3. Fill in the integration details:

   Field	Value
   Name	QLS (or any recognisable name)
   Base URL	api.pakketdienstqls.nl
   Authentication	Basic Auth
   Username	Your QLS portal username
   Password	Your QLS portal password

4. Click Save.

Step 2: Create HTTP Actions

HTTP Actions define the specific API calls your agent can make. Each action maps to one QLS API endpoint. You can add as many actions as you need.

To add an action:

1. Go to Actions in your Engaige dashboard, in the left side menu

2. Click Add Action, scroll down and select Call API.

Action: Get Order

Retrieves the details of a specific order by its order ID. In Instructions, choose the QLS integration you created in Step 1 and add an action description for the AI Agent so it has context on when to use the action.

In the tab API Connection, set the following values for parameters below:

Request Body template:

Add this to the request body:

{"order_id": #{order_id}}

In the tab Action Input, you will need to describe the parameters you just added in the request body template. The order_id is the order number of the customer.

In the tab Test, you can add a real order number and test the action on the endpoint and values you have added.

Action: Get Shipment

Retrieves shipment information for a specific shipment, including its current tracking status and carrier details.

Request Body template:

Add this to the request body:

{"shipment_id": #{shipment_id}}

In the tab Action Input, you will need to describe the parameters you just added in the request body template. The shipment_id is the shipment number of the customer.

In the tab Test, you can add a real order number and test the action on the endpoint and values you have added.Action: Get Shipments for Order (optional)

Retrieves all shipments linked to a specific order. Helpful when an order has multiple parcels.

Action: Get Shipments for Order

Request Body template:

Add this to the request body:

{"shipment_id": #{shipment_id}}

In the tab Action Input, you will need to describe the parameters you just added in the request body template. The shipment_id is the shipment number of the customer.

Step 3: Attach Actions to Your Agent

Once your actions are created, you need to add them to policies so your agent can start using them.

1. Open the Policies screen and create a policy where this action will be used in.

2. Add the action to a policy step.

3. Test the policy in the Playground by triggering it.

Your agent can now call QLS during a conversation. When a customer asks about an order or shipment, the agent will use the appropriate action to fetch the information and respond with up-to-date data.

Tips

• Use v2 endpoints whenever possible. QLS recommends v2 for better performance. The paths in this guide all use /v2/.

• Keep credentials secure. Your QLS username and password are stored encrypted in the integration. Never share them in action configurations or agent instructions.

• Test before going live. After setting up each action, use the Test button in the dashboard to verify the action returns the expected response with a known order or shipment ID.

Troubleshooting: if you receive any errors upon testing your actions

Further Resources

• QLS Knowledge Base: qls.nl

• QLS API Reference: api.pakketdienstqls.nl/swagger

• QLS IT Support: available via the QLS portal

This guide covers the most common QLS actions. If you need additional actions (e.g. Create Order, Print Label, List Products), the same pattern applies: choose the right v2 endpoint from the QLS API reference, create an HTTP Action in Engaige, and add it to the policies.