Add Multiple Attachments To Issue with Jira API on Customer Created from Plain API

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

Trigger workflow on

Customer Created from the Plain API

Next, do this

Add Multiple Attachments To 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 Plain 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 Customer Created trigger
1. Connect your Plain account
Configure the Add Multiple Attachments To Issue action
1. Connect your Jira account
2. Select a Cloud ID
3. Select a Issue id or key
4. Configure File Paths or URLs
5. Optional- Configure syncDir
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#

Customer Created on Plain

Description:Emit new event when a customer is created.

Version:0.0.1

Key:plain-customer-created

View on GitHub

Plain Overview#

The Plain API provides functionality for automating customer support tasks, such as managing conversations, customers, and team inboxes. Within Pipedream, you can leverage these features to create custom workflows that respond to events from your app or external services, triggering actions in Plain. By integrating the Plain API with Pipedream, you can enhance customer support efficiency, streamline communication, and keep customer data synchronized across platforms.

Trigger Code#

import common from "../common/base-webhook.mjs"; import sampleEmit from "./test-event.mjs"; export default { ...common, key: "plain-customer-created", name: "Customer Created", description: "Emit new event when a customer is created.", version: "0.0.1", type: "source", dedupe: "unique", methods: { ...common.methods, getEventType() { return "customer.customer_created"; }, getSummary({ payload }) { return `Customer Created ID ${payload.customer.id}`; }, }, 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
Plain	`plain`	`app`	This component uses the Plain app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
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#

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

To get an API key, follow the following instructions: https://www.plain.com/docs/api-reference/graphql/authentication

About Plain#

Customer support for modern tools. Fast, flexible and extendable.

Action#

Add Multiple Attachments To Issue on Jira

Description:Adds multiple attachments to an issue, [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-issue-issueidorkey-attachments-post)

Version:1.0.5

Key:jira-add-multiple-attachments-to-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 { getFileStreamAndMetadata } from "@pipedream/platform"; import FormData from "form-data"; import jira from "../../jira.app.mjs"; export default { key: "jira-add-multiple-attachments-to-issue", name: "Add Multiple Attachments To Issue", description: "Adds multiple attachments to an issue, [See the docs](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-issue-issueidorkey-attachments-post)", version: "1.0.5", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { jira, cloudId: { propDefinition: [ jira, "cloudId", ], }, issueIdOrKey: { propDefinition: [ jira, "issueIdOrKey", (c) => ({ cloudId: c.cloudId, }), ], }, files: { type: "string[]", label: "File Paths or URLs", description: "Provide either an array of file URLs or paths to files in the /tmp directory (for example, /tmp/myFile.pdf).", }, syncDir: { type: "dir", accessMode: "read", sync: true, optional: true, }, }, async run({ $ }) { const responses = []; for (let i = 0; i < this.files.length; i++) { const file = this.files[i]; const data = new FormData(); const { stream, metadata, } = await getFileStreamAndMetadata(file); data.append("file", stream, { contentType: metadata.contentType, knownLength: metadata.size, filename: metadata.name, }); const headers = { "Content-Type": `multipart/form-data; boundary=${data._boundary}`, "X-Atlassian-Token": "no-check", }; const response = await this.jira.addAttachmentToIssue({ $, cloudId: this.cloudId, issueIdOrKey: this.issueIdOrKey, headers, data, }); responses.push(response); } $.export("$summary", `Attachment/s were added to the issue with ID (or key): ${this.issueIdOrKey}`); return responses; }, };

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.
File Paths or URLs	`files`	`string[]`	Provide either an array of file URLs or paths to files in the /tmp directory (for example, /tmp/myFile.pdf).
syncDir	`syncDir`	`dir`

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

Add Multiple Attachments To Issue with Jira API on Customer Created from Plain API

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

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

Developers ♥ Pipedream

1-24of2,800+apps by most popular

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