Create Issue with Jira API on Card Moved (Instant) from Trello API

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

Trigger workflow on

Card Moved (Instant) from the Trello 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 Trello 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 Card Moved (Instant) trigger
1. Connect your Trello account
2. Select a Board
3. Optional- Select one or more Lists
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#

Card Moved (Instant) on Trello

Description:Emit new event each time a card is moved to a list.

Version:0.1.3

Key:trello-card-moved

View on GitHub

Trello Overview#

Trello's API lets you craft workflows around managing boards, lists, cards, and users. With Pipedream, you can automate Trello tasks, like syncing cards with external databases, updating checklists, and posting notifications to other platforms. It enables seamless connection with other apps, fostering productivity by automating routine board operations, card management, and team notifications.

Trigger Code#

import common from "../common/common-webhook.mjs"; import sampleEmit from "./test-event.mjs"; export default { ...common, key: "trello-card-moved", name: "Card Moved (Instant)", /* eslint-disable-line pipedream/source-name */ description: "Emit new event each time a card is moved to a list.", version: "0.1.3", type: "source", props: { ...common.props, board: { propDefinition: [ common.props.app, "board", ], }, lists: { propDefinition: [ common.props.app, "lists", (c) => ({ board: c.board, }), ], description: "If specified, events will only be emitted if a card is moved to or from one of the selected lists", }, }, methods: { ...common.methods, async getSampleEvents() { const cards = this.lists?.length > 0 ? await this.app.getCardsInList({ listId: this.lists[0], }) : await this.app.getCards({ boardId: this.board, }); return cards; }, getSortField() { return "dateLastActivity"; }, _getListAfter() { return this.db.get("listAfter"); }, _setListAfter(listAfter) { this.db.set("listAfter", listAfter); }, isCorrectEventType({ display }) { return display?.translationKey === "action_move_card_from_list_to_list"; }, getResult({ data }) { /** Record listAfter to use in generateMeta() */ this._setListAfter(data?.listAfter?.name); return this.app.getCard({ cardId: data?.card?.id, }); }, isRelevant({ result: card, action, }) { return ( (!this.board || this.board === card.idBoard) && (!this.lists?.length || this.lists.includes(action?.data?.listAfter?.id) || this.lists.includes(action?.data?.listBefore?.id)) ); }, generateMeta({ id, name, }) { const listAfter = this._getListAfter(); name = name || id; const summary = listAfter ? `${name} - moved to ${listAfter}` : name; return { id, summary, ts: Date.now(), }; }, }, 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
Trello	`app`	`app`	This component uses the Trello 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.
Board	`board`	`string`	Select a value from the drop down menu.
Lists	`lists`	`string[]`	Select a value from the drop down menu.

Trigger Authentication#

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

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

readwrite

About Trello#

Trello is the flexible work management tool that empowers all teams to plan, track, and accomplish their work, their way.

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.24

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.24", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, 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

Create Issue with Jira API on Card Moved (Instant) from Trello API

Pipedream makes it easy to connect APIs for Jira, Trello 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