TicketSauce TRIGGER
New Event
- Trigger
- Polling
- OAuth
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's TicketSauce account, configure the source, and choose the webhook where your backend receives events.
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 deployed = await pd.triggers.deploy({
id: "ticketsauce-new-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
ticketsauce: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
partnerId: "Partner ID",
},
webhookUrl: "https://example.com/webhooks/ticketsauce",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "ticketsauce-new-event",
"webhook_url": "https://example.com/webhooks/ticketsauce",
"configured_props": {
"ticketsauce": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"partnerId": "Partner ID"
}
}'MCP servers expose TicketSauce actions as on-demand tools.
New Event is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
timer Timer | $.interface.timer | Required |
partnerId Partner ID | string | Filter events by a specific partner ID (optional) Optional |
organizationId Organization ID | string | Filter events by a specific organization ID (optional) Optional |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes TicketSauce through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- ticketsauce-new-event
- Version
- 0.0.1
- App
- TicketSauce
- Authentication
- OAuth
- Delivery
- Polling source
- Output
- Events emitted by TicketSauce.
- Source
- View on GitHub ↗