Integration
Connect Codebase and Jira Service Management
When New Ticket fires in Codebase, your agent runs List customers in Jira Service Management, or New Request in Jira Service Management to Find Tickets in Codebase. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Codebase and Jira Service Management to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Codebase and Jira Service Management can do together
From Codebase to Jira Service Management
When New Ticket in Codebase
then List customers in Jira Service Management
When New Time Session in Codebase
then Add comment in Jira Service Management
From Jira Service Management to Codebase
When New Request in Jira Service Management
then Find Tickets in Codebase
When Updated Request in Jira Service Management
then Get Ticket Note in Codebase
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Codebase and Jira Service Management
Triggers and actions 4 triggers · 25 actions
Trigger
New TicketTriggers when a new ticket is created in a Codebase project.
Trigger
New Time SessionTriggers when a new time session is logged on a Codebase project.
Action
Delete ProjectDeletes a Codebase project. Codebase refuses the delete when the project still has dependent records.
Action
Delete Time SessionDeletes a time session from a Codebase project.
Action
Find TicketsSearches a Codebase project's tickets with a Codebase search query (for example "status:open assignee:me") and returns the matching tickets.
Action
Get ProjectReturns one Codebase project by its permalink, with its status and ticket counts.
Action
Get Ticket NoteReturns one note (update) on a Codebase ticket.
Action
Get Time SessionReturns one time session logged on a Codebase project.
Action
List MilestonesReturns the milestones in a Codebase project with their dates, status and responsible user.
Action
List ProjectsReturns all projects in the Codebase account, with each project's name, permalink, status and ticket counts.
Action
List Ticket CategoriesReturns the ticket categories defined in a Codebase project, with the IDs used to set a ticket's category.
Action
List Ticket NotesReturns every note (update) posted on a Codebase ticket.
Action
List Ticket PrioritiesReturns the ticket priorities defined in a Codebase project, with the IDs used to set a ticket's priority.
Action
List Ticket StatusesReturns the ticket statuses defined in a Codebase project, with the IDs used to set a ticket's status.
Action
List Ticket TypesReturns the ticket types defined in a Codebase project (Bug, Enhancement, Feature, Task and any custom types).
Action
List Time SessionsReturns the time sessions logged on a Codebase project, optionally filtered by user and date range.
Trigger
New RequestTriggers when a new customer request is raised in Jira Service Management.
Trigger
Updated RequestTriggers when a customer request in Jira Service Management is created or changed (status, fields or other details).
Action
Add commentAdds a public or internal comment to a Jira Service Management customer request.
Action
Add organizationAdds an existing organization to a service desk so its members can raise requests there. Does nothing if the organization is already on the service desk.
Action
Add participants to requestAdds one or more users as participants on a Jira Service Management customer request and returns the request's participants.
Action
Create RequestCreates a customer request in a Jira Service Management service desk, using the chosen request type and its field values.
Action
Get requestReturns a customer request by its ID or key, including its summary, status, reporter and field values.
Action
List commentsReturns the comments on a Jira Service Management customer request, optionally filtered to public or internal comments.
Action
List customersReturns the customers of a service desk, optionally filtered by name or email.
Action
List requestsReturns the customer requests visible to the connected user, optionally filtered by service desk, request type, status, ownership or a summary search.
Action
List request typesReturns the customer request types available in a Jira Service Management service desk, optionally filtered by group or search text.
Action
List service desk organizationsReturns the customer organizations associated with a service desk.
Action
List service desksReturns all the service desks in your Jira Service Management site that you have access to, with each desk's id, project key and name.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Codebase
Codebase to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Codebase to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Codebase to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Codebase to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Codebase to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Codebase to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Jira Service Management
HubSpot to Jira Service ManagementHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Jira Service ManagementGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Jira Service ManagementGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Jira Service ManagementGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Jira Service ManagementGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to Jira Service ManagementActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Codebase and Jira Service Management, answered
What can start an automation from Codebase?
Any of Codebase's 2 triggers in the catalog, including New Ticket and New Time Session. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Jira Service Management when something happens in Codebase?
Any of Jira Service Management's 11 actions, including Create Request, Add comment, Add organization and Add participants to request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jira Service Management to Codebase?
Yes. When something happens in Jira Service Management, your agent can act in Codebase too. This page covers both directions: Jira Service Management's triggers and Codebase's actions are listed here as well.
Do I have to build a connector for Codebase or Jira Service Management?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Codebase and Jira Service Management without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.