Create Issue with Jira API on New Shared Drive from Google Drive API

Pipedream makes it easy to connect APIs for Jira, Google Drive and 2,200+ other apps remarkably fast.

Trigger workflow on

New Shared Drive from the Google Drive API

Next, do this

Create Issue 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 Google Drive 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 Shared Drive trigger
1. Connect your Google Drive account
2. Configure Polling interval
Configure the Create Issue action
1. Connect your Jira account
2. Select a Cloud ID
3. Optional- Configure History Metadata
4. Optional- Configure Properties
5. Optional- Configure Update
6. Optional- Configure Additional properties
7. Optional- Configure Update history
8. Select a Project ID
9. Select a Issue Type
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 Shared Drive on Google Drive

Description:Emits a new event any time a shared drive is created.

Version:0.1.7

Key:google_drive-new-shared-drive

View on GitHub

Google Drive Overview#

The Google Drive API on Pipedream allows you to automate various file management tasks, such as creating, reading, updating, and deleting files within your Google Drive. You can also share files, manage permissions, and monitor changes to files and folders. This opens up possibilities for creating workflows that seamlessly integrate with other apps and services, streamlining document handling, backup processes, and collaborative workflows.

Trigger Code#

import googleDrive from "../../google_drive.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "google_drive-new-shared-drive",
  name: "New Shared Drive",
  description: "Emits a new event any time a shared drive is created.",
  version: "0.1.7",
  type: "source",
  dedupe: "unique",
  props: {
    googleDrive,
    db: "$.service.db",
    timer: {
      label: "Polling interval",
      description: "Interval to poll the Google Drive API for new shared drives",
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  hooks: {
    async deploy() {
      const { drives: initDrives } = await this.googleDrive.listDrivesInPage();
      for (const drive of initDrives) {
        const newDrive = await this.googleDrive.getDrive(drive.id);
        const meta = this.generateMeta(newDrive);
        this.$emit(newDrive, meta);
      }

      this._setKnownDrives(initDrives.map((drive) => drive.id));
    },
  },
  methods: {
    _getKnownDrives() {
      return this.db.get("driveIds");
    },
    _setKnownDrives(driveIds) {
      this.db.set("driveIds", Array.from(driveIds));
    },
    generateMeta(drive) {
      const ts = new Date(drive.createdTime).getTime();
      return {
        id: drive.id,
        summary: drive.name,
        ts,
      };
    },
  },
  async run() {
    const knownDrives = new Set(this._getKnownDrives());
    const drivesStream = this.googleDrive.listDrives();
    for await (const drive of drivesStream) {
      if (knownDrives.has(drive.id)) {
        // We've already seen this drive, so we skip it
        continue;
      }

      knownDrives.add(drive.id);

      const newDrive = await this.googleDrive.getDrive(drive.id);
      const meta = this.generateMeta(newDrive);
      this.$emit(newDrive, meta);
    }

    this._setKnownDrives(knownDrives);
  },
};

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
Google Drive	`googleDrive`	`app`	This component uses the Google Drive app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling interval	`timer`	`$.interface.timer`	Interval to poll the Google Drive API for new shared drives

Trigger Authentication#

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

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

https://www.googleapis.com/auth/drive

About Google Drive#

Google Drive is a file storage and synchronization service which allows you to create and share your work online, and access your documents from anywhere.

Action#

Create Issue on Jira

Description:Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask, [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-post)

Version:0.1.19

Key:jira-create-issue

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 constants from "../../common/constants.mjs";
import utils from "../../common/utils.mjs";
import common from "../common/issue.mjs";

export default {
  ...common,
  key: "jira-create-issue",
  name: "Create Issue",
  description: "Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask, [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-post)",
  version: "0.1.19",
  type: "action",
  props: {
    ...common.props,
    updateHistory: {
      type: "boolean",
      label: "Update history",
      description: "Whether the project in which the issue is created is added to the user's **Recently viewed** project list, as shown under **Projects** in Jira.",
      optional: true,
    },
    projectId: {
      propDefinition: [
        common.props.app,
        "projectID",
        ({ cloudId }) => ({
          cloudId,
        }),
      ],
    },
    issueTypeId: {
      reloadProps: true,
      propDefinition: [
        common.props.app,
        "issueType",
        ({
          cloudId, projectId,
        }) => ({
          cloudId,
          projectId,
        }),
      ],
    },
  },
  async additionalProps() {
    const {
      cloudId,
      projectId,
      issueTypeId,
    } = this;

    const {
      projects: [
        {
          issuetypes: [
            { fields = {} } = {},
          ],
        },
      ],
    } = await this.app.getCreateIssueMetadata({
      cloudId,
      params: {
        projectIds: projectId,
        issuetypeIds: issueTypeId,
        expand: "projects.issuetypes.fields",
      },
    });

    const keys = [
      constants.FIELD_KEY.ISSUETYPE,
      constants.FIELD_KEY.PROJECT,
    ];

    return this.getDynamicFields({
      fields,
      predicate: ({ key }) => !keys.includes(key),
    });
  },
  async run({ $ }) {
    const {
      // eslint-disable-next-line no-unused-vars
      app,
      cloudId,
      projectId,
      issueTypeId,
      updateHistory,
      historyMetadata,
      properties,
      update,
      additionalProperties,
      ...dynamicFields
    } = this;

    const fields = utils.reduceProperties({
      initialProps: {
        project: {
          id: projectId,
        },
        issuetype: {
          id: issueTypeId,
        },
      },
      additionalProps: this.formatFields(dynamicFields),
    });

    const params = utils.reduceProperties({
      additionalProps: {
        updateHistory,
      },
    });

    const response = await this.app.createIssue({
      $,
      cloudId,
      params,
      data: {
        fields: {
          ...utils.parseObject(additionalProperties),
          ...fields,
        },
        historyMetadata: utils.parseObject(historyMetadata),
        properties: utils.parse(properties),
        update: utils.parseObject(update),
      },
    });

    $.export("$summary", `Issue has been created successfuly. (ID:${response.id}, KEY:${response.key})`);

    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	`app`	`app`	This component uses the Jira app.
Cloud ID	`cloudId`	`string`	Select a value from the drop down menu.
History Metadata	`historyMetadata`	`object`	Additional issue history details.
Properties	`properties`	`string`	Details of issue properties to be add or update, please provide an array of objects with keys and values.
Update	`update`	`object`	A Map containing the field name and a list of operations to perform on the issue screen field. Note that fields included in here cannot be included in `fields`.
Additional properties	`additionalProperties`	`object`	Extra properties of any type may be provided to this object.
Update history	`updateHistory`	`boolean`	Whether the project in which the issue is created is added to the user's Recently viewed project list, as shown under Projects in Jira.
Project ID	`projectId`	`string`	Select a value from the drop down menu.
Issue Type	`issueTypeId`	`string`	Select a value from the drop down menu.

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 + Google Drive#

Other Popular Integrations#

JIRA - Create Issue with Jira API on Changes to Specific Files from Google Drive API

Google Drive + Jira

Create Issue with Jira API on New Shared Drive from Google Drive API

Pipedream makes it easy to connect APIs for Jira, Google Drive and 2,200+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,200+apps by most popular

1
-
24
of
2,200+
apps by most popular