The Bookie ACTION
Create Sales Invoice
Creates a new sales invoice. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's The Bookie account once, then configure and run Create Sales Invoice 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: "the_bookie-create-sales-invoice",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
the_bookie: { authProvisionId: "apn_xxxxxxx" },
contactId: "Contact ID",
invoiceNumber: "Invoice Number",
},
})
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": "the_bookie-create-sales-invoice",
"configured_props": {
"the_bookie": { "authProvisionId": "apn_xxxxxxx" },
"contactId": "Contact ID",
"invoiceNumber": "Invoice Number"
}
}'// 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": "the_bookie",
},
},
},
)
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: "the_bookie-create-sales-invoice",
arguments: {
contactId: "Contact ID",
invoiceNumber: "Invoice Number",
},
})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 |
|---|---|---|
contactId Contact ID | string | The ID of the contact Required Dynamic |
invoiceNumber Invoice Number | string | The number of the invoice Required |
invoiceDate Invoice Date | string | The date of the invoice. Format: YYYY-MM-DD Required |
expirationDate Expiration Date | string | The expiration date of the invoice. Format: YYYY-MM-DD Required |
btwShifted VAT shifted | string | The VAT type Optional |
journalEntryLines Journal Entry Lines | string[] | An array of stringified objects of item entry lines. Example: { "description": "Boekregel 1", "btw_type": "PROCENT_21", "amount": "1200.0", "quantity": "2.00"} btw_type can be only 'PERCENT_9', 'PERCENT_21' or 'PERCENT_0' Optional |
attachment Attachment | string | Provide either a file URL or a path to a file in the /tmp directory (for example, /tmp/myFile.pdf). Optional |
syncDir SyncDir | dir | 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
- the_bookie-create-sales-invoice
- Version
- 0.0.4
- App
- The Bookie
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗