Create Issue with Jira API on New or Removed Documents in a Collection from Fauna API

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

Trigger workflow on

New or Removed Documents in a Collection from the Fauna 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 Fauna 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 or Removed Documents in a Collection trigger
1. Configure timer
2. Connect your Fauna account
3. Select a Collection
4. Optional- Configure Emit changes as a single event
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 or Removed Documents in a Collection on Fauna

Description:Emit new event each time you add or remove a document from a specific collection, with the details of the document.

Version:0.0.8

Key:faunadb-changes-to-collection

View on GitHub

Fauna Overview#

Fauna API offers a powerful serverless database solution for modern applications. Its unique capabilities allow for highly scalable, secure, and flexible data management. With Pipedream, you can harness the power of Fauna to create intricate serverless workflows that react to various triggers, manage data efficiently, and connect seamlessly with other services and APIs to automate complex tasks.

Trigger Code#

import fauna from "../../faunadb.app.mjs"; import _ from "lodash"; import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform"; export default { type: "source", key: "faunadb-changes-to-collection", name: "New or Removed Documents in a Collection", description: "Emit new event each time you add or remove a document from a specific collection, with the details of the document.", version: "0.0.8", dedupe: "unique", // Dedupe events based on the concatenation of event + document ref id props: { timer: { type: "$.interface.timer", default: { intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL, }, }, db: "$.service.db", fauna, collection: { propDefinition: [ fauna, "collections", ], }, emitEventsInBatch: { type: "boolean", label: "Emit changes as a single event", description: "If `true`, all events are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each event in Fauna as its own event in Pipedream", optional: true, default: false, }, }, async run() { // As soon as the script runs, mark the start time so we can fetch changes // since this time on the next run. Fauna expects epoch ms as its cursor. const ts = +new Date() * 1000; const cursor = this.db.get("cursor") || ts; const events = await this.fauna.getEventsInCollectionAfterTs( this.collection, cursor, ); if (!events.length) { console.log(`No new events in collection ${this.collection}`); this.db.set("cursor", ts); return; } console.log(`${events.length} new events in collection ${this.collection}`); // Batched emits do not take advantage of the built-in deduper if (this.emitEventsInBatch) { this.$emit({ events, }, { summary: `${events.length} new event${events.length > 1 ? "s" : ""}`, id: cursor, }); } else { for (const event of events) { this.$emit(event, { summary: `${event.action.toUpperCase()} - ${event.document.id}`, id: `${event.action}-${event.document.id}`, // dedupes events based on this ID }); } } // Finally, set cursor for the next run to the max timestamp of the changed events, ensuring we // get all events after that on the next run. We need to add 1 since the timestamp filter in // Fauna is inclusive: https://docs.fauna.com/fauna/current/api/fql/functions/paginate const maxEventTs = _.maxBy(events, (event) => event.ts).ts + 1; this.db.set("cursor", maxEventTs); }, };

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
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Fauna	`fauna`	`app`	This component uses the Fauna app.
Collection	`collection`	`string`	Select a value from the drop down menu.
Emit changes as a single event	`emitEventsInBatch`	`boolean`	If `true`, all events are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each event in Fauna as its own event in Pipedream

Trigger Authentication#

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

Create a key in the Security section of your FaunaDB dashboard, then enter the Secret below.

About Fauna#

The distributed serverless database combining the flexibility of NoSQL with the relational querying capabilities of SQL systems.

Action#

Create Issue on Jira

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

Version:0.1.25

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 documentation](https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-post)", version: "0.1.25", 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 added or updated. 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 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 + Fauna#

Other Popular Integrations#

Execute GraphQL Query with Fauna API on New Event from Jira API

Jira + Fauna

Create Issue with Jira API on New or Removed Documents in a Collection from Fauna API

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