You are helping me build the following AI agent workflow.

## Goal
PDF Actions After Generation: When PDFMonkey generates a document, this workflow fetches the file and automatically emails it, saves it to cloud storage.

## Specification
- What it does: When PDFMonkey generates a new document, you get it delivered automatically: emailed, saved to cloud storage, sent as a notification, or logged to a database, with a separate path if generation fails.
- Trigger: Triggered by an event (Event · on new PDF generation via webhook)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - PDFMonkey: Trigger and source of generated PDF files
  - n8n: Workflow orchestration and webhook handling
  - HTTP Request: Fetching PDF data from the service API

## Known pitfalls, handle each one explicitly in your implementation
1. Large PDF files can cause memory issues in n8n so configure the HTTP node to stream binary data instead of loading it into memory.
2. Webhook signatures might be ignored by default so enable signature verification in n8n to ensure requests actually come from PDFMonkey.
3. Email providers often block automated sends if SPF records are missing so verify your domain authentication before routing emails through the workflow.

## Reference implementation
https://n8n.io/workflows/3060 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/automate-pdf-actions-after-generation/ via usecasesforagents.com