ServiceM8 ACTION
Update Job Payment
Update a job payment (loads the record, merges your fields, then POSTs). See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's ServiceM8 account once, then configure and run Update Job Payment 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: "servicem8-update-job-payment",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
servicem8: { authProvisionId: "apn_xxxxxxx" },
uuid: "Job payment to update",
jobUuid: "Job",
},
})
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": "servicem8-update-job-payment",
"configured_props": {
"servicem8": { "authProvisionId": "apn_xxxxxxx" },
"uuid": "Job payment to update",
"jobUuid": "Job"
}
}'// 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": "servicem8",
},
},
},
)
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: "servicem8-update-job-payment",
arguments: {
uuid: "Job payment to update",
jobUuid: "Job",
},
})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 |
|---|---|---|
uuid Job payment to update | string | Payment record to load, merge, and save (search or paste UUID). Required Dynamic |
jobUuid Job | string | Job this payment belongs to. Optional Dynamic |
actionedByUuid Actioned by | string | Staff member who recorded this payment. Optional Dynamic |
amount Amount | string | Payment amount in the account currency. Optional |
method Method | string | e.g. Cash, Credit Card, Bank Transfer, Stripe Optional |
note Note | string | Reference numbers, transaction IDs, or other details. Optional |
attachmentUuid Attachment | string | Optional attachment (e.g. receipt) linked to this payment. Optional Dynamic |
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
- servicem8-update-job-payment
- Version
- 0.0.1
- App
- ServiceM8
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗