AppsPricingBlogTry it
Jira logo
HTTP / Webhook logo

Connect Jira to HTTP / Webhook

Use 4 documented Jira triggers to run 7 documented HTTP / Webhook actions.

4 source triggers
7 target actions
Reverse direction supported

Why Connect Jira & HTTP / Webhook?

Start with a Jira event

Choose from 4 documented triggers, including New Event, New Issue Created Event (Instant), New Issue Deleted Event (Instant).

Run a HTTP / Webhook action

Send the event into one of 7 documented actions, such as Send any HTTP Request, Send GET Request, Send POST Request.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Jira logo

Jira

Triggers (4)

New Event

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

webhook
New Issue Created Event (Instant)

Emit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Deleted Event (Instant)

Emit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook
New Issue Updated Event (Instant)

Emit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please use New Event source and select multiple events.

webhook

Actions (24)

Add Attachment To Issue

Adds an attachment to an issue. See the documentation

Add Comment To Issue

Adds a new comment to an issue. See the documentation

Add Multiple Attachments To Issue

Adds multiple attachments to an issue. See the documentation

Add Watcher To Issue

Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

Assign Issue

Assigns an issue to a user. See the documentation

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

Count Issues Using JQL

Provide an estimated count of the issues that match the JQL. See the documentation

Create Custom Field Options (Context)

Create a context for custom field options. See the documentation.

Create Future Sprint

Creates a future sprint. See the documentation

Create Issue

Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

Create Jira Version in Project

Creates a project version. See the documentation

Delete Project

Deletes a project. See the documentation

Get All Projects

Gets metadata on all projects. See the documentation

Get Board

Returns the board for the given board ID. See the documentation

Get Cloud ID

Gets the cloud ID and details of all accessible Jira Cloud sites. See the documentation

Get Current User

Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with **Search Issues with JQL** (e.g. assignee = '{accountId}') or **Assign Issue**. Requires a Cloud ID to identify the Jira site. See the documentation.

Get Issue

Gets the details for an issue. See the documentation

Get Issue Picker Suggestions

Returns lists of issues matching a query string. See the documentation

Get Issue Types

Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

Get Sprint

Returns the sprint for a given sprint ID. See the documentation

Get Task

Gets the status of a long-running asynchronous task. See the documentation

Get Transitions

Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

Get User

Gets details of user. See the documentation

Get Users

Gets the details for a list of users. See the documentation

HTTP / Webhook logo

HTTP / Webhook

Triggers (4)

New Requests

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

polling
New Requests (Payload Only)

Get a URL and emit the HTTP body as an event on every request

polling
New event when the content of the URL changes.

Emit new event when the content of the URL changes.

polling
New Webhook Request

Emit new event when an HTTP request is received at the webhook URL. Use as a trigger to run workflows from external services (GitHub, Stripe, n8n, etc.). Configure response code, body, and which HTTP methods to accept.

webhook

Actions (7)

Send any HTTP Request

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

Send GET Request

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Send POST Request

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

Send PUT Request

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

Return HTTP Response

Use with an HTTP trigger that uses "Return a custom response from your workflow" as its HTTP Response

Validate Webhook Auth

Require authorization for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Verify HMAC Signature

Validate HMAC signature for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Integration Features

4 documented Jira triggers
7 documented HTTP / Webhook actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported HTTP / Webhook to Jira direction

Capability Examples

Jira trigger → HTTP / Webhook action

Catalog example
JiraJira

New Event

HTTP / WebhookHTTP / Webhook

Send any HTTP Request

HTTP / Webhook trigger → Jira action

Reverse direction
HTTP / WebhookHTTP / Webhook

New Requests

JiraJira

Add Attachment To Issue

How It Works

1

Connect Apps

Authenticate your Jira and HTTP / Webhook accounts

2

Choose a Trigger

Select a documented Jira event

3

Choose an Action

Select the documented HTTP / Webhook operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 4 documented Jira triggers.

Automated Actions

Run one of 7 documented HTTP / Webhook actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

HTTP / Webhook logoJira logo

Reverse Integration Available

Also connect HTTP / Webhook to Jira for bidirectional automation

View Integration
Jira logo

All Jira Integrations

Explore all available Jira connections

View All Integrations
HTTP / Webhook logo

All HTTP / Webhook Integrations

Explore all available HTTP / Webhook connections

View All Integrations

Ready to Connect Jira & HTTP / Webhook?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free