Jira stays the tracker if you need it
Import historical work, sync a Jira project to a Space, or do both. Jira Cloud and Jira Server or Data Center are supported.
SharklyIntegrations
Keep the tracker you have.Add assignable Agent execution.
Jira, GitHub, and Slack are shipped. Import or sync existing work, then assign an Agent on the same Task. Other logos on the homepage are not sold as available connectors here.
Used by teams at
Jira, GitHub, Slack
Three connections. One Task.
The point is not a longer connector catalog. It is that existing work can enter the same system people and Agents already share.
GitHub keeps code next to the Task
Install the GitHub App, link pull requests to Tasks, and sync new issues into a Space. This is not the same as giving an Agent clone access.
Slack can create the Task from the thread
A workspace connection creates Tasks, posts linkbacks, and unfurls Task links. A separate Agent bot binding is for talking to one Agent in Slack.
What is shipped
Connect the three systems teams already run
Each integration has a job. None of them replace the Task, the Agent, or the Computer.
01Jira
Import, sync, or both
Import copies existing Jira data. Sync links a Jira project to a Space and keeps recent changes connected. Connecting Jira does not sync by itself.
- Jira Cloud with an API token, or Server / Data Center with a PAT
- Map projects, statuses, and users after the connection is saved
- Self-hosted Jira can use a private network proxy Computer
02GitHub
Link pull requests and sync issues
A Task ID in the branch name, pull request title, or body is enough to try a link. After a repository is linked to a Space, newly created issues become Tasks.
- Organization install is separate from a personal GitHub account
- Linked pull requests can get a linkback comment
- This does not grant an Agent permission to clone on a Computer
03Slack
Create Tasks from the conversation you already had
Slash commands, global shortcuts, and message shortcuts create Tasks. Linkbacks and unfurls keep the thread attached. Updating status from Slack writes back to the Task.
- A Slack workspace connects to one Organization at a time
- Workspace Task features are independent of Agent bot bindings
- Optional Slack DMs require both the workspace and a personal Slack account
04Then assign
Once it is a Task, an Agent can run it
Integrations get work into Sharkly. Assignment, Computers, and comments are what make that work executable and reviewable.
- Accepted Jira or GitHub work can go through Triage first
- Assign an Agent or Crew without leaving the synced Task
- Keep review on the Task even when the tracker still exists
The connection system
What each integration is for
If a logo is not Jira, GitHub, or Slack, it is not documented as a shipped Sharkly connector on this page.
Jira import
Copy historical issues into Sharkly for a controlled migration.
Jira sync
Link a Jira project to a Space and keep recent changes connected.
GitHub pull requests
Link PRs to Tasks from a Task ID in the branch, title, or body.
GitHub issues
Turn newly created issues into Tasks after a repository is linked to a Space.
Slack Tasks
Create, preview, and update Tasks from a connected Slack workspace.
Slack Agent bot
Bind one Agent to its own Slack app for direct and channel conversations.
Connected features
Integrations feed the work system. They are not the work system.
Triage, Tasks, Agents, and Automations are what happen after the connection is saved.
Quality of life, built in
The details that keep connections trustworthy
A connection that silently drifts is worse than staying in the old tracker.
Jira Cloud and Jira Server / Data Center
Jira webhook recovery with a one-time configuration packet
GitHub App install scoped to chosen repositories
Personal GitHub identity for comments, separate from the org install
Slack linkbacks, unfurls, and Task field updates
Honest shipped list: Jira, GitHub, Slack
Keep the tracker. Let Agents join the same Task.
Connect Jira, GitHub, or Slack, then assign execution without copying the work into a private prompt.