Get Issue with Jira API on New Custom Webhook Events from Stripe API

Pipedream makes it easy to connect APIs for Jira, Stripe and 2,900+ other apps remarkably fast.

Trigger workflow on

New Custom Webhook Events from the Stripe API

Next, do this

Get 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 Stripe 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 Custom Webhook Events trigger
1. Connect your Stripe account
2. Select one or more Events
Configure the Get Issue action
1. Connect your Jira account
2. Select a Cloud ID
3. Select a Issue ID or Key
4. Optional- Configure Fields
5. Optional- Configure Fields By Keys
6. Optional- Configure Properties
7. Optional- Configure Update History
8. Optional- Configure Expand
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 Custom Webhook Events on Stripe

Description:Emit new event on each webhook event

Version:0.1.4

Key:stripe-custom-webhook-events

View on GitHub

Stripe Overview#

The Stripe API is a powerful tool for managing online payments, subscriptions, and invoices. With Pipedream, you can leverage this API to automate payment processing, monitor transactions, and sync billing data with other services. Pipedream's no-code platform allows for quick integration and creation of serverless workflows that react to Stripe events in real-time. For instance, you might automatically update customer records, send personalized emails after successful payments, or escalate failed transactions to your support team.

Trigger Code#

import constants from "../common/constants.mjs";
import sampleEmit from "./test-event.mjs";
import common from "../common/webhook-base.mjs";

export default {
  ...common,
  key: "stripe-custom-webhook-events",
  name: "New Custom Webhook Events",
  type: "source",
  version: "0.1.4",
  description: "Emit new event on each webhook event",
  props: {
    ...common.props,
    enabledEvents: {
      type: "string[]",
      label: "Events",
      description: "Events to listen for. Select `*` for all events",
      options: constants.WEBHOOK_EVENTS,
      default: [
        "*",
      ],
    },
  },
  methods: {
    ...common.methods,
    getEvents() {
      return this.enabledEvents;
    },
  },
  sampleEmit,
};

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
Stripe	`app`	`app`	This component uses the Stripe app.
N/A	`http`	`$.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.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Events	`enabledEvents`	`string[]`	Select a value from the drop down menu:`*account.application.authorizedaccount.application.deauthorizedaccount.external_account.createdaccount.external_account.deletedaccount.external_account.updatedaccount.updatedapplication_fee.createdapplication_fee.refund.updatedapplication_fee.refundedbalance.availablebilling_portal.configuration.createdbilling_portal.configuration.updatedbilling_portal.session.createdbilling.alert.triggeredbilling.credit_balance_transaction.createdbilling.credit_grant.createdbilling.credit_grant.updatedbilling.meter.createdbilling.meter.deactivatedbilling.meter.reactivatedbilling.meter.updatedcapability.updatedcash_balance.funds_availablecharge.capturedcharge.dispute.closedcharge.dispute.createdcharge.dispute.funds_reinstatedcharge.dispute.funds_withdrawncharge.dispute.updatedcharge.expiredcharge.failedcharge.pendingcharge.refund.updatedcharge.refundedcharge.succeededcharge.updatedcheckout.session.async_payment_failedcheckout.session.async_payment_succeededcheckout.session.completedcheckout.session.expiredclimate.order.canceledclimate.order.createdclimate.order.delayedclimate.order.deliveredclimate.order.product_substitutedclimate.product.createdclimate.product.pricing_updatedcoupon.createdcoupon.deletedcoupon.updatedcredit_note.createdcredit_note.updatedcredit_note.voidedcustomer_cash_balance_transaction.createdcustomer.createdcustomer.deletedcustomer.discount.createdcustomer.discount.deletedcustomer.discount.updatedcustomer.source.createdcustomer.source.deletedcustomer.source.expiringcustomer.source.updatedcustomer.subscription.createdcustomer.subscription.deletedcustomer.subscription.pausedcustomer.subscription.pending_update_appliedcustomer.subscription.pending_update_expiredcustomer.subscription.resumedcustomer.subscription.trial_will_endcustomer.subscription.updatedcustomer.tax_id.createdcustomer.tax_id.deletedcustomer.tax_id.updatedcustomer.updatedentitlements.active_entitlement_summary.updatedfile.createdfinancial_connections.account.createdfinancial_connections.account.deactivatedfinancial_connections.account.disconnectedfinancial_connections.account.reactivatedfinancial_connections.account.refreshed_balancefinancial_connections.account.refreshed_ownershipfinancial_connections.account.refreshed_transactionsidentity.verification_session.canceledidentity.verification_session.createdidentity.verification_session.processingidentity.verification_session.redactedidentity.verification_session.requires_inputidentity.verification_session.verifiedinvoice_payment.paidinvoice.createdinvoice.deletedinvoice.finalization_failedinvoice.finalizedinvoice.marked_uncollectibleinvoice.overdueinvoice.overpaidinvoice.paidinvoice.payment_action_requiredinvoice.payment_failedinvoice.payment_succeededinvoice.sentinvoice.upcominginvoice.updatedinvoice.voidedinvoice.will_be_dueinvoiceitem.createdinvoiceitem.deletedissuing_authorization.createdissuing_authorization.requestissuing_authorization.updatedissuing_card.createdissuing_card.updatedissuing_cardholder.createdissuing_cardholder.updatedissuing_dispute.closedissuing_dispute.createdissuing_dispute.funds_reinstatedissuing_dispute.funds_rescindedissuing_dispute.submittedissuing_dispute.updatedissuing_personalization_design.activatedissuing_personalization_design.deactivatedissuing_personalization_design.rejectedissuing_personalization_design.updatedissuing_token.createdissuing_token.updatedissuing_transaction.createdissuing_transaction.purchase_details_receipt_updatedissuing_transaction.updatedmandate.updatedpayment_intent.amount_capturable_updatedpayment_intent.canceledpayment_intent.createdpayment_intent.partially_fundedpayment_intent.payment_failedpayment_intent.processingpayment_intent.requires_actionpayment_intent.succeededpayment_link.createdpayment_link.updatedpayment_method.attachedpayment_method.automatically_updatedpayment_method.detachedpayment_method.updatedpayout.canceledpayout.createdpayout.failedpayout.paidpayout.reconciliation_completedpayout.updatedperson.createdperson.deletedperson.updatedplan.createdplan.deletedplan.updatedprice.createdprice.deletedprice.updatedproduct.createdproduct.deletedproduct.updatedpromotion_code.createdpromotion_code.updatedquote.acceptedquote.canceledquote.createdquote.finalizedquote.will_expireradar.early_fraud_warning.createdradar.early_fraud_warning.updatedrefund.createdrefund.failedrefund.updatedreporting.report_run.failedreporting.report_run.succeededreporting.report_type.updatedreview.closedreview.openedsetup_intent.canceledsetup_intent.createdsetup_intent.requires_actionsetup_intent.setup_failedsetup_intent.succeededsigma.scheduled_query_run.createdsource.canceledsource.chargeablesource.failedsource.mandate_notificationsource.refund_attributes_requiredsource.transaction.createdsource.transaction.updatedsubscription_schedule.abortedsubscription_schedule.canceledsubscription_schedule.completedsubscription_schedule.createdsubscription_schedule.expiringsubscription_schedule.releasedsubscription_schedule.updatedtax_rate.createdtax_rate.updatedtax.settings.updatedterminal.reader.action_failedterminal.reader.action_succeededterminal.reader.action_updatedtest_helpers.test_clock.advancingtest_helpers.test_clock.createdtest_helpers.test_clock.deletedtest_helpers.test_clock.internal_failuretest_helpers.test_clock.readytopup.canceledtopup.createdtopup.failedtopup.reversedtopup.succeededtransfer.createdtransfer.reversedtransfer.updated`

Trigger Authentication#

Stripe uses API keys for authentication. When you connect your Stripe account, Pipedream securely stores the keys so you can easily authenticate to Stripe APIs in both code and no-code steps.

About Stripe#

Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes.

Action#

Get Issue on Jira

Description:Gets the details for an issue. [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get)

Version:0.1.16

Key:jira-get-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 jira from "../../jira.app.mjs";

export default {
  key: "jira-get-issue",
  name: "Get Issue",
  description: "Gets the details for an issue. [See the documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get)",
  version: "0.1.16",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    jira,
    cloudId: {
      propDefinition: [
        jira,
        "cloudId",
      ],
    },
    issueIdOrKey: {
      propDefinition: [
        jira,
        "issueIdOrKey",
        (c) => ({
          cloudId: c.cloudId,
        }),
      ],
    },
    fields: {
      type: "string",
      label: "Fields",
      description: "A list of fields to return for the issue. This parameter accepts a comma-separated list. Use it to retrieve a subset of fields.  All fields are returned by default. Allowed values:\n`*all` Returns all fields.\n`*navigable` Returns navigable fields.\nAny issue field, prefixed with a minus to exclude, as in `-description `.",
      optional: true,
    },
    fieldsByKeys: {
      type: "boolean",
      label: "Fields By Keys",
      description: "Whether `fields` in fields are referenced by keys rather than IDs. This parameter is useful where fields have been added by a connect app and a field's key may differ from its ID.",
      optional: true,
    },
    properties: {
      propDefinition: [
        jira,
        "properties",
      ],
      description: "A list of issue properties to return for the issue. This parameter accepts a comma-separated list. Allowed values:\n`*all` Returns all issue properties.\nAny issue property key, prefixed with a minus to exclude.",
    },
    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,
    },
    expand: {
      propDefinition: [
        jira,
        "expand",
      ],
      description: "Use expand to include additional information about the issues in the response. This parameter accepts a comma-separated list. Expand options include:\n`renderedFields` Returns field values rendered in HTML format.\n`names` Returns the display name of each field.\n`schema` Returns the schema describing a field type.\n`transitions` Returns all possible transitions for the issue.\n`editmeta` Returns information about how each field can be edited.\n`changelog` Returns a list of recent updates to an issue, sorted by date, starting from the most recent.\n`versionedRepresentations` Returns a JSON array for each version of a field's value, with the highest number representing the most recent version. Note: When included in the request, the fields parameter is ignored.",
    },
  },
  async run({ $ }) {
    let properties;
    try {
      properties = JSON.parse(this.properties);
    } catch (err) {
      //pass
    }
    const response = await this.jira.getIssue({
      $,
      cloudId: this.cloudId,
      issueIdOrKey: this.issueIdOrKey,
      params: {
        fields: this.fields,
        fieldsByKeys: this.fieldsByKeys,
        properties,
        updateHistory: this.updateHistory,
        expand: this.expand,
      },
    });
    $.export("$summary", `Successfully retrieved issue with ID(or key): ${this.issueIdOrKey}`);
    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	`jira`	`app`	This component uses the Jira app.
Cloud ID	`cloudId`	`string`	Select a value from the drop down menu.
Issue ID or Key	`issueIdOrKey`	`string`	Select a value from the drop down menu.
Fields	`fields`	`string`	A list of fields to return for the issue. This parameter accepts a comma-separated list. Use it to retrieve a subset of fields. All fields are returned by default. Allowed values: `all` Returns all fields. `navigable` Returns navigable fields. Any issue field, prefixed with a minus to exclude, as in `-description` .
Fields By Keys	`fieldsByKeys`	`boolean`	Whether `fields` in fields are referenced by keys rather than IDs. This parameter is useful where fields have been added by a connect app and a field's key may differ from its ID.
Properties	`properties`	`string`	A list of issue properties to return for the issue. This parameter accepts a comma-separated list. Allowed values: `*all` Returns all issue properties. Any issue property key, prefixed with a minus to exclude.
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
Expand	`expand`	`string`	Use expand to include additional information about the issues in the response. This parameter accepts a comma-separated list. Expand options include: `renderedFields` Returns field values rendered in HTML format. `names` Returns the display name of each field. `schema` Returns the schema describing a field type. `transitions` Returns all possible transitions for the issue. `editmeta` Returns information about how each field can be edited. `changelog` Returns a list of recent updates to an issue, sorted by date, starting from the most recent. `versionedRepresentations` Returns a JSON array for each version of a field's value, with the highest number representing the most recent version. Note: When included in the request, the fields parameter is ignored.

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

Get Issue with Jira API on New Custom Webhook Events from Stripe API

Pipedream makes it easy to connect APIs for Jira, Stripe and 2,900+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,900+apps by most popular

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