Get Issue with Jira API on New Email Is Soft Bounced (Instant) from Mailersend API

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

Trigger workflow on

New Email Is Soft Bounced (Instant) from the Mailersend 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 Mailersend 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 Email Is Soft Bounced (Instant) trigger
1. Connect your Mailersend account
2. Select a Domain ID
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 Email Is Soft Bounced (Instant) on Mailersend

Description:Emit new event when your email is not delivered because it soft bounced. [See the documentation](https://developers.mailersend.com/api/v1/webhooks.html#webhooks-overview)

Version:0.0.1

Key:mailersend-email-is-soft-bounced

View on GitHub

Mailersend Overview#

The MailerSend API integrates with Pipedream to create powerful email automation workflows, enabling you to send transactional emails, create and manage templates, and track email activities like opens or clicks. With these capabilities, you can automate routine communications, personalize mass mailings based on user actions or data, and gain insights into your email campaign performances, all within the context of a serverless Pipedream workflow.

Trigger Code#

import common from "../common/webhook.mjs";
import { EmailWebhookEventType } from "mailersend";

export default {
  ...common,
  key: "mailersend-email-is-soft-bounced",
  name: "New Email Is Soft Bounced (Instant)",
  description: "Emit new event when your email is not delivered because it soft bounced. [See the documentation](https://developers.mailersend.com/api/v1/webhooks.html#webhooks-overview)",
  version: "0.0.1",
  dedupe: "unique",
  type: "source",
  methods: {
    ...common.methods,
    getEvents() {
      return [
        EmailWebhookEventType.SOFT_BOUNCED,
      ];
    },
  },
};

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
Mailersend	`app`	`app`	This component uses the Mailersend app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Domain ID	`domainId`	`string`	Select a value from the drop down menu.
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.

Trigger Authentication#

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

API tokens are generated for sending domains and can have different permissions to limit which areas of your account they may be used to access. See docs

About Mailersend#

Transactional email service that delivers

Action#

Get Issue on Jira

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

Version:0.1.11

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 docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get)",
  version: "0.1.11",
  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 Email Is Soft Bounced (Instant) from Mailersend API

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

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

Developers ♥ Pipedream

1-24of2,700+apps by most popular

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