Jira events

Node catalog Triggers

On this page

Start a workflow from provider webhook events.

Usage and specifics

Choose the account, workspace or project and operation. Task and resource identifiers must belong to the authorized account. For a trigger, configure its mode and events, then publish the workflow. A simulated payload does not prove remote event delivery.

Technical type : jira_trigger. Runtime : nodulz.

Credentials and prerequisites

Project management webhook secret (integration / project_webhook). Dedicated secret for webhook signing or authentication

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`rateLimitEnabled`	`boolean`	-	-
`rateLimitMax`	`number`	-	-; > 0
`rateLimitWindowMs`	`number`	-	-; > 0
`allowedIps`	`array`	-	-; max 256
`blockedIps`	`array`	-	-; max 256
`credentialId`	`string`	`""`	-
`events`	`array`	`[]`	-
`resourceId`	`string`	`""`	-
`testPayload`	`string`	`""`	-

Configuration help

events Events: An empty selection accepts all events. Register the webhook in the provider with the same event selection.
testPayload Test payload (JSON): Normalized event: provider, event, resourceId and payload. Leave empty to use an example.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "credentialId": "",
  "events": [],
  "resourceId": "",
  "testPayload": ""
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.