Monta ACTION
Update Order
Change an existing order by its ID, for example to correct a customer's delivery address before it is picked. Call this directly with the order ID and the fields to change. When changing the delivery address, first read the current address with Get Order, then call this with the full address plus your change, since Monta replaces the entire address (it needs at least Street, City, and Country Code). Monta rejects address changes once picking has started (error 17) or after the order has shipped (error 19). See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Monta account once, then configure and run Update Order from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "monta-update-order",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
monta: { authProvisionId: "apn_xxxxxxx" },
orderId: "Order ID",
street: "Delivery Street",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "monta-update-order",
"configured_props": {
"monta": { "authProvisionId": "apn_xxxxxxx" },
"orderId": "Order ID",
"street": "Delivery Street"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "monta",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "monta-update-order",
arguments: {
orderId: "Order ID",
street: "Delivery Street",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
orderId Order ID | string | The ID of an order. Use the List Order ID Options action to discover order IDs. Required Dynamic |
street Delivery Street | string | The street name Optional |
houseNumber Delivery House Number | string | The house number Optional |
houseNumberAddition Delivery House Number Addition | string | An addition to the house number Optional |
postalCode Delivery Postal Code | string | The postal code Optional |
city Delivery City | string | The city Optional |
state Delivery State | string | The state or province Optional |
countryCode Delivery Country Code | string | The ISO 3166-1 alpha-2 country code (e.g. NL) Optional |
company Delivery Company | string | The company name Optional |
firstName Delivery First Name | string | The recipient's first name Optional |
middleName Delivery Middle Name | string | The recipient's middle name Optional |
lastName Delivery Last Name | string | The recipient's last name Optional |
phoneNumber Delivery Phone Number | string | The recipient's phone number Optional |
emailAddress Delivery Email Address | string | The recipient's email address Optional |
additionalFields Additional Fields | object | Additional order properties to send in the request body, using Monta's request-body casing (e.g. { "Comment": "..." }) Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- monta-update-order
- Version
- 0.0.2
- App
- Monta
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗