Jira TRIGGER
New Event
- Trigger
- Polling
- OAuth
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Jira 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: "jira-events",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
cloudId: "Cloud ID",
},
webhookUrl: "https://example.com/webhooks/jira",
})
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": "jira-events",
"webhook_url": "https://example.com/webhooks/jira",
"configured_props": {
"jira": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"cloudId": "Cloud ID"
}
}'MCP servers expose Jira 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 Webhook renewal schedule | $.interface.timer | Jira expires a webhook 30 days after it is registered. This runs in the background, so you should not need to modify this schedule. See the documentation Required |
cloudId Cloud ID | string | The Jira Cloud site ID (for example, 11223344-a1b2-3b33-c444-def123456789). Use Get Cloud ID to discover IDs. See the documentation Required Dynamic |
jqlFilter JQL Filter | string | The JQL filter that specifies which issues the webhook is sent for, only a subset of JQL can be used, e.g. project = P1 See supported JQL filters Required |
overrideExistingWebhooks Override Existing Webhooks | boolean | Override existing webhooks with this new Pipedream source's webhook. Recommend to set this to true if you have an existing Jira webhook that you no longer use and want to override with the new Pipedream source. Optional |
events Event types | string[] | The Jira events that trigger the webhook Required |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Jira 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
- jira-events
- Version
- 0.0.25
- App
- Jira
- Authentication
- OAuth
- Delivery
- Polling source
- Output
- Events emitted by Jira.
- Source
- View on GitHub ↗