Mindbody ACTION
Get Client Visits
Returns the paginated list of visit records for a specific Mindbody client (member), each including its date/datetime (e.g.
StartDateTime). Use this to derive retention metrics: visit count is the total record count across all pages and last visit date is the latest StartDateTime. Requires the client's numeric ID - use Search Clients first to look up the ID by name or email. Note: Get Client Details may already surface scalar visit-summary fields; use this action when you need the full per-visit history for precise date math or milestone detection. Iterate offset to page through the full history. IMPORTANT: the API defaults startDate to today and endDate to end of today, so for true lifetime spend you MUST set startDate to an early date (e.g. 2000-01-01) and page through all results via offset. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Mindbody account once, then configure and run Get Client Visits 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: "mindbody-get-client-visits",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mindbody: { authProvisionId: "apn_xxxxxxx" },
clientId: "Client ID",
startDate: "Start Date",
},
})
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": "mindbody-get-client-visits",
"configured_props": {
"mindbody": { "authProvisionId": "apn_xxxxxxx" },
"clientId": "Client ID",
"startDate": "Start Date"
}
}'// 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": "mindbody",
},
},
},
)
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: "mindbody-get-client-visits",
arguments: {
clientId: "Client ID",
startDate: "Start Date",
},
})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 |
|---|---|---|
clientId Client ID | string | The unique ID of the Mindbody client (member). Use Search Clients to look up the ID by name or email. Required |
startDate Start Date | string | Filter results on or after this date. Format: YYYY-MM-DD (e.g., 2026-01-01). Optional |
endDate End Date | string | Filter results on or before this date. Format: YYYY-MM-DD (e.g., 2026-12-31). Optional |
limit Limit | integer | Maximum number of results to return per page. Minimum 1, maximum 200. Defaults to 100. Optional |
offset Offset | integer | Number of results to skip for pagination. Defaults to 0. 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
- mindbody-get-client-visits
- Version
- 0.0.2
- App
- Mindbody
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗