Printcart trigger Trigger

Handle Printcart Worksuite events via webhooks

Overview

This node acts as a webhook trigger for Printcart Worksuite events. It listens for specific event notifications sent via webhooks from the Printcart service and triggers workflows in n8n accordingly. This is useful for automating processes that depend on changes or additions within the Printcart system, such as when new projects, products, or sides are added.

Practical examples include:

  • Automatically updating an internal database or CRM when a new project is added in Printcart.
  • Triggering notifications or further processing when a new product is created.
  • Initiating quality checks or design workflows when a new side (e.g., print side) is added.

Properties

Name Meaning
Event The Printcart event(s) to listen for. Multiple options can be selected: "Project Added", "Product Added", "Side Added".

Output

The node outputs the JSON payload received from the Printcart webhook in the json field of the output data. This payload contains details about the triggered event, allowing subsequent nodes in the workflow to process this information.

No binary data output is produced by this node.

Dependencies

  • Requires access to the Printcart API to manage webhook registration.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests to the Printcart API.
  • Uses the printcartApiRequest helper function to interact with the Printcart API endpoints.

Troubleshooting

  • Webhook Registration Issues: If the webhook does not trigger, ensure the node has successfully registered the webhook URL with Printcart. Check API credentials and network accessibility.
  • Event Mismatch: Make sure the selected events in the node properties match the events sent by Printcart. Note that the option "Side Added" has a value "side Added" with a space, which might cause issues if the API expects a different format.
  • API Request Failures: Errors during webhook creation or deletion may indicate invalid credentials or connectivity problems. Verify API keys and endpoint availability.
  • Payload Format Changes: If downstream nodes fail to process the webhook data, confirm that the Printcart webhook payload structure has not changed.

Links and References

Discussion