Integration
Connect Codebase and Leiga
When New Ticket fires in Codebase, your agent runs Create Issue in Leiga, or Updated Issue in Leiga 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 Leiga 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 Leiga can do together
From Codebase to Leiga
When New Ticket in Codebase
then Create Issue in Leiga
When New Time Session in Codebase
then Update issue in Leiga
From Leiga to Codebase
When Updated Issue in Leiga
then Find Tickets in Codebase
When Updated Issue in Leiga
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 Leiga
Triggers and actions 3 triggers · 29 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
Updated IssueTriggers when an issue is updated in Leiga.
Action
Add commentAdds a comment to a Leiga issue or other record, optionally as a reply to an existing comment.
Action
Add epicCreates a new epic in a Leiga project.
Action
Add projectCreates a new project in Leiga from a project template, with a name, leader and optional description.
Action
Add versionCreates a new version (release) in Leiga with a name, owner, and optional description, start date and estimated release date.
Action
Create IssueCreates a new issue in a Leiga project with the issue type and field values you provide.
Action
Delete issueDeletes an issue from a Leiga project.
Action
Find issues by criteriaSearches the issues in a Leiga project matching a summary keyword, status types, field values or date ranges, and returns the matching issues.
Action
Get issueReturns the full details of a Leiga issue, including its custom field values, by issue ID.
Action
Get projectReturns the details of a Leiga project by its ID.
Action
Get versionReturns the details of a Leiga version, including its name, status and release dates.
Action
List commentsReturns the comments on a Leiga issue or other item, including replies and attachments.
Action
List Issue TypesReturns the issue types (such as bug or task) available in a Leiga project.
Action
List projectsReturns all projects in your Leiga organization with their id, name, key and archived status.
Action
Update issueUpdates an existing Leiga issue's field values, such as its summary, description, status, priority, assignee or labels.
Action
Update projectUpdates a Leiga project's overview fields, such as its name or start time.
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 Leiga
HubSpot to LeigaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LeigaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to LeigaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeigaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LeigaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LeigaActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Codebase and Leiga, 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 Leiga when something happens in Codebase?
Any of Leiga's 15 actions, including Create Issue, Update issue, Update project and Add comment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leiga to Codebase?
Yes. When something happens in Leiga, your agent can act in Codebase too. This page covers both directions: Leiga's triggers and Codebase's actions are listed here as well.
Do I have to build a connector for Codebase or Leiga?
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 Leiga 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.