Loyverse ACTION
Create Receipt
Creates a new receipt for a specific store. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Loyverse account once, then configure and run Create Receipt 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: "loyverse-create-receipt",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
loyverse: { authProvisionId: "apn_xxxxxxx" },
storeId: "Store ID",
lineItems: ["Line Items"],
},
})
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": "loyverse-create-receipt",
"configured_props": {
"loyverse": { "authProvisionId": "apn_xxxxxxx" },
"storeId": "Store ID",
"lineItems": ["Line Items"]
}
}'// 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": "loyverse",
},
},
},
)
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: "loyverse-create-receipt",
arguments: {
storeId: "Store ID",
lineItems: ["Line Items"],
},
})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 |
|---|---|---|
storeId Store ID | string | Select a store or provide a store ID. Required Dynamic |
lineItems Line Items | string[] | An array of JSON-stringified objects. You can use the Generate Receipt Items action to generate these items. Required |
paymentTypeId Payment Type ID | string | Select a payment type or provide a payment type ID. Required Dynamic |
employeeId Employee ID | string | Select an employee or provide an employee ID. Optional Dynamic |
order Order | string | The order name or number associated with the receipt Optional |
customerId Customer ID | string | Select a customer or provide a customer ID. Optional Dynamic |
source Source | string | The name of the source this receipt comes from. By default it is the name of the application that created the receipt. Optional |
receiptDate Receipt Date | string | A date/time string such as 2022-03-15T18:30:00Z. By default, this is the date/time the receipt was created. Optional |
totalDiscounts Total Discounts | string[] | The list of all discounts applied in the receipt, as JSON-stringified objects. See the documentation for the expected properties. Optional |
note Note | string | The receipt's note 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
- loyverse-create-receipt
- Version
- 0.0.2
- App
- Loyverse
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗