jira: add MakeApiCall component#1048
Open
apx-vero wants to merge 3 commits into
Open
Conversation
added 3 commits
April 8, 2026 16:08
Adds a generic MakeApiCall component for Jira connector. Allows making arbitrary authorized API calls to the Jira Cloud API using OAuth2 authentication. The base URL is automatically derived from the user's authenticated Jira Cloud site (profileInfo.apiUrl). Supports: GET, POST, PUT, PATCH, DELETE methods, query parameters, and JSON body. Closes #1459
Contributor
|
@vtalas test mention 12339839 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a generic
MakeApiCallcomponent to the Jira connector (closes #1459).What's included
core/MakeApiCall/MakeApiCall.js— Makes an authorized HTTP request using Jira OAuth2 (Bearer {accessToken}). The endpoint path is appended toprofileInfo.apiUrl(which resolves tohttps://api.atlassian.com/ex/jira/{cloudId}/rest/api/3) — this way users don't need to know their cloudId, it's picked up automatically from the auth profile.core/MakeApiCall/component.json— Inputs: endpoint path, HTTP method, query parameters, request body. Outputs: status, headers, body.Auth / Scopes
OAuth2 — all existing connector scopes included per spec in #1459. Note from the issue:
manage:jira-configurationis admin-level and more privileged than most use cases need, but this is the current approach per the spec (dynamic scope selection is a future improvement).