DevRev ACTION
Create Ticket
Creates a new ticket in DevRev. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's DevRev account once, then configure and run Create Ticket 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: "devrev-create-ticket",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
devrev: { authProvisionId: "apn_xxxxxxx" },
appliesToPart: "Applies To Part",
ownedBy: ["Owned By"],
},
})
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": "devrev-create-ticket",
"configured_props": {
"devrev": { "authProvisionId": "apn_xxxxxxx" },
"appliesToPart": "Applies To Part",
"ownedBy": ["Owned By"]
}
}'// 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": "devrev",
},
},
},
)
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: "devrev-create-ticket",
arguments: {
appliesToPart: "Applies To Part",
ownedBy: ["Owned By"],
},
})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 |
|---|---|---|
appliesToPart Applies To Part | string | The part that the work applies to Required Dynamic |
ownedBy Owned By | string[] | The users that own the work Required Dynamic |
title Title | string | Title of the work object Required |
body Body | string | Body of the work object Optional |
customSchemaFragments Custom Schema Fragments | string[] | Array of IDs of custom schema fragments to use Optional Dynamic |
tagIds Tags | string[] | Array of IDs of tags associated with the work item Optional Dynamic |
revOrgId Rev Organization | string | The Rev organization that the ticket is associated with Optional Dynamic |
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
- devrev-create-ticket
- Version
- 0.0.3
- App
- DevRev
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗