Print Zendesk Ticket Attachments Automatically with PrintNode

6 min setup
No coding required
Runs automatically

Stop manually downloading and printing ticket files. This workflow grabs PDF attachments from new Zendesk tickets and sends them straight to your PrintNode printer. Perfect for support teams handling physical documents, shipping labels, or customer forms that need immediate printing. Set it up once and watch your printer handle everything while you focus on solving customer problems.

zendesk logo icon
Ticket Created
Loop over comment's attachments
Create Print Job

You're in good company

"MESA has been a game changer for us. And, if you ever get stuck, their support team is always super helpful."

  • Ico star
  • Ico star
  • Ico star
  • Ico star
  • Ico star
PetFriendly

"It's like Zapier but exactly designed for Shopify. I have been able to complete all the workflows that I've needed."

  • Ico star
  • Ico star
  • Ico star
  • Ico star
  • Ico star
Zailys

"The MESA team has been amazing at helping us set up our automations. We would highly recommend this app!"

  • Ico star
  • Ico star
  • Ico star
  • Ico star
  • Ico star
Rothy's

How it works

5 steps to start automatically printing Zendesk ticket attachments to your physical printer

zendesk logo icon

Ticket Created

App connector: Zendesk • Time to complete: 0 minutes (Auto-configured)
Why this matters: This trigger monitors your Zendesk account and starts the workflow whenever a new support ticket is submitted, ensuring no ticket attachments are missed.

When a customer or team member creates a new ticket in Zendesk, this trigger captures all the ticket details including ID, subject, requester information, and associated data. The trigger runs automatically in the background and requires no configuration from you. It passes the ticket information to the next step so the workflow can find and process any attachments that were included with the ticket.

Get List of Comments

App connector: Zendesk • Time to complete: 0 minutes (Auto-configured)
Why this matters: This step retrieves all comments associated with the ticket to identify which ones contain file attachments that need to be printed.

The system automatically pulls the complete list of comments from the ticket, including the initial ticket description and any follow-up responses. This step scans through each comment to locate file attachments, which in Zendesk are stored within individual comments rather than directly on the ticket itself. No configuration is needed as it uses the ticket ID from the trigger to find the right comments.

Loop over ticket's comments

App connector: Loop • Time to complete: 0 minutes (Auto-configured)
Why this matters: This loop processes each comment individually to systematically check for attachments, ensuring no files are overlooked in tickets with multiple comments.

The loop examines every comment retrieved in the previous step, creating a separate processing path for each one. It automatically filters and organizes the comments so the workflow can move through them methodically. This step handles tickets with single comments as well as lengthy conversation threads with dozens of back-and-forth exchanges.

Loop over comment's attachments

App connector: Loop • Time to complete: 0 minutes (Auto-configured)
Why this matters: This nested loop identifies and processes each individual file attachment within each comment, handling cases where customers upload multiple documents at once.

For each comment that contains attachments, this loop creates a separate processing track for every file. It checks that each attachment has a valid content URL before proceeding, filtering out broken or inaccessible files. The loop handles various file types including PDFs, images, and documents, preparing each one for the printing step.

Create Print Job

App connector: PrintNode • Time to complete: 2 minutes
Why this matters: This step sends each attachment file directly to your selected physical printer, completing the automation by producing hard copies of customer documents.

You'll need to configure which PrintNode printer should receive the attachments by selecting from the dropdown menu. The step automatically converts file URLs into print jobs and sends them to your chosen printer using PrintNode's printing service. Make sure your target printer is connected and shows as online in your PrintNode dashboard before selecting it, as the workflow can only print to active, connected devices.

Ready to set this up? It only takes 6 minutes.

Our support team will even help you personalize this workflow for free.

Get started →

Make it your own!

Customize this workflow even further:

Add conditional filters
Set up conditions to only print specific file types (like PDFs) or attachments from certain ticket priorities, preventing your printer from processing unnecessary documents.
Connect multiple printer locations
Extend the workflow to route different ticket types to different printers based on department, urgency, or customer tier using conditional logic steps.
Store attachment records in tables
Save details about printed attachments (filename, ticket ID, print timestamp) in MESA's database tables for tracking and audit purposes.
Send notification emails
Add email steps to notify team members when attachments have been successfully printed, including details about which files were processed and any printing errors.

Common questions

What file types can be printed through this workflow?

Will this print attachments from internal agent comments or only customer submissions?

What happens if the selected printer is offline when an attachment tries to print?

Ready to start automatically printing Zendesk ticket attachments to your physical printer?

7-day free trial • 6 min setup • Cancel anytime

Need help? Our automation experts will help you personalize this workflow for free. Contact support