Bubble ACTION
Search Things
Searches for things (records) in your Bubble app's database with optional filtering, sorting, and pagination. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Bubble account once, then configure and run Search Things 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: "bubble-search-things",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bubble: { authProvisionId: "apn_xxxxxxx" },
typeName: "Data Type Name",
constraints: ["Constraints"],
},
})
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": "bubble-search-things",
"configured_props": {
"bubble": { "authProvisionId": "apn_xxxxxxx" },
"typeName": "Data Type Name",
"constraints": ["Constraints"]
}
}'// 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": "bubble",
},
},
},
)
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: "bubble-search-things",
arguments: {
typeName: "Data Type Name",
constraints: ["Constraints"],
},
})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 |
|---|---|---|
typeName Data Type Name | string | The name of the data type (e.g., customer, product). The API will convert this to lowercase with spaces removed. Required |
constraints Constraints | string[] | Array of search filters as JSON strings. Each constraint should be a JSON object with key, constraint_type, and value properties. Example: {"key": "name", "constraint_type": "equals", "value": "John"}. Supported constraint types: equals, not equal, is_empty, is_not_empty, text contains, not text contains, greater than, less than, in, not in, contains, not contains, geographic_search. Optional |
cursor Cursor | integer | Starting position for pagination (rank of first item to return) Optional |
limit Limit | integer | Maximum number of items to return (up to 50,000 for standard plans, 10,000,000 for Enterprise) Optional |
sortField Sort Field | string | Field name to sort results by (defaults to creation date) Optional |
descending Descending | boolean | Set to true to sort in descending order, false for ascending 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
- bubble-search-things
- Version
- 0.0.2
- App
- Bubble
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗