View as Markdown
Trengo icon

Trengo ACTION

List Tickets

List tickets according to the specified criteria. See the documentation
  • Action
  • Read only
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Trengo 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: "trengo-list-tickets",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    trengo: { authProvisionId: "apn_xxxxxxx" },
    status: "Status",
    userIds: [10],
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

List Tickets inputs
Property Type Description
status Status string
The ticket's status
Optional
userIds User IDs integer[]
Filter by one or more user IDs
Optional Dynamic
channelIds Channel IDs integer[]
Filter by one or more channel IDs
Optional Dynamic
lastMessageType Last Message Type string
Filter by the type of the last message
Optional
sortDirection Sort Direction string
Sort ascending or descending by last message date
Optional
maxResults Max Results integer
Maximum number of tickets to return (if not specified, all results will be returned)
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
trengo-list-tickets
Version
0.0.10
App
Trengo
Authentication
API key
Read-only
Yes
Destructive
No
Open world
Yes