Jenkins TRIGGER
New Jenkins Job Status Notification (Instant)
- Trigger
- Instant
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Jenkins 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: "jenkins-new-job-status-notification-instant",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jenkins: { authProvisionId: "apn_xxxxxxx" },
jobName: "Job Name",
},
webhookUrl: "https://example.com/webhooks/jenkins",
})
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": "jenkins-new-job-status-notification-instant",
"webhook_url": "https://example.com/webhooks/jenkins",
"configured_props": {
"jenkins": { "authProvisionId": "apn_xxxxxxx" },
"jobName": "Job Name"
}
}'MCP servers expose Jenkins actions as on-demand tools.
New Jenkins Job Status Notification (Instant) 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 |
|---|---|---|
jobName Job Name | string | The name of the Jenkins job to monitor for status updates. Required Dynamic |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Jenkins 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 — as it happens.
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
- jenkins-new-job-status-notification-instant
- Version
- 0.0.2
- App
- Jenkins
- Authentication
- API key
- Delivery
- Instant event
- Output
- Events emitted by Jenkins.
- Source
- View on GitHub ↗