Integration
Connect PandaDoc to Simpleen Translation
When something happens in PandaDoc, your agent does the next thing in Simpleen Translation. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PandaDoc and Simpleen Translation to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with PandaDoc and Simpleen Translation
Triggers and actions 3 triggers · 32 actions
Trigger
Document completedPolling trigger. Fires when a document reaches completed status. Dedup by document id.
Trigger
Document completed (instant)Instant trigger: fires when a PandaDoc document reaches the completed state. Self-registering — APIANT creates the PandaDoc webhook when you turn the automation on and removes it when you turn it off, so there is nothing to paste. Only document_state_changed events with status document.completed are passed through; each fires once with the document id, name, status, created/modified/completed timestamps and the full document object.
Trigger
Document updatedPolling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.
Action
Change document statusManually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.
Action
Create contactCreates a new contact.
Action
Create document from templateCreates a new document from a template, with recipients, tokens, fields, and pricing tables.
Action
Create document linkGenerates a shareable session link for a recipient to view/sign a document.
Action
Delete contactDeletes a contact by ID.
Action
Delete documentDeletes a document by ID.
Action
Download document PDFReturns the document as a PDF file. Use watermark options as needed.
Action
Find document by nameFinds a document by name and emits its ID. An error occurs if none or more than one is found.
Action
Get document detailsRetrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.
Action
Get document entered dataEmits arrays of field and token names and values for the specified document.
Action
Get document statusReturns the current status of a document by ID.
Action
Get template detailsRetrieves details for a template by ID, including roles, fields, tokens, and pricing tables.
Action
List contactsLists contacts in the workspace.
Action
List documentsLists documents, optionally filtered by status, template, folder, or search query.
Action
List foldersLists document folders.
Action
List membersLists workspace members (users).
Action
List templatesLists available document templates.
Action
Send documentMoves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.
Action
Update contactUpdates an existing contact by ID.
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segmentCreate a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create TranslationTranslates content to selected target language
Action
Get fileGet a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossaryGet a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segmentGet a specific translation segment by id. GET /segments/{id}.
Action
List filesList the localization files known to the account. GET /files.
Action
List glossariesList the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languagesList all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segmentsList translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translatorTranslate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossaryUpdate an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segmentPost-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{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