> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Text to PDF

> Connect DialNexa calls to Text to PDF for file, document, folder, form submission, PDF, extracted field, signature request, or review task workflows.

Convert text to PDF.

<Note>
  Use Text to PDF with DialNexa when the call depends on a file, form, PDF, signature, contract, storage folder, or document review.
</Note>

## Where Text to PDF fits in a DialNexa workflow

Text to PDF should receive DialNexa output when the conversation affects a file, document, folder, form submission, PDF, extracted field, signature request, or review task. The handoff should explain what the caller asked for, what DialNexa learned, which record or object is affected, and who owns the next step.

<CardGroup cols={2}>
  <Card title="Prepare document handoffs" icon="check-circle">
    Capture document type, owner, missing fields, requested change, deadline, and approval path.
  </Card>

  <Card title="Extract or verify fields" icon="check-circle">
    Compare caller statements with parsed invoice, ID, contract, form, or PDF data before approval.
  </Card>

  <Card title="Route signature blockers" icon="check-circle">
    Record who needs to sign, what term is disputed, what changed, and whether legal or finance must review.
  </Card>

  <Card title="Store evidence correctly" icon="check-circle">
    Keep recordings, transcripts, generated PDFs, and signed documents beside the customer or case record.
  </Card>
</CardGroup>

## What DialNexa should capture for Text to PDF

* Caller, account, document type, file link, folder path, submission ID, signer, and permission level
* Requested change, extracted fields, missing fields, signer details, deadline, and approval owner
* Exception reason, document version, customer expectation, and promised next step
* Transcript link, recording link, DialNexa call ID, CRM link, ticket link, and storage folder link
* Redaction, retention, access, and sensitive-document flags

## High-value Text to PDF workflows

<AccordionGroup>
  <Accordion title="Caller asks for a document resend">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Text to PDF. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Contract term is disputed on a call">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Text to PDF. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Form submission needs missing fields">
    For this workflow, DialNexa should confirm location details, access notes, timing constraints, and the operational owner before updating Text to PDF. Low-confidence addresses or risky visits should go to review.
  </Accordion>

  <Accordion title="Invoice or ID text must be extracted">
    Use Text to PDF to keep the money-related context precise: reference number, amount if mentioned, customer claim, policy or approval need, and the safe follow-up path. Do not put private payment details into broad-access notes.
  </Accordion>

  <Accordion title="Signature request is blocked">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Text to PDF. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Use upload file to convertapi">
    Use upload file to convertapi when the call depends on a document, image, transcript, receipt, contract, recording, or attachment. Include why the file matters and where it should live.
  </Accordion>

  <Accordion title="Use delete file">
    Treat delete file as a controlled workflow. DialNexa should capture the caller's reason, identity confidence, approval owner, and rollback path before anything destructive or irreversible happens in Text to PDF.
  </Accordion>
</AccordionGroup>

## Workflows that pair Text to PDF with other integrations

* [Text to PDF](/integrations/text_to_pdf) + [Google Drive](/integrations/googledrive): Google Drive for storing files and evidence.
* [Text to PDF](/integrations/text_to_pdf) + [DocuSign](/integrations/docusign): DocuSign for signature requests.
* [Text to PDF](/integrations/text_to_pdf) + [HubSpot](/integrations/hubspot): HubSpot for account and deal context.
* [Text to PDF](/integrations/text_to_pdf) + [Slack](/integrations/slack): Slack for approval alerts.
* [Text to PDF](/integrations/text_to_pdf) + [Gmail](/integrations/gmail): Gmail for approved document delivery.
* [Text to PDF](/integrations/text_to_pdf) + [Zendesk](/integrations/zendesk): Zendesk for support cases tied to documents.
* [Text to PDF](/integrations/text_to_pdf) + [Google Sheets](/integrations/googlesheets): Google Sheets for extracted-field review.
* [Text to PDF](/integrations/text_to_pdf) + [QuickBooks](/integrations/quickbooks): QuickBooks for invoice-related documents.

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Text to PDF actions.
* Write a short operational summary into Text to PDF and link to the full transcript or recording for audit.
* Map required fields before launch: destination object, owner, status, urgency, next step, and record URL.
* Create review paths for low-confidence matches, sensitive requests, high-value customers, and actions that change money, access, legal terms, or customer commitments.

## FAQs

<AccordionGroup>
  <Accordion title="What should reviewers see first?">
    The document link, caller explanation, missing or disputed fields, requested outcome, owner, and transcript link.
  </Accordion>

  <Accordion title="Should DialNexa paste full documents into notes?">
    No. Store links, extracted fields, and why the document matters. Keep sensitive files in controlled storage.
  </Accordion>

  <Accordion title="When should a document go to review?">
    Missing fields, low-confidence extraction, signature blockers, legal language, identity files, and money-related changes should go to review.
  </Accordion>

  <Accordion title="What should be captured for signatures?">
    Signer, role, email, agreed terms, disputed terms, deadline, approval owner, and transcript link.
  </Accordion>

  <Accordion title="How are duplicate documents avoided?">
    Match by customer, file ID, document type, version, case, destination folder, and call ID.
  </Accordion>

  <Accordion title="Can DialNexa generate PDFs after calls?">
    Yes for approved templates such as confirmations, quotes, or summaries. Use review for legal, billing, or high-value documents.
  </Accordion>

  <Accordion title="What stays private?">
    IDs, contracts, tax documents, payment images, private health or HR files, and full recordings.
  </Accordion>

  <Accordion title="How should document resends work?">
    Verify recipient, document type, and permission before sending. Log what was sent and why.
  </Accordion>
</AccordionGroup>