Provider integrations

Connect Jira Cloud to FastHook

Connect one Atlassian account, select one or more Jira Cloud sites, and route issue, comment, sprint, version, and issue-property events to any FastHook Destination. Choose a focused Source, combine event types with Custom Webhook Events, or receive every supported event.

Create a Jira Provider Source

  1. Open Sources → New source → Provider app → Jira.
  2. Connect Atlassian and approve read access plus managed dynamic webhooks.
  3. Select the Jira sites that should deliver events.
  4. Optionally add a JQL filter for issue, comment, and issue-property events, then save.

Connect Jira Cloud to FastHook →

Supported events

  • Issue created, updated, deleted, and issue-property changes.
  • Comment created, updated, and deleted.
  • Sprint created, updated, started, closed, and deleted.
  • Version created, updated, moved, merged, released, unreleased, and deleted.
  • Any Jira Event and multi-select Custom Webhook Events Sources.

Supported Actions

  • Create Issue — choose a site, project, and issue type, then map the summary, description, and additional fields.
  • Update Issue — update an issue by key with a Jira fields object.
  • Add Comment — add a plain-text comment; FastHook converts it to Atlassian Document Format.
  • Transition Issue — select one of the transitions currently available for the issue.
  • Assign Issue — assign an issue to a Jira user or explicitly leave it unassigned.
  • Custom API Request — call another Jira Cloud REST API v3 path on the selected site.

Default Workflow mapping

Every Jira Trigger publishes an event-specific primary output before the first live run. Issue events use the issue summary, comment events use the comment text, sprint events use the sprint name, version events use the version name, and issue-property events use the property value. FastHook maps that primary output into compatible text fields on Actions from every provider, including title, summary, subject, name, description, body, content, comment, and message fields.

Jira-to-Jira Workflows also reuse issue.key, issue.fields.project.key, andissue.fields.issuetype.id when the selected Action accepts those resources. Site, transition, assignee, and arbitrary JSON fields remain explicit selections because guessing them could modify the wrong Jira resource.

Schema contracts

All 22 Triggers and all 6 Actions have versioned schema.json contracts. The contracts describe input requirements, output payloads, primary output paths, samples, and provenance from Atlassian's Jira Cloud OpenAPI definitions. The Workflow editor combines these contracts with the latest successful run, so optional Jira fields remain available for mapping even when one webhook payload is sparse.

Reliability and security

  • FastHook verifies Atlassian's short-lived HS256 webhook JWT before accepting the payload.
  • The exact payload is durably stored before acknowledgement and provider retries are deduplicated.
  • Rotating OAuth refresh tokens are encrypted and updated atomically.
  • Dynamic webhooks are automatically reconciled and refreshed before their 30-day expiration.
  • Sources with the same site and JQL share one managed webhook, conserving Jira's five-webhook per-user tenant limit.

Support, privacy, and terms