Search Issues with JQL with Jira API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Jira, HTTP / Webhook and 2,500+ other apps remarkably fast.

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Search Issues with JQL with the Jira API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Jira action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Search Issues with JQL action
1. Connect your Jira account
2. Select a Cloud ID
3. Configure JQL Query
4. Optional- Configure Max Results
5. Optional- Configure Fields
6. Optional- Select one or more Expand
7. Optional- Configure Properties
8. Optional- Configure Fields by Keys
9. Optional- Configure Fail Fast
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests (Payload Only) on HTTP / Webhook

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

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Search Issues with JQL on Jira

Description:Search for issues using JQL (Jira Query Language). [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get)

Version:0.0.1

Key:jira-search-issues-with-jql

View on GitHub

Jira Overview#

The Jira API opens up a world of possibilities for automating project management tasks, syncing with other tools, and enhancing data visibility. With Pipedream's integration, you can streamline issue tracking by automatically creating, updating, and searching for issues in Jira, as well as managing projects, sprints, users, and more. This integration not only saves time but also ensures real-time data flow across various platforms, keeping teams in sync and projects on track.

Action Code#

import jira from "../../jira.app.mjs";

export default {
  name: "Search Issues with JQL",
  description: "Search for issues using JQL (Jira Query Language). [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get)",
  key: "jira-search-issues-with-jql",
  version: "0.0.1",
  type: "action",
  props: {
    jira,
    cloudId: {
      propDefinition: [
        jira,
        "cloudId",
      ],
    },
    jql: {
      type: "string",
      label: "JQL Query",
      description: "The [JQL](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/) query to search for issues",
    },
    maxResults: {
      type: "integer",
      label: "Max Results",
      description: "Maximum number of issues to return (default: 50, max: 100)",
      optional: true,
      default: 50,
      min: 1,
      max: 100,
    },
    fields: {
      type: "string",
      label: "Fields",
      description: "Comma-separated list of fields to return for each issue",
      default: "*all",
      optional: true,
    },
    expand: {
      type: "string[]",
      label: "Expand",
      description: "Use expand to include additional information about the issues in the response",
      optional: true,
      options: [
        {
          label: "Returns field values rendered in HTML format",
          value: "renderedFields",
        },
        {
          label: "Returns the display name of each field",
          value: "names",
        },
        {
          label: "Returns the schema describing a field type",
          value: "schema",
        },
        {
          label: "Returns all possible transitions for the issue",
          value: "transitions",
        },
        {
          label: "Returns information about how each field can be edited",
          value: "editmeta",
        },
        {
          label: "Returns a list of recent updates to an issue, sorted by date, starting from the most recent",
          value: "changelog",
        },
        {
          label: "Returns a JSON array for each version of a field's value, with the highest number representing the most recent version",
          value: "versionedRepresentations",
        },
      ],
    },
    properties: {
      type: "string",
      label: "Properties",
      description: "A list of up to 5 issue properties to include in the results. This parameter accepts a comma-separated list.",
      optional: true,
    },
    fieldsByKeys: {
      type: "boolean",
      label: "Fields by Keys",
      description: "Reference fields by their key (rather than ID). The default is `false`.",
      optional: true,
    },
    failFast: {
      type: "boolean",
      label: "Fail Fast",
      description: "Fail this request early if we can't retrieve all field data",
      optional: true,
    },
  },
  methods: {
    searchIssues(args = {}) {
      return this.jira._makeRequest({
        path: "/search/jql",
        ...args,
      });
    },
  },
  async run({ $ }) {
    try {
      const response = await this.searchIssues({
        $,
        cloudId: this.cloudId,
        params: {
          jql: this.jql,
          maxResults: this.maxResults,
          fields: this.fields,
          expand: this.expand
            ? this.expand.join(",")
            : undefined,
          properties: this.properties,
          fieldsByKeys: this.fieldsByKeys,
          failFast: this.failFast,
        },
      });
      $.export("$summary", `Successfully retrieved ${response.issues.length} issues`);
      return response;
    } catch (error) {
      throw new Error(`Failed to search issues: ${error.message}`);
    }
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Jira	`jira`	`app`	This component uses the Jira app.
Cloud ID	`cloudId`	`string`	Select a value from the drop down menu.
JQL Query	`jql`	`string`	The JQL query to search for issues
Max Results	`maxResults`	`integer`	Maximum number of issues to return (default: 50, max: 100)
Fields	`fields`	`string`	Comma-separated list of fields to return for each issue
Expand	`expand`	`string[]`	Select a value from the drop down menu:`{ "label": "Returns field values rendered in HTML format", "value": "renderedFields" }{ "label": "Returns the display name of each field", "value": "names" }{ "label": "Returns the schema describing a field type", "value": "schema" }{ "label": "Returns all possible transitions for the issue", "value": "transitions" }{ "label": "Returns information about how each field can be edited", "value": "editmeta" }{ "label": "Returns a list of recent updates to an issue, sorted by date, starting from the most recent", "value": "changelog" }{ "label": "Returns a JSON array for each version of a field's value, with the highest number representing the most recent version", "value": "versionedRepresentations" }`
Properties	`properties`	`string`	A list of up to 5 issue properties to include in the results. This parameter accepts a comma-separated list.
Fields by Keys	`fieldsByKeys`	`boolean`	Reference fields by their key (rather than ID). The default is `false`.
Fail Fast	`failFast`	`boolean`	Fail this request early if we can't retrieve all field data

Action Authentication#

Jira uses OAuth authentication. When you connect your Jira account, Pipedream will open a popup window where you can sign into Jira and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Jira API.

Pipedream requests the following authorization scopes when you connect your account:

read:jira-workmanage:jira-projectread:jira-userwrite:jira-workmanage:jira-data-providerread:meoffline_accessread:issue-details:jiraread:board-scope:jira-softwareread:webhook:jirawrite:webhook:jiraread:field:jiraread:project:jiradelete:webhook:jirawrite:board-scope:jira-softwareread:board-scope.admin:jira-softwareread:sprint:jira-softwarewrite:sprint:jira-softwareread:field.option:jirawrite:field.option:jiraread:custom-field-contextual-configuration:jira write:custom-field-contextual-configuration:jiramanage:jira-configurationread:jql:jira

About Jira#

Jira is the #1 agile project management tool used by teams to plan, track, release, and support great software with confidence

More Ways to Connect Jira + HTTP / Webhook#

Other Popular Integrations#

Send any HTTP Request with HTTP / Webhook API on New Event from Jira API

Jira + HTTP / Webhook