Integration
Connect Doclift PDF to PractiTest
When something happens in Doclift PDF, your agent does the next thing in PractiTest. Describe it 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 PractiTest to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 can start in PractiTest
When New PDF Document Generated in Doclift PDF
then Add Instance in PractiTest
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 PractiTest
Triggers and actions 1 trigger · 33 actions
- New PDF Document Generated
Webhook 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}).
- Add Template
create a custom (HTML-body) template: title, description, content, orientation, margins, optional variables_attributes. Server forces category=custom.
- Add Variable
create a variable on a custom template: title (unique, naming pattern), description, field_type (text/checkbox/radio/select/collection, default text), seed_value, allowed_values.
- Delete Template
removes a custom template (scope restricted to category=custom, non-archived, same org).
- Get Document Request
status and documents_generations detail (signed file url, valid 2 hours) for one document request.
- Get Template
full template detail including variables and content (custom templates); works for any published template of the three categories.
- List Document Requests
list document generation requests with id, tag, type, status, documents_generations (each with generation_status and file url).
- List Templates
returns published, non-archived templates (custom/fillable_form/workflow) for the organization: id, title, description.
- List Variables
all variables of a custom, non-archived template: id, title, description, field_type, allowed_values (no pagination, no seed_value).
- Publish Template
marks a custom template published (usable for document generation).
- Unpublish Template
marks a custom template unpublished.
- Update Variable
update description/field_type/allowed_values/title of a variable; allowed_values replaces the stored array.
- Add Instance
Adds a test to a test set in a PractiTest project as a new instance.
- Add Issue
Creates an issue in a PractiTest project.
- Add Test
Create a new test case in a project.
- Create a Run
Uploads a new run result for a test instance in a PractiTest project — typically automated test results from CI, or a manual run with step results.
- Create Requirement
Creates a new requirement.
- Delete Issue
Deletes a specific issue from a PractiTest project.
- Delete Requirement
Deletes a specific requirement from a PractiTest project.
- Delete Test
Deletes a specific test from a PractiTest project.
- Get Issue
Retrieves a single issue from a PractiTest project, including its attributes and custom field values.
- Get Requirement
Retrieves a single requirement from a PractiTest project by its system id.
- Get Run
Retrieve a single test run by id.
- Get Test
Retrieve a single test by id.
- List Instances
Lists the test instances in a PractiTest project, optionally filtered by test set, test, name or display id.
- List Issues
Lists the issues in a PractiTest project, optionally narrowed by filter, display ids, title or PTQL query.
- List Projects
Lists the projects in the PractiTest account. With a personal API token, only the projects that user can access are returned.
- List Requirements
Returns all requirements in a PractiTest project, optionally narrowed by filter, display ids, name or PTQL query.
- List Runs
List all test runs in a project.
- List Tests
List all tests in a project.
- List Users
Lists the users in the PractiTest account, optionally filtered by email address or to active users only.
- Update Issue
Updates an existing issue in a PractiTest project. Only the fields you fill in are changed.
- Update Requirement
Update a requirement's fields.
- Update Test
Updates a specific test in a PractiTest project. Only the fields you fill in are changed.
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 PractiTest
Google Sheets to PractiTestGoogle Sheets
Gmail to PractiTestGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PractiTestGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Doclift PDF and PractiTest, 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 PractiTest when something happens in Doclift PDF?
Any of PractiTest's 22 actions, including Create a Run, Create Requirement, Update Issue and Update Requirement. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PractiTest to Doclift PDF?
PractiTest has no triggers in the catalog today, so automations start in Doclift PDF. If you need the other direction, ask: your agent reads PractiTest's API documentation and adds it.
Do I have to build a connector for Doclift PDF or PractiTest?
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.
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.