# Automatically populate ticket properties from attached PDF documents

**URL:** <https://community.hubspot.com/t/automatically-populate-ticket-properties-from-attached-pdf-documents/145115>\
**Category:** HubSpot Ideas\
**Tags:** help-desk\
**Created:** [January 19, 2026, 7:15pm UTC](https://community.hubspot.com/t/automatically-populate-ticket-properties-from-attached-pdf-documents/145115 "2026-01-19T19:15:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AMorelly](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/amorelly/32/8867_2.png) [@AMorelly](https://community.hubspot.com/u/AMorelly)\
**Post date:** [January 19, 2026, 7:15pm UTC](https://community.hubspot.com/t/automatically-populate-ticket-properties-from-attached-pdf-documents/145115/1 "2026-01-19T19:15:48Z")

</div>

**Description:**

When a PDF document is uploaded to a ticket record (either manually by a user or via email attachment), allow HubSpot to read the PDF content and automatically populate ticket properties based on that data.

**Example use cases:**

- Support teams receive standardized PDF forms (e.g., order forms, incident reports, RMA forms, clinical reports) that include key details like customer ID, product, serial number, case type, priority, and location.
- Currently, an agent must open the PDF, manually read the data, and then copy/paste it into the ticket properties.

**Proposed functionality:**

1. **Automatic parsing of attached PDFs**

2. **Mapping extracted fields to ticket properties**

3. **Configurable templates / patterns**

4. **Review and confirmation**

5. **Automation & reporting benefits**

**Why this matters:**

- Reduces manual data entry and human error.
- Speeds up intake and triage for tickets that rely on structured PDF forms.
- Improves data consistency across tickets, enabling more accurate reporting and automation.
- Frees support agents to focus on resolution rather than transcription.

**Nice-to-have enhancements:**

- Support for other document types (e.g., DOCX, image-based PDFs with OCR).
- Logging of an “extracted from PDF” note on the ticket timeline with a link to the source file.
- Ability to re-run extraction if a newer version of the PDF is attached.