Skip to content

📄 Document Node

Purpose

The Document node sends a file attachment to the customer on WhatsApp. Use it to share PDFs, brochures, price lists, manuals, contracts, or any downloadable file.

Business Scenario

Use the Document node when you need to:

  • Share product brochures — let customers download your catalogue
  • Send price lists — provide detailed pricing in a formatted PDF
  • Distribute forms — application forms, registration documents
  • Provide manuals — user guides, setup instructions
  • Send contracts — terms and conditions, service agreements

Configuration

Field Description
Title Internal name (e.g., "Product Brochure")
File Pick a file from My Documents — resolved to a fresh download link at send time
Or a direct URL Fallback: a public URL to the file (used when no My Documents file is selected)
Filename The filename shown to the customer (e.g., brochure.pdf)
Caption Text shown beneath the file in WhatsApp

Media Source Priority

The runtime resolves the file in this order:

  1. Asset ID (My Documents) — recommended, always generates a fresh signed URL
  2. Document Alias — a named reference
  3. Direct URL — a public URL you enter manually

Use My Documents

Uploading files to My Documents is the recommended approach. The system generates a fresh, signed download link every time the message is sent, so links never expire.

Properties

Property Type Required Default Description
title Text No "" Internal node name
assetId Text No — My Documents asset reference
documentAlias Text No — Named alias for the document
url Text No — Direct URL to the file
filename Text Yes document.pdf Displayed filename
caption Text Yes "" Caption text shown below the file

Media Source Required

At least one media source (asset, alias, or URL) must be set. The designer shows a validation error if all three are empty.

Inputs

Handle Type Description
Top (↑) Target Receives a connection from any preceding node

Outputs

Handle Type Description
Bottom (↓) Continue Connects to the next node in the flow

Connection Rules

  • ✅ Can receive connections from any node type
  • ✅ Can connect to any node type
  • ❌ Must have a media source (asset, alias, or URL) — validation error otherwise

Example Flow Diagram

flowchart TD
    A["📋 Menu"] -->|"Download Brochure"| B["📄 Product Brochure<br/><em>brochure.pdf</em><br/><em>Here's our latest catalogue!</em>"]
    B --> C["💬 Follow-up<br/><em>Would you like to know more?</em>"]
    C --> A

    style B fill:#fef3c7,stroke:#f59e0b,stroke-width:2px

Best Practices

  • ✅ Use descriptive filenames — acmecorp-pricing-2025.pdf is better than document.pdf.
  • ✅ Write helpful captions — tell the customer what the file contains.
  • ✅ Upload to My Documents for reliable links that never expire.
  • ✅ Follow with a message — add a Message or Menu after the document so the conversation continues.
  • ✅ Keep files small — WhatsApp has a 100 MB file size limit, but smaller files download faster.

Common Mistakes

Mistake What Happens Fix
No media source set Validation error: "Document has no media source" Upload a file or enter a URL
Direct URL expires Customers get a broken link Use My Documents instead
Missing filename Customer sees a generic file icon Set a descriptive filename
Forgetting to connect to next node Dead end — conversation stops Connect to a Message or Menu
  • 🖼️ Image — Send images instead of documents
  • 💬 Message — Add context before or after sending a document
  • 📋 Menu — Let customers choose which document to receive