Fortnox ACTION
Update Customer
Updates an existing customer in the Fortnox API. See the documentation.
- Action
- Writes data
- Destructive
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Fortnox account once, then configure and run Update Customer 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: "fortnox-update-customer",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fortnox: { authProvisionId: "apn_xxxxxxx" },
customerNumber: "Customer Number",
name: "Customer Name",
},
})
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": "fortnox-update-customer",
"configured_props": {
"fortnox": { "authProvisionId": "apn_xxxxxxx" },
"customerNumber": "Customer Number",
"name": "Customer Name"
}
}'// 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": "fortnox",
},
},
},
)
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: "fortnox-update-customer",
arguments: {
customerNumber: "Customer Number",
name: "Customer Name",
},
})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 |
|---|---|---|
customerNumber Customer Number | string | The number of the customer Required Dynamic |
name Customer Name | string | The name of the customer Optional |
email Email | string | The email address of the customer Optional |
phone Phone | string | The phone number of the customer Optional |
address1 Address 1 | string | The first line of the address Optional |
address2 Address 2 | string | The second line of the address Optional |
city City | string | The city of the address Optional |
zipCode Postal Code | string | The postal code of the address Optional |
country Country | string | The country of the address Optional |
type Customer Type | string | The type of the customer Optional |
vat VAT | string | The VAT number of the customer Optional |
vatType VAT Type | string | The VAT type of the customer 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
- fortnox-update-customer
- Version
- 0.0.2
- App
- Fortnox
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗