Faster time to market
Ship integrations without building backend connectors.

Embed in-app Jira workflows at scale — create and update issues, surface project data and automate ticketing directly inside your SaaS product using Cyclr’s low-code builder and publish integrations to your customers.
Ship integrations without building backend connectors.
Centralize auth, retries and rate-limit handling.
Expose approved Jira actions as managed, versioned MCP tools.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Cyclr’s JIRA connector lets product and engineering teams embed customer-facing Jira integrations — issue creation, search, project and board reads, and webhook-driven automation — into multi-tenant SaaS apps. Build orchestrations, map and transform data between systems, and expose selected actions as governed MCP tools without shipping bespoke integration code.
PRODUCT USE CASES
Build customer-facing automations that create issues from app events, sync ticket status, embed issue creators and surface project data for reporting — all publishable through Cyclr’s embedded integration marketplace.
Automatically open Jira issues when app alerts, error logs or user reports occur, with mapped context and attachments.
Keep status, priority and comments in sync between your app and Jira for consistent cross-system workflows.
Embed an issue creator, issue picker and JQL-based search directly inside your product UI for end users.
ORCHESTRATION
Cyclr sits between your SaaS product and JIRA to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
JIRA processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore JIRA methods you can orchestrate through Cyclr.
Creates a new Issue.
Returns details of an issue for a given ID.
List all issues updated since the last successful run.
List all issues attached to this project and issue type.
List all issues created since the last successful run.
List all issues in the project.
Lists all issues created or updated since the last successful run.
Returns (where available) the comment left with a satisfaction rating for an issue.
Retrieve a worklog by issue ID and worklog ID.
List ID's for worklogs that have been updated since last run.
Adds a worklog to an issue.
Returns a list of the specified worklogs.
Updates a worklog to for an issue.
Update a webhook.
Get a webhook specified by ID.
Create a webhook.
List all webhooks.
Delete a webhook.
Create a project in this JIRA account.
List all projects.
Get details of a project, by passing its ID or Key.
List all projects which are visible for the currently logged in user. If no user is logged in, it returns the list of projects that are visible when using anonymous access.
Lists all meta data for creating an issue.
Returns meta data for the issue.
Returns the details of a single Object.
Creates a new Object in Assets.
List all Objects in Assets with a Status of 'Active'.
Update an existing Object in Assets.
List all Objects in Assets with a Status of 'Active' created since the last successful run.
List all Objects in Assets with a Status of 'Active' updated since the last successful run.
Delete the referenced Object.
Returns details of the requested Dashboard.
Returns a list of all Dashboards.
Triggered whenever a sprint is updated.
Get a sprint by ID.
Triggered whenever a sprint is created.
Create a future sprint.
Updates a sprint.
List all worklogs for an issue updated since the last successful run.
List all worklogs for an issue.
List all worklogs for an issue created since the last successful run.
List all worklogs for an issue started since the last successful run.
Triggered whenever an issue is updated.
List all issues updated since the last successful run.
List all issues created since the last successful run.
Lists all issues created or updated since the last successful run.
Returns a list of all issue types for a project that are visible to the user.
Returns details of an issue for a given ID.
Triggered whenever an issue is created.
Lists all issue types visible to the user.
Update an issue.
Deletes the specified issue.
Creates a new Issue.
Lists all transitions available for this issue, for the current user.
Search for issues with a user defined JQL string.
List all issues.
Performs the issue transition.
Creates a link between two issues.
Search for issues with a user defined JQL string.
List all issues attached to a project.
Returns the contents of an attachment.
Adds one or more attachments to an issue.
Delete a specified property for the issue identified.
Returns the keys of all properties for the issue identified.
Returns the keys of a specified property for the issue identified.
Returns details and file content for the specified attachment.
Store data in an array against a property key.
Store data against a property key.
Triggered whenever a board is created.
Returns all boards the user has permission to view.
Triggered whenever a board is updated.
Move issues from the backlog to the board.
Returns the board for a specific ID.
Returns a list of all issues.
Returns a list of all issues.
Update an issue.
Deletes specified comment attached to an issue.
Returns all comments for an issue.
Triggered whenever a comment is updated.
Returns a single comment attached to an issue.
Update a specified comment attached to an issue.
Triggered whenever a comment is created.
Add a new comment to a specified issue.
Create an organization.
List all organizations.
Retrieve a list of objects based on an AQL query.
Delete an existing Object in Assets.
Creates a new Object in Assets.
Retrieve a list of objects based on the provided query.
Get the specified object.
Returns the details of a single Object.
Update an existing Object in Assets.
Allows you to search users.
Allows you to search users with the v2 API.
Returns the details of a specified user
Deletes a user. If the operation completes successfully then the user is removed from Jira's user base.
Creates a user. This resource is retained for legacy compatibility.
Returns a list of Assets workspace IDs.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing JIRA integrations in Cyclr.
https://api.atlassian.comCloud site domain, Atlassian account email plus API token or OAuth client ID/secret and redirect URI.
Issues, Projects, Users, Search, Boards, Sprints, Worklogs, Webhooks
Jira Cloud REST uses offset pagination with startAt and maxResults; responses include total for next-page calculation.
Jira Cloud enforces burst-based per-tenant rate limits and returns HTTP 429 for excess requests. Implement exponential backoff and avoid load testing production tenants.
IMPLEMENTATION
OAuth 2.0 authorization code grants (3LO) are recommended for apps. Ad-hoc scripts or service accounts can use Atlassian API tokens with basic auth. Forge and Connect apps use their platform-specific auth flows.
Cloud site domain, Atlassian account email plus API token or OAuth client ID/secret and redirect URI.
API tokens default to one-year expiration; admin permissions often required to register apps and webhooks.
COMMON QUESTIONS
Use OAuth 2.0 (3LO) for customer-facing apps; ad-hoc scripts or service accounts can use Atlassian API tokens with basic auth. Forge and Connect apps use their own auth frameworks.
Admin rights may be required to register apps, configure OAuth credentials or create instance-level webhooks. Basic API token access can work for per-user integrations.
Yes. Jira Cloud supports admin and app webhooks and they can drive Cyclr orchestrations for near real-time automation.
Implement retries with exponential backoff, batch work when possible and respect Jira’s burst-based per-tenant limits to avoid HTTP 429 responses.
KEEP EXPLORING
Related Developer Tools connector for customer-facing integration workflows.
Related connectorRelated Developer Tools connector for customer-facing integration workflows.
Related connectorRelated Developer Tools connector for customer-facing integration workflows.