# New Event — Jira

> Emit new event when an event with subscribed event source triggered, See the documentation

- Key: `jira-events`
- Type: Trigger (Polling)
- Version: 0.0.25
- App: Jira (`jira`) — https://pipedream.com/apps/jira.md
- This page (HTML): https://pipedream.com/apps/jira/triggers/events
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/jira/sources/events/events.mjs

## Description

Emit new event when an event with subscribed event source triggered, [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-webhooks/#api-rest-api-3-webhook-post)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | 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 |
| `cloudId` | `string` | Yes | The Jira Cloud site ID (for example, 11223344-a1b2-3b33-c444-def123456789). Use Get Cloud ID to discover IDs. See the documentation Options are loaded from the connected account. |
| `jqlFilter` | `string` | Yes | 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 |
| `overrideExistingWebhooks` | `boolean` | No | 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. |
| `events` | `string[]` | Yes | The Jira events that trigger the webhook |

## Returns

Events emitted by Jira.

## Run it

**TypeScript**

```ts
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**

```bash
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**

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.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/jira.md · All apps: https://pipedream.com/apps