Ask for it
Tell it where the files should go:- “Copy every finished file to our S3 bucket print-jobs under the folder filecheck/.”
- “Email the print files to prepress@printshop.com when a job is done.”
- “Put a JSON file with the order details next to each PDF in the hotfolder, so our MIS picks up both.”
- “Call our Zapier hook when a proof is approved.”
What the assistant does
1
Builds the destination
It reads the destination schema and saves one for the transport you named:
sftp, ftp, s3, email or webhook, with the folder or key layout you described. Folder paths take tokens such as {orderId}, {sku} and {product}, and hotfolders can get a metadata sidecar next to each print file, uploaded after it so the watcher never picks up a half-written file.2
Tests it, when you agree
A test delivery sends a sample order (TEST-1001, a one-page
Sample_Product.pdf) through the real transport and reports whether it arrived. Hotfolders really receive the file and email really goes out, where your print workflow may pick it up, so the assistant asks first.3
Adds it to the workflow
It adds the destination to the workflows that should deliver there. Delivery runs once per job, after it is done; each destination is tried once, and a failure on one doesn’t stop the others.
Webhooks
Webhooks tell your own systems when something happens on your account: a job created, completed or delivered, a proof ready or approved, settings changed, credits running low. The assistant lists the events, creates the webhook for the ones you want, and sends it a signed test event to show what your receiver answers. Each call is a JSON POST signed withX-FileCheck-Signature; see Webhooks for verifying it.