JTL Order Actions
What is this?
ArminCX agents can read from and write to your JTL system directly. Instead of an agent only looking up an order, it can also change it: update the delivery date, set order fields, and update custom fields. You connect these actions inside the agent through your prompt, so the agent takes the right action on its own when a customer writes in.
Best practice: read before you write
Start every order flow with a lookup, then act. Have the agent fetch the order first so it works with live data, then run the action that changes something. This keeps the agent from updating the wrong field or the wrong order.
Available JTL actions
Action | What it does |
|---|---|
Get Order | Reads an order from JTL (status, fields, delivery info). Read-only, nothing is changed. |
Update Delivery Date | Sets or changes the delivery date on an existing JTL order. |
Update Order | Updates an existing JTL order. ⚠️ |
Update Custom Field | Updates a custom field on the order. The agent first fetches the custom fields available on your JTL system by the name you give it, then updates the matching one. |
List On Hold Reasons | Returns the on-hold reasons configured in your JTL system, so the agent can pick a valid one. |
⚙️ How to set it up
Open the agent you want to give JTL access to.
Add the JTL actions you need from the action list.
In the agent instructions, tell it when to use each action and in what order (for example: get the order, then update the delivery date). The actions are connected through prompting, not through a separate config screen.
Update Custom Field, no ID needed
You no longer have to look up and paste a numeric custom field ID. You give the agent the field name, the agent fetches the custom fields on your system, matches by that name, and updates the right one.
When to use JTL order actions
A customer asks where their order is. → Get Order.
A customer wants to move their delivery to a later date. → Get Order, then Update Delivery Date.
A customer asks to change an order detail you store in a custom field. → Get Order, then Update Custom Field.
An order needs an on-hold reason set. → List On Hold Reasons, then update.
When NOT to use JTL order actions
For order data that lives in Shopify, not JTL. Use the Shopify actions instead.
For a one-off manual change on a single order. Doing it directly in JTL is faster than reprompting an agent.
To read a field you only want to display. A lookup (Get Order) is enough. Don't add a write action you won't use.
Good to know: The Update Custom Field action matches on the field name you provide. If a field is named slightly differently in your JTL system, the agent updates by what it actually finds there, so use the exact field name from JTL in your instructions.
Good to know: Write actions (Update Delivery Date, Update Order, Update Custom Field) change live order data in JTL. Test each one on a single order before you let an agent run it on real tickets.
You're all set and good to go!