Printcart icon

Printcart

Consume Prinrcart API

Actions83

Overview

This node integrates with the Printcart API to manage webhooks related to various events and topics within the Printcart platform. Specifically, the Create Webhook operation allows users to register a new webhook by specifying an event type (such as HTTP methods like POST, PUT, DELETE), a callback URL where notifications will be sent, and a topic that categorizes the webhook (e.g., designs, products, projects).

Common scenarios for this node include automating workflows triggered by changes in Printcart resources—for example, triggering downstream processes when a new product is created or a design is updated. This enables real-time synchronization between Printcart and other systems.

Practical example:

  • Automatically notify an external system whenever a new design is posted by creating a webhook with event type POST and topic designs. The external system receives updates at the specified callback URL.

Properties

Name Meaning
Authentication Method of authentication; currently supports only "API Token".
Event The HTTP event type that triggers the webhook. Options: DELETE, DELETE BATCH, POST, POST BATCH, PUT, PUT BATCH.
Callback Url The URL to which the webhook payloads will be sent when the event occurs.
Topic The category/topic of the webhook. Options: designs, products, projects, sides, templates.

Output

The node outputs a JSON array containing the response from the Printcart API after creating the webhook. The structure typically includes details about the newly created webhook such as its ID, event type, callback URL, topic, and possibly status or metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API token credential for authenticating requests to the Printcart API.
  • The node makes HTTPS requests to the Printcart API endpoints, so network connectivity to api.printcart.com is necessary.
  • No additional environment variables are required beyond the API token credential configured in n8n.

Troubleshooting

  • Authentication errors: If the API token is invalid or missing, the API will reject requests. Ensure the API token credential is correctly set up in n8n.
  • Invalid callback URL: The callback URL must be a valid, reachable URL. Invalid URLs may cause webhook creation to fail or the webhook to not function properly.
  • Unsupported event or topic values: Only the predefined event types and topics are accepted. Using unsupported values will result in API errors.
  • Network issues: Failure to reach the Printcart API endpoint due to network problems will cause request failures.
  • Error messages from API: The node surfaces error messages returned by the Printcart API. Review these messages for clues on misconfiguration or invalid parameters.

To resolve common errors, verify credentials, input parameters, and network connectivity.

Links and References

Discussion