> ## 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.

# Cloudflare Browser Rendering

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

Cloudflare Browser Rendering enables developers to programmatically control and interact with headless browser instances running on Cloudflare’s global network, facilitating tasks such as automating browser interactions, capturing screenshots, generating PDFs, and extracting data from web pages.

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

## Where Cloudflare Browser Rendering fits in a DialNexa workflow

Cloudflare Browser Rendering 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="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>

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

## What DialNexa should capture for Cloudflare Browser Rendering

* 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 Cloudflare Browser Rendering workflows

<AccordionGroup>
  <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 Cloudflare Browser Rendering. 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 Cloudflare Browser Rendering. Low-confidence addresses or risky visits should go to review.
  </Accordion>

  <Accordion title="Invoice or ID text must be extracted">
    Use Cloudflare Browser Rendering 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 Cloudflare Browser Rendering. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Customer sends a file as evidence">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Cloudflare Browser Rendering. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Document should be stored with a case">
    DialNexa should attach the relevant file or visual evidence, summarize what the caller says it proves, and mark the review owner in Cloudflare Browser Rendering. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Reviewer needs a structured exception note">
    For this workflow, DialNexa should send Cloudflare Browser Rendering a concise, action-ready handoff: matched caller, affected record, reason for the update, urgency, owner, next step, and links to call evidence.
  </Accordion>

  <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 Cloudflare Browser Rendering. Sensitive files should stay behind restricted links.
  </Accordion>

  <Accordion title="Use list accounts">
    Use list accounts before answering, routing, or creating follow-up. DialNexa should verify the lookup result against the caller and send low-confidence matches to a human queue.
  </Accordion>

  <Accordion title="Use capture screenshot">
    Use capture screenshot when the call outcome maps clearly to that operation and the required fields, owner, review state, and evidence links are known.
  </Accordion>
</AccordionGroup>

## Workflows that pair Cloudflare Browser Rendering with other integrations

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

## Implementation notes

* Use the DialNexa call ID as the idempotency key before running Cloudflare Browser Rendering actions.
* Write a short operational summary into Cloudflare Browser Rendering 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="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>
</AccordionGroup>