Leiga is an AI-powered project management tool that automates tasks and enhances team collaboration.
Leiga is an AI-powered project management tool that automates tasks and enhances team collaboration. On Nagent, Leiga is exposed as a fully-configurable project management integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Leiga into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Leiga to automate the kinds of tasks project management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Leiga into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Leiga, with input parameters and output schema. Drop these into any step of an agent built in Helix.
LEIGA_CREATE_PROJECTTool to create a new project in Leiga. Use after gathering project details and authenticating.
Input parameters
Name of the project
Contact person for the project
Identifier of the project type
Project end date and time in ISO 8601 format
Project start date and time in ISO 8601 format
Project description
Phone number of the contact person
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_FILE_LISTTool to retrieve a paginated list of files in a specified directory. Use after obtaining the directory ID to view files.
Input parameters
Page number for pagination (must be >= 1)
Optional search keyword to filter file names
Optional filter for file type, e.g., 'image', 'pdf'
Number of items per page (must be >= 1)
Directory ID to list files from
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_ISSUE_DETAIL_BY_ISSUE_NUMBERTool to fetch detailed information about a specific issue using its issue number. Use when you have an issue number and need complete issue details.
Input parameters
The unique identifier for the issue.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_ISSUE_SCHEMATool to retrieve the issue custom-field schema. Use when you need the full list of field configurations after selecting an issue type.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_PROJECT_INFORMATIONTool to fetch detailed information about a specific project by its ID. Use when you need complete project metadata, including owner and members.
Input parameters
The unique identifier of the project
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_PROJECT_OVERVIEW_TEMPLATETool to retrieve the project overview template. Use when you need the structured overview template for a project after confirming its ID.
Input parameters
Unique identifier of the project to retrieve the overview template for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_PROJECT_TEMPLATE_LISTTool to retrieve a list of project templates. Use when browsing available templates before creating a new project.
Input parameters
Template name to filter the list
Current page number (must be >= 1)
Number of records per page (must be >= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_VERSION_LISTTool to fetch list of versions for a specific platform. Use when you need to view all available versions before deployment.
Input parameters
Page number for pagination (must be >= 1)
Number of items per page (must be >= 1)
Platform type, e.g., 'android' or 'ios'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_GET_WEBHOOK_TYPE_LISTTool to retrieve the list of available webhook types. Use when configuring webhooks and you need to know valid event types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
LEIGA_LIST_PROJECTSTool to list all projects available to the authenticated user. Use when you need to retrieve your projects in paginated form (e.g., page 1 with 10 per page).
Input parameters
Page number for pagination (must be >= 1)
Number of projects per page (must be >= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 74 agents privately built on Nagent that already use Leiga.
Build on Nagent
Connect Leiga to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Leiga, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Leiga is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Leiga is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Leiga steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Leiga event fires, the agent kicks off automatically.
Every Leiga action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Leiga ships with 10 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Leiga together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Leiga-based workflows tailored to your business.