Supported Webhooks Events in printIQ
Summary
printIQ supports a variety of events that can trigger webhook calls or hot folder drops to external systems. These events allow real-time communication and automation with third-party platforms when specific actions occur within printIQ.
This article provides a full list of supported events and instructions on how to enable them.
How to Enable Webhooks or Hot Folder Events
To enable any supported event:
Contact the printIQ team with one of the following:
For webhooks: Provide a publicly accessible POST endpoint URL that can receive JSON or XML data.
For hot folders: Provide a folder path linked to a configured storage location in printIQ (either Azure Blob Storage or FTP).
The printIQ team will link the selected event(s) to your endpoint or hot folder location.
Supported Events List
CreateCustomer – Triggered when a customer is created or updated. Sends a Customer object.
CreateCustomerContact – Triggered when a customer contact is created or updated. Sends a CustomerContact object.CreateCustomerAddress – Triggered when a customer address is created or updated. Sends a CustomerAddress object.
CreateQuote – Triggered when a quote is created or updated to “Awaiting Acceptance” or “Printed.” Sends a QuoteDetails object.
CreateJob – Triggered when a quote is accepted. Sends an AcceptanceDetails object with the new job.
CompleteJob – Triggered when a job is marked as complete. Sends an AcceptanceDetails object.
RejectQuote – Triggered when a quote is rejected. Sends a QuoteDetails object.
ExpireQuote – Triggered automatically when quotes expire via a scheduled service. Sends a QuoteDetails object.
DiscardQuote – Triggered when a quote status is changed to rejected. Sends a QuoteDetails object.
ExportInvoice – Triggered when an invoice is exported. Sends an Invoice object.
FailCxmlJob – Triggered when a CXML order fails. Sends a JobFailData object.
ExportPurchaseOrder – Triggered when a purchase order is exported. Sends a PurchaseOrder object.
FailXMPieJob – Triggered when an XMPie or custom CSV import fails. Sends a JobFailData object.
CreateJobXml – Triggered when a quote is accepted and is not a ganged job. Sends an AcceptanceDetails object in XML format.
UpdateJobStatus – Triggered when a job status is updated. Sends an AcceptanceDetails object.
UpdateDispatchStatus – Triggered when a dispatch status changes. Sends one event per job in dispatch. Sends an AcceptanceDetails object.
RequestQuoteApproval – Triggered when a quote status changes to "Requires Approval." Sends a QuoteDetails object.
UpdateOrderStatus – Triggered when a sales order status is updated. Sends an AcceptanceDetails object.
CompleteOrder – Triggered when a sales order is marked as complete. Sends an AcceptanceDetails object.
InventoryPOStatusChange – Triggered when an inventory purchase order status is updated. Sends an InventoryPurchaseOrder object.
OutsourcePOStatusChange – Triggered when an outsource purchase order status is updated. Sends an OutsourcePurchaseOrder object.
InventoryTransactionInserted – Triggered when a new inventory transaction is inserted. Sends an InventoryTransaction object.
UpdateJobStatus_Xml – Triggered when a job status is updated. Sends an AcceptanceDetails object in XML format.
AcceptQuote – Triggered when a quote is accepted. Sends a QuoteDetails object.
CreateConsignment – Triggered when a consignment is created. Sends a Consignment object.
AcceptanceCreated – Triggered when a quote is accepted. Sends an AcceptanceDetails object.
SalesItemUpdated – Triggered when a sales item or its linked inventory item is updated. Sends a SalesItem object.
ProductUpdated – Triggered when a simplified product is created or updated. Sends a ProductDetail object.
UpdateSalesOrderStatusLine – Triggered when a sales order item's status is updated. Sends an AcceptanceDetails object for each affected item.
Payload Format
Most events deliver data in JSON.
Specific events (e.g.,
CreateJobXml,UpdateJobStatus_Xml) send data in XML format.
Best Practices
Your endpoint must accept HTTP POST requests and return a 2xx response to confirm receipt.
Ensure your system can handle the corresponding object schema as expected by printIQ.
Test in a UAT environment before enabling in production.
Related Articles
printIQ Integration toolbox
Integration Toolbox Getting started with integration and API overview Access printable attachment at the top or bottom of this article depending on your browser. Introduction When it comes to workflow and integration, everyone’s requirements are ...Setting Up Infigo Integration with printIQ
Summary This article outlines the steps required to configure your Infigo platform to integrate with printIQ. Most of the setup is performed within the Infigo environment. Note: The printIQ team does not manage the Infigo-side configuration. Please ...IQ Product Setup for Infigo
Infigo & Print IQ Product Integration Brief Description Infigo provides a web-to-print engine that integrates with IQ to create quotes and jobs inside of your IQ instance from "web orders" created on the Infigo website. The Infigo site has a product ...API (SOAP) – Job XML highlights
Introduction The printIQ Job XML contains many elements, attributes and values to allow automated processing by supported production integration systems. As your third party system receives the Job XML from printIQ, use the below tags as guides to ...Tilia Phoenix Integration - Gang Module
Overview The printIQ Gang Module allows an operator to filter jobs by a combination of status, stock and finishing options. The filtered jobs can be exported as a batch to import into Tilia Phoenix imposition software. Here the user can create ...