Printful Integration with Jumpseller via Zapier

Connect Jumpseller with Printful via Zapier to automatically create fulfillment orders when a purchase is marked as paid. The action to Printful is performed through Webhooks by Zapier, sending a direct POST to the Printful API.

⚡ Create Zap · Jumpseller → Printful

Key concept

Each product variant in Jumpseller must have the exact Printful catalog variant identifier assigned to it. This is stored in a custom field of type select, and Zapier reads it when the order event is received to include it in the payload sent to Printful.

No catalog lookups or dynamic mappings are performed: Jumpseller acts as the single source of truth.

Step 1: Set up the custom field in Jumpseller

Before creating the Zap, you need to configure the field that will store the Printful ID.

1. Go to Settings → Custom Fields → Variants
2. Create a Select type field named printful_catalog_variant_id
3. Add one option per Printful catalog variant you use, for example:
   • 4011 — Black T-shirt / S
   • 4012 — Black T-shirt / M
   • 4013 — Black T-shirt / L
4. Save the field

Then, for each product:

1. Go to the corresponding variant
2. Assign the correct value for the printful_catalog_variant_id field
3. Repeat for all size and color combinations

Each size and color combination must have its own Printful identifier.

Step 2: Configure the Zap in Zapier

Trigger: Paid order in Jumpseller

• App: Jumpseller
• Event: New Paid Order
• Connect your Jumpseller account and test the trigger with a real or test order to verify that the order fields appear correctly

Action: Create order in Printful via Webhooks

• App: Webhooks by Zapier
• Event: POST
• URL: https://api.printful.com/orders
• Headers:
  • Authorization: Bearer YOUR_PRINTFUL_API_KEY
  • Content-Type: application/json Body (JSON):

{
  "recipient": {
    "name": "{{customer_name}}",
    "address1": "{{shipping_address_line1}}",
    "city": "{{shipping_city}}",
    "country_code": "{{shipping_country_code}}",
    "zip": "{{shipping_zip}}"
  },
  "items": [
    {
      "catalog_variant_id": "{{variant_custom_fields_printful_catalog_variant_id}}",
      "quantity": "{{quantity}}",
      "files": [
        {
          "url": "{{product_options_artwork_url}}"
        }
      ]
    }
  ]
}

The names in `` are references to the Jumpseller trigger fields as they appear in Zapier. Adjust them to match the exact names exposed by the trigger when you run the test.

Print files

Printful requires print files to be available via a public URL at the time of the order. This value is obtained from the artwork product option configured in Jumpseller.

Make sure the file URL is accessible without authentication.

Advantages of this approach

• No code or custom server required
• Visual configuration from Zapier
• Deterministic and auditable flow
• Errors visible from the failed Zaps history

Important considerations

• The printful_catalog_variant_id field must be assigned on all product variants before receiving orders
• The print file must be publicly accessible at the time of the order
• If any of this data is missing, the Zap will fail and be recorded in the Zapier history
• Orders created via API in Printful require manual confirmation before entering production, unless you have automatic fulfillment enabled in your Printful account

Need help implementing this integration?

If you need to adapt this integration to a more advanced workflow, you can request professional support. This is useful if you need:

• Conditional logic by product or variant
• Error handling and automatic notifications
• Automatic mockup generation
• Integration with other systems

Approximate price: professional services from 400 EUR.

Request professional help