Get Zendesk ticket attachments
Module · Stable
Pull a ticket’s attachments onto local disk — the customer’s photo, ready to read.
Fetches the files attached to a Zendesk ticket and returns local paths to their bytes. Zendesk hangs attachments off comments rather than the ticket, so this walks every comment on the ticket — a photo sent in a follow-up reply is found, not just one on first contact — and so is one pasted straight into the body of an e-mail rather than attached as a file, which Zendesk otherwise leaves out entirely. This is a pure fetch: it does not write to memory or the document store. Chain a Save to memory step when the file should persist, or feed file_path straight into Extract / Ask AI when it is only needed for this run. file_path is the first match, for the common one-photo-per-ticket case; file_paths and attachments carry them all. Branch on found to handle a ticket that has no attachment at all — which for a support queue usually means asking the customer for a photo rather than guessing.
When to use
Section titled “When to use”When a support ticket may carry a photo the reply depends on — a customer photographing the part they need or the damage they’re reporting — and the next step reads that image. Set content_type_prefix to ‘image/’ when only photos matter, so a signature logo or an attached PDF invoice doesn’t get pulled and read as if it were the subject. For real customer photos only, add min_bytes 20000, exclude_name_contains logo and newest 3 — no code step needed to pick them.
When not to use
Section titled “When not to use”Not for reading the ticket’s text or fields — the trigger payload already carries those. Not a way to persist files: this node keeps nothing, so chain Save to memory if the image must survive the run. Not for fetching an arbitrary URL either; it only reads attachments on the tenant’s own Zendesk.
Inputs
Section titled “Inputs”Configured per use: ticket_id, content_type_prefix, max_files, min_bytes, exclude_name_contains, newest.
Outputs
Section titled “Outputs”Requires
Section titled “Requires”the zendesk integration
Auto-generated from the skill registry (load_skills()). Do not edit by hand.