Integration
Connect Doclift PDF and Leiga
When New PDF Document Generated fires in Doclift PDF, your agent runs Create Issue in Leiga, or Updated Issue in Leiga to Get Document Request in Doclift PDF. 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 Doclift PDF 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)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 Doclift PDF and Leiga can do together
From Doclift PDF to Leiga
When New PDF Document Generated in Doclift PDF
then Create Issue in Leiga
When New PDF Document Generated in Doclift PDF
then Update issue in Leiga
From Leiga to Doclift PDF
When Updated Issue in Leiga
then Get Document Request in Doclift PDF
When Updated Issue in Leiga
then List Document Requests in Doclift PDF
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 Doclift PDF and Leiga
Triggers and actions 2 triggers · 26 actions
Trigger
New PDF Document GeneratedWebhook trigger for Doclift's async document-generation completion callback (POST .../webhooks/doclift, X-Doclift-Signature: sha256=hmac). Delivery URL is configured manually on the external application in the Doclift dashboard — no register/list/delete API exists. Fires once per document_request (all its documents_generations resolved to success/error), payload includes id, tag, type, timestamp, documents_generations[] (generation_status, file{filename,url,size}).
Action
Add Templatecreate a custom (HTML-body) template: title, description, content, orientation, margins, optional variables_attributes. Server forces category=custom.
Action
Add Variablecreate a variable on a custom template: title (unique, naming pattern), description, field_type (text/checkbox/radio/select/collection, default text), seed_value, allowed_values.
Action
Delete Templateremoves a custom template (scope restricted to category=custom, non-archived, same org).
Action
Get Document Requeststatus and documents_generations detail (signed file url, valid 2 hours) for one document request.
Action
Get Templatefull template detail including variables and content (custom templates); works for any published template of the three categories.
Action
List Document Requestslist document generation requests with id, tag, type, status, documents_generations (each with generation_status and file url).
Action
List Templatesreturns published, non-archived templates (custom/fillable_form/workflow) for the organization: id, title, description.
Action
List Variablesall variables of a custom, non-archived template: id, title, description, field_type, allowed_values (no pagination, no seed_value).
Action
Publish Templatemarks a custom template published (usable for document generation).
Action
Unpublish Templatemarks a custom template unpublished.
Action
Update Variableupdate description/field_type/allowed_values/title of a variable; allowed_values replaces the stored array.
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 Doclift PDF
Doclift PDF to Dungeons and DragonsThe D&D 5th Edition API (dnd5eapi.co) is a public reference database for the Dungeons and Dragons 5e System...
Doclift PDF to FutureAGIFutureAGI is a platform for evaluating and optimizing AI systems to ensure performance, safety, and...
Doclift PDF to ItsThisForThatItsThisForThat generates random "X for Y" startup ideas — the classic mashup pitch format.
Doclift PDF to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Doclift PDF to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Doclift PDF to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Leiga
HubSpot to LeigaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LeigaGoogle Sheets
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
Doclift PDF and Leiga, answered
What can start an automation from Doclift PDF?
Any of Doclift PDF's 1 trigger in the catalog, including New PDF Document Generated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Leiga when something happens in Doclift PDF?
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 Doclift PDF?
Yes. When something happens in Leiga, your agent can act in Doclift PDF too. This page covers both directions: Leiga's triggers and Doclift PDF's actions are listed here as well.
Do I have to build a connector for Doclift PDF 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 Doclift PDF 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.