Freshdesk ACTION
List Tickets
Fetch up to 100 tickets according to the selected filters. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Freshdesk account once, then configure and run List Tickets 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: "freshdesk-list-all-tickets",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
freshdesk: { authProvisionId: "apn_xxxxxxx" },
orderBy: "Sort By",
orderType: "Sort Order",
},
})
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": "freshdesk-list-all-tickets",
"configured_props": {
"freshdesk": { "authProvisionId": "apn_xxxxxxx" },
"orderBy": "Sort By",
"orderType": "Sort Order"
}
}'// 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": "freshdesk",
},
},
},
)
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: "freshdesk-list-all-tickets",
arguments: {
orderBy: "Sort By",
orderType: "Sort Order",
},
})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 |
|---|---|---|
orderBy Sort By | string | Which field to sort tickets by. Defaults to Created At Optional |
orderType Sort Order | string | Whether to sort in ascending or descending order. Defaults to descending Optional |
requesterId Requester ID | integer | Filter by the numeric Freshdesk requester ID, for example 12345. Obtain it from the Freshdesk requester record or API. Optional |
email Email | string | Filter by the requester's email address, for example user@example.com. Optional |
companyId Company ID | integer | Filter by the numeric Freshdesk company ID, for example 67890. Obtain it from the Freshdesk company record or API. Optional |
updatedSince Updated Since | string | Filter tickets updated since the specified date and time in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Optional |
perPage Per Page | integer | Number of tickets to return per page. Must be between 1 and 100. Optional |
include Include | string[] | Optional array of response fields. Supported values are description, requester, and stats; for example, ['description', 'requester']. 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
- freshdesk-list-all-tickets
- Version
- 0.2.16
- App
- Freshdesk
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗