Integration
Connect Doclift PDF and Trengo
When something happens in Doclift PDF or Trengo, your agent does the next thing in the other. 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 Trengo 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 and Trengo can do together
From Doclift PDF to Trengo
When New PDF Document Generated in Doclift PDF
then Add internal note to ticket in Trengo
When New PDF Document Generated in Doclift PDF
then Add ticket in Trengo
From Trengo to Doclift PDF
When New Internal Note in Trengo
then Add Template in Doclift PDF
When New Outbound Message in Trengo
then Add Variable 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 Trengo
Triggers and actions 4 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
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
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 Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TrengoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TrengoGoogle Sheets
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Doclift PDF and Trengo, 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 Trengo when something happens in Doclift PDF?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Doclift PDF?
Yes. When something happens in Trengo, your agent can act in Doclift PDF too. This page covers both directions: Trengo's triggers and Doclift PDF's actions are listed here as well.
Do I have to build a connector for Doclift PDF or Trengo?
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.