Create Request with Jira Service Desk API on New Item in Feed from RSS API

Pipedream makes it easy to connect APIs for Jira Service Desk, RSS and 2,000+ other apps remarkably fast.

Trigger workflow on

New Item in Feed from the RSS API

Next, do this

Create Request with the Jira Service Desk API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Item in Feed trigger
1. Connect your RSS account
2. Configure timer
3. Configure Feed URL
4. Configure Published After
Configure the Create Request action
1. Connect your Jira Service Desk account
2. Select a Cloud ID
3. Select a Service Desk ID
4. Select a Request Type ID
5. Optional- Configure Request Participants
6. Optional- Configure Raise On Behalf Of
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 Item in Feed on RSS

Description:Emit new items from an RSS feed

Version:1.2.6

Key:rss-new-item-in-feed

View on GitHub

RSS Overview#

The RSS app allows users to automatically fetch and parse updates from web feeds. This functionality is pivotal for staying abreast of content changes or updates from websites, blogs, and news outlets that offer RSS feeds. With Pipedream, you can harness the RSS API to trigger workflows that enable a broad range of automations, like content aggregation, monitoring for specific keywords, notifications, and data synchronization across platforms.

Trigger Code#

import rss from "../../app/rss.app.mjs";
import { defineSource } from "@pipedream/types";
import rssCommon from "../common/common.mjs";
export default defineSource({
    ...rssCommon,
    key: "rss-new-item-in-feed",
    name: "New Item in Feed",
    description: "Emit new items from an RSS feed",
    version: "1.2.6",
    type: "source",
    dedupe: "unique",
    props: {
        ...rssCommon.props,
        url: {
            propDefinition: [
                rss,
                "url",
            ],
        },
        publishedAfter: {
            type: "string",
            label: "Published After",
            description: "Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`",
            default: new Date(Date.now() - 24 * 60 * 60 * 1000).toISOString(), // default to one day ago
        },
    },
    hooks: {
        async activate() {
            // Try to parse the feed one time to confirm we can fetch and parse.
            // The code will throw any errors to the user.
            await this.rss.fetchAndParseFeed(this.url);
        },
    },
    methods: {
        ...rssCommon.methods,
        generateMeta: function (item) {
            return {
                id: this.rss.itemKey(item),
                summary: item.title,
                ts: Date.now(),
            };
        },
    },
    async run() {
        const items = await this.rss.fetchAndParseFeed(this.url);
        for (const item of items.reverse()) {
            const publishedAfter = +new Date(this.publishedAfter);
            const ts = this.rss.itemTs(item);
            if (Number.isNaN(publishedAfter) || publishedAfter > ts) {
                continue;
            }
            const meta = this.generateMeta(item);
            this.$emit(item, meta);
        }
    },
});

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
RSS	`rss`	`app`	This component uses the RSS app.
	`timer`	`$.interface.timer`	How often you want to poll the feed for new items
Feed URL	`url`	`string`	Enter the URL for any public RSS feed
Published After	`publishedAfter`	`string`	Emit items published after the specified date in ISO 8601 format .e.g `2022-12-07T12:57:10+07:00`

Trigger Authentication#

The RSS API does not require authentication.

About RSS#

Real Simple Syndication

Action#

Create Request on Jira Service Desk

Description:Creates a new customer request. [See the documentation](https://docs.atlassian.com/jira-servicedesk/REST/3.6.2/#servicedeskapi/request-createCustomerRequest)

Version:0.1.0

Key:jira_service_desk-create-request

View on GitHub

Jira Service Desk Overview#

The Jira Service Desk API allows you to interact programmatically with your support ticket system, enabling the creation, updating, and management of tickets, customers, and service desk configurations. With Pipedream's integration, you can automate workflows by connecting Jira Service Desk to hundreds of other apps, listen to webhooks for real-time triggers, and execute custom logic.

Action Code#

import jiraServiceDesk from "../../jira_service_desk.app.mjs";

export default {
  key: "jira_service_desk-create-request",
  name: "Create Request",
  description:
    "Creates a new customer request. [See the documentation](https://docs.atlassian.com/jira-servicedesk/REST/3.6.2/#servicedeskapi/request-createCustomerRequest)",
  version: "0.1.0",
  type: "action",
  props: {
    jiraServiceDesk,
    cloudId: {
      propDefinition: [
        jiraServiceDesk,
        "cloudId",
      ],
    },
    serviceDeskId: {
      propDefinition: [
        jiraServiceDesk,
        "serviceDeskId",
        ({ cloudId }) => ({
          cloudId,
        }),
      ],
    },
    requestTypeId: {
      propDefinition: [
        jiraServiceDesk,
        "requestTypeId",
        ({
          cloudId, serviceDeskId,
        }) => ({
          cloudId,
          serviceDeskId,
        }),
      ],
      reloadProps: true,
    },
    requestParticipants: {
      type: "string[]",
      label: "Request Participants",
      description:
        "Not available to users who only have the Service Desk Customer permission or if the feature is turned off for customers..",
      optional: true,
    },
    raiseOnBehalfOf: {
      type: "string",
      label: "Raise On Behalf Of",
      description:
        "Not available to users who only have the Service Desk Customer permission.",
      optional: true,
    },
  },
  async additionalProps() {
    const {
      cloudId, serviceDeskId, requestTypeId,
    } = this;
    const types = await this.jiraServiceDesk.getRequestTypeFields({
      cloudId,
      serviceDeskId,
      requestTypeId,
    });

    return Object.fromEntries(
      types.map((field) => [
        field.fieldId,
        {
          type: "string",
          label: `Field: "${field.name}"`,
          description: `[See the documentation](https://docs.atlassian.com/jira-servicedesk/REST/3.6.2/#fieldformats) for info on specific fields. If the provided value is not a string, it will be parsed as JSON.${field.description
            ? `
\\
Field description: "${field.description}"`
            : ""}${field.jiraSchema
            ? `
  \\
  Field schema: \`${JSON.stringify(field.jiraSchema)}\``
            : ""}`,
          optional: !field.required,
        },
      ]),
    );
  },
  async run({ $ }) {
    const {
      // eslint-disable-next-line no-unused-vars
      jiraServiceDesk,
      cloudId,
      serviceDeskId,
      requestTypeId,
      requestParticipants,
      raiseOnBehalfOf,
      ...requestFieldValues
    } = this;

    Object.entries(requestFieldValues).forEach(([
      key,
      value,
    ]) => {
      try {
        const parsedValue = JSON.parse(value);
        requestFieldValues[key] = parsedValue;
      }
      catch (err) {
        // ignore non-serializable values
      }
    });

    const response = await this.jiraServiceDesk.createCustomerRequest({
      $,
      cloudId,
      data: {
        serviceDeskId,
        requestTypeId,
        requestFieldValues,
        requestParticipants,
        raiseOnBehalfOf,
      },
    });
    $.export("$summary", "Successfully created request");
    return response;
  },
};

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 Service Desk	`jiraServiceDesk`	`app`	This component uses the Jira Service Desk app.
Cloud ID	`cloudId`	`string`	Select a value from the drop down menu.
Service Desk ID	`serviceDeskId`	`string`	Select a value from the drop down menu.
Request Type ID	`requestTypeId`	`string`	Select a value from the drop down menu.
Request Participants	`requestParticipants`	`string[]`	Not available to users who only have the Service Desk Customer permission or if the feature is turned off for customers..
Raise On Behalf Of	`raiseOnBehalfOf`	`string`	Not available to users who only have the Service Desk Customer permission.

Action Authentication#

Jira Service Desk uses OAuth authentication. When you connect your Jira Service Desk account, Pipedream will open a popup window where you can sign into Jira Service Desk 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 Service Desk API.

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

read:servicedesk-requestmanage:servicedesk-customerwrite:servicedesk-requestread:jira:userread:jira-workread:organization:jira-service-managementread:meoffline_access