Jira webhook automations in Make.com

Using make.com with Jira webhooks lets you turn issue updates into powerful, automated workflows without custom code or complex infrastructure.

This how-to guide walks you through capturing Jira webhooks in a scenario, inspecting the raw payload, stabilizing your integrations, and turning every event into actionable data.

What are Jira webhooks in Make.com?

A Jira webhook is an HTTP callback that Jira sends when an event occurs, such as an issue being created, updated, transitioned, or commented on.

In make.com, these webhooks are received by a special trigger module. Each incoming request becomes a bundle of data you can map to other modules to automate your processes.

Jira sends JSON data when specified events occur.
make.com receives the webhook at a unique URL.
Each request is processed as a separate execution.
You can branch, filter, and transform data from the payload.

The official reference article this guide is based on is available at this Jira webhooks on make.com page.

Why use make.com for Jira webhooks?

Using Jira webhooks directly in make.com gives you a visual, low-code environment to handle events that would otherwise require scripting or additional middleware.

Key reasons teams connect Jira webhooks to make.com:

Instant reactions to issue changes.
No need to poll Jira for updates.
Visual mapping of JSON fields without code.
Flexible routing and filtering based on issue content.
Reusable scenarios you can adapt for multiple projects.

Prerequisites before you start

Before configuring Jira webhooks for make.com, confirm the following:

You have administrator access (or sufficient permissions) in your Jira instance.
You have a make.com account and can create scenarios.
You are allowed to configure webhooks or manage Jira system settings.

Once these conditions are met, you’re ready to connect Jira and make.com through webhooks.

Step 1: Create a webhook trigger in Make.com

The first step is to prepare a scenario in make.com that can receive webhook calls.

Log in to your make.com dashboard.
Create a new scenario.
Add a webhook trigger module. If the tutorial you follow uses a generic HTTP webhook, select the appropriate webhook module from the list.
Generate a new webhook URL. This is the unique endpoint Jira will call.
Leave the scenario in a state where it can listen for data (typically by running it once or using the built-in listening mode).

At this point, make.com is ready to receive a test webhook from Jira so that you can inspect the structure of the payload.

Step 2: Configure the Jira webhook to call Make.com

Next, set up the webhook in Jira and point it to the URL generated by make.com.

Sign in to Jira with an account that can manage system settings.
Navigate to the webhook configuration section in Jira administration.
Create a new webhook and give it a clear, descriptive name so you know it is connected to make.com.
Paste the webhook URL from make.com into the URL field.
Select the events to trigger the webhook, such as issue created, updated, or transitioned.
Optionally, define JQL filters to limit which issues will trigger the webhook.
Save the webhook configuration.

After saving, Jira will start sending HTTP requests to the make.com endpoint whenever the selected events occur.

Step 3: Send a test event from Jira

Now you need a sample payload so that you can map fields within make.com.

With the webhook enabled, perform an action in Jira that matches your configured event, such as creating a new issue.
Ensure your scenario in make.com is running or listening for a webhook.
Wait for the scenario to capture the webhook. You should see a new execution appear.

This first captured request is crucial because it shows the exact JSON structure of the data that Jira sends to make.com.

Step 4: Inspect and understand the webhook payload

Once the test event is triggered, inspect the data received inside make.com.

Open the scenario execution that received the webhook.
Click the webhook module to view the input data.
Expand the JSON structure to see the available fields, such as issue key, summary, description, statuses, and user information.
Note which paths correspond to the data you want to use in later modules.

This inspection step helps you understand what the webhook looks like in practice so you can map it reliably throughout your make.com workflow.

Step 5: Map webhook data to other modules in Make.com

With the payload structure understood, you can start using the data to power downstream actions in make.com.

Add the next module in your scenario, such as an email, a database operation, or a notification in another tool.
In the module’s configuration, use the data picker to select values from the webhook module, like issue key, project name, or assignee.
Map the fields to subject lines, message bodies, or record fields according to your process needs.
Save the scenario and run another test event from Jira.

By working this way, every Jira update that triggers the webhook can immediately create or update records in your connected systems through make.com.

Step 6: Add filters and routing for stable Make.com workflows

Real-world Jira systems often generate many webhook events, not all of which you need to process in the same way. Adding filters and routing in make.com helps keep your processes efficient and reliable.

Filters: Add filters after the webhook trigger to process only specific issues, such as those from a certain project, issue type, or status.
Routers: Use routers in make.com to branch the flow based on issue fields, so that different conditions result in different sets of actions.
Error handling: Configure error handling and retries so transient failures in downstream systems do not break the entire scenario.

These techniques align with the best practices described in the original Jira webhook guidance for make.com and help prevent noisy or unreliable automations.

Step 7: Test, log, and maintain your Jira–Make.com integration

Once basic automation is in place, continuous testing and monitoring keep it healthy.

Trigger multiple different Jira events (create, update, transition) and confirm the resulting executions in make.com behave as expected.
Inspect execution logs for failures or unexpected data.
Adjust filters, mappings, or Jira webhook settings if you see missing or extra events.
Document your scenario logic, especially which Jira projects and events are connected to which make.com workflows.

As your Jira configuration evolves, revisit your webhook and scenario setup to ensure it stays aligned with your current processes.

Advanced ideas for Jira webhooks in Make.com

Once you master the basics, you can use Jira webhooks with make.com to build more sophisticated automations, for example:

Syncing issue changes to CRM or help desk tools.
Creating audit logs or analytics dashboards when specific transitions occur.
Sending contextual alerts to chat platforms when high-priority issues appear.
Auto-assigning work or creating sub-tasks according to business rules.

Each of these ideas relies on the same core principles: capture the webhook, understand the payload, and orchestrate actions in make.com.

Further resources

For strategy, architecture, and automation help that goes beyond a single tool, you can visit Consultevo, which focuses on automation and integration solutions.

For the original reference content that inspired this how-to guide, see the official Jira webhooks article on make.com.

By combining Jira events with the visual power of make.com, you can create scalable, maintainable workflows that adapt as your projects grow.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help