Menu
Mattering Automations connector

A Printful MCP where creating an order never charges a card

Connect one Private Token and the Printful catalog, sync products, orders, files, and webhooks become workflow steps for visual automations and AI agents. Order creation is draft-only by design: the one node that charges the store's card is a separate, deliberate step you gate however you like.

33 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Printful MCP connector does

The Printful connector for Mattering Automations is 33 nodes across the v1 API: stores, the product catalog (products, variants, size guides, and categories), the sync product lifecycle (create, update, and delete products and variants in a store), the order lifecycle (draft, update, confirm, cancel, plus pure cost and shipping calculations), File Library uploads by URL, the store's webhook configuration, and the countries and tax reference data that order addresses need.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer what a product would cost to fulfill, which variants are in stock, and where an order's shipment is, without anyone opening the Printful dashboard.

Because Mattering is a work platform rather than middleware, print-on-demand work lands somewhere useful by default: a scheduled order sweep can close tasks or update records in a Mattering database when orders reach fulfilled, and new artwork can become a draft product with a review task attached, all on one canvas next to the rest of the work.

The money boundary is structural, not advisory. Printful only charges for confirmed orders, and Printful: Create Order Draft cannot confirm: the connector does not expose Printful's confirm shortcut and actively strips it if a workflow tries to smuggle it in, so a draft is always just a draft. Printful: Confirm Order is the single node that submits an order for fulfillment and charges the store's card. Put a condition, an approval step, or a manual run in front of it, never a bare trigger.

One connection, three surfaces

  • Visual automations. Drag Printful nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Printful node, ready to drop on the canvas

33 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 20

Printful: Calculate Shipping Rates

Calculate the available shipping methods and rates for a prospective shipment without creating anything. Returns each method's id (usable as the shipping field on orders), rate and delivery day estimates. A POST, but purely a calculation.

Printful: Calculate Tax Rate

Calculate the sales tax rate for a recipient address. A POST, but purely a calculation with no side effects.

Printful: Estimate Order Costs

Estimate the full costs of a prospective order (items, print costs, shipping, taxes) without creating anything. A POST, but purely a calculation with no side effects. The safe way to price an order before drafting it.

Printful: Get Catalog Product

Get a single catalog product with its full variant list (size and color combinations with prices and stock status).

Printful: Get Catalog Variant

Get a single catalog variant (a specific size and color of a product) with price, stock and material info, plus its parent product.

Printful: Get Category

Get a single catalog category by numeric id.

Printful: Get File

Get a File Library file's metadata, processing status and preview URLs by id.

Printful: Get Order

Get a single order with items, status, costs and shipment tracking. Reference by Printful order id or by external id prefixed with @.

Printful: Get Product Size Guide

Get the size tables of a catalog product (measure yourself and product measure tables) in inches or centimeters.

Printful: Get Store

Get basic information about one store by its numeric id.

Printful: Get Sync Product

Get a single sync product with all of its sync variants (the variant ids, retail prices and print files).

Printful: Get Sync Variant

Get a single sync variant with its catalog link, retail price and print files.

Printful: Get Webhook Config

Get the store's webhook configuration: the delivery URL and the enabled event types. Printful keeps one configuration object per store, not a list of subscriptions.

Printful: List Catalog Products

List every product model in the Printful catalog (tees, mugs, posters and so on), optionally filtered by category. Large response. The catalog ids here are what sync products and on-the-fly order items reference.

Printful: List Categories

List all catalog categories (a tree via parent_id).

Printful: List Countries

List the countries and their states with the codes used in recipient addresses (country_code, state_code).

Printful: List Orders

List the orders of a store (paginated). Filter by status: draft, pending, failed, canceled, inprocess, onhold, partial or fulfilled. Account level tokens must set store_id.

Printful: List Stores

List the stores the Printful token can access. Takes no parameters, so this is the connector's auth probe: run it first to confirm the token works and to get the store_id that Account level tokens must send on store-scoped Printful nodes.

Printful: List Sync Products

List the sync products of a store (paginated). Account level tokens must set store_id. Filter by sync status or catalog category.

Printful: List Tax Countries

List the countries and states for which Printful requires tax calculation.

Action nodes 13

Printful: Add File

Add a file to the store's File Library from a publicly reachable URL (Printful downloads it; plain JSON, no multipart). If a file with the same URL already exists it is reused. The returned id can be referenced by order items and sync variant print files.

Printful: Cancel Order

Cancel a draft or pending order. Irreversible: a canceled order cannot be reopened, only recreated. If the order was already charged, the amount is refunded to the store owner's credit card. Orders in the inprocess state can no longer be canceled through the API.

Printful: Confirm Order

Confirm a draft order for fulfillment. This costs real money: Printful's docs say the store owner's credit card is charged when the order is submitted for fulfillment, and production starts. Cancel is only possible until the order reaches the inprocess state. The safe path is draft first: create with Printful: Create Order Draft, review, then confirm.

Printful: Create Order Draft

Create an order as a DRAFT. Drafts are free: Printful only charges orders that have been confirmed, and this node never confirms (the API's confirm-on-create shortcut is deliberately not exposed). Review the draft, then run Printful: Confirm Order to submit it for fulfillment and be charged. Use Printful: Estimate Order Costs first to price it without creating anything.

Printful: Create Sync Product

Create a product in the store from catalog variants and print file URLs. Creating a product does not order or charge anything; delete it to undo. Get catalog variant ids from Printful: Get Catalog Product.

Printful: Create Sync Variant

Add a new variant to an existing sync product from a catalog variant id and print files. Delete the variant to undo.

Printful: Delete Sync Product

Permanently delete a sync product and all of its variants from the store. Irreversible. Orders already placed are not affected.

Printful: Delete Sync Variant

Permanently delete a single sync variant from its product. Irreversible; recreate it to restore.

Printful: Disable Webhooks

Remove the store's entire webhook configuration; event delivery stops immediately. The previous URL and event type list are not recoverable through the API, so treat this as irreversible (set a new configuration to resume).

Printful: Set Webhook Config

Set the store's webhook configuration. REPLACES any existing configuration (one config per store). Event types include package_shipped, package_returned, order_created, order_updated, order_failed, order_canceled, product_synced, product_updated, product_deleted, order_put_hold, order_remove_hold, order_refunded and stock_updated. Failed deliveries are retried in increasing intervals.

Printful: Update Order

Update an unsubmitted (draft or failed) order. Send only the fields to change. If an items array is given it is merged by item id: existing ids are updated, missing ids are deleted, new entries are created. Never bills; the API's confirm-on-update shortcut is deliberately not exposed.

Printful: Update Sync Product

Update a sync product. CAREFUL with sync_variants: Printful treats the array as the complete new variant list, so include the id of every existing variant you want to KEEP; variants left out are deleted. Omit sync_variants entirely to leave variants untouched.

Printful: Update Sync Variant

Update a sync variant. Send only the fields to change: the catalog variant mapping, print files, retail price, SKU or options.

Connecting Printful takes one credential

Printful issues Private Tokens from its Developer Portal at developers.printful.com/tokens. A Private Token is for automating your own store, needs no OAuth flow, and is sent as a bearer credential on every request. Tokens carry the scopes and the expiration date you choose at creation, and an expired token cannot be refreshed, only replaced.

1

In the Printful Developer Portal (developers.printful.com/tokens), create a Private Token with the scopes your automations need and note its expiration date.

2

In Mattering Automations, open Connectors, click Add Connector, choose Printful, and create a credential with that token.

3

Click Test Connection. Mattering calls Printful's stores endpoint and confirms the token authenticates.

4

All 33 Printful nodes appear in the canvas palette. Run Printful: List Stores first: if the token is account level, every store-scoped node needs the store id it returns.

Common uses for the Printful MCP

Catalog research an agent can do

Printful: List Catalog Products, Printful: Get Catalog Product, and Printful: Get Catalog Variant answer what exists, in which sizes and colors, at what price, and whether it is in stock. Add Printful: Get Product Size Guide and an assistant can answer sizing questions from the actual measure tables, all read-only.

Pricing an order before it exists

Printful: Estimate Order Costs prices a prospective order end to end (items, print costs, shipping, taxes) and Printful: Calculate Shipping Rates returns each shipping method with rate and delivery estimates. Both are POSTs but pure calculations: nothing is created, nothing is charged. This is the safe way to quote fulfillment.

Artwork to store product without the clicking

Printful: Add File pulls artwork into the File Library straight from a URL, and Printful: Create Sync Product builds a store product with variants referencing catalog variant ids and print files. Creating or deleting sync products orders nothing and charges nothing.

Drafts that wait for a person

Printful: Create Order Draft assembles a real order that sits unconfirmed and unbilled. The confirm shortcut is structurally blocked on this node, so the draft cannot accidentally go to fulfillment. A person, an approval step, or a downstream condition decides when Printful: Confirm Order runs.

Order status the team can see

Run Printful: List Orders on a schedule, filter by status, and route what changed into tasks, records, or messages: an order that reaches fulfilled can close its task, and one that lands in failed can open a ticket for a person. Printful: Get Order adds shipment tracking per order, addressable by Printful id or your own external id.

Webhook configuration managed from the canvas

Printful keeps one webhook configuration per store rather than a list of subscriptions. Printful: Get Webhook Config, Printful: Set Webhook Config, and Printful: Disable Webhooks manage that single object: the delivery URL and which event types fire to it.

Example: New artwork becomes a store product and a priced draft, with a person before any charge

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a form submission or scheduled check delivers an image URL, a product title, and a recipient address.

2

Printful: List Stores supplies the store id that account level tokens must pass to store-scoped nodes.

3

Printful: Add File pulls the artwork into the File Library from the URL and returns the file id.

4

Printful: Create Sync Product builds the store product with variants referencing catalog variants and the uploaded print file.

5

Printful: Estimate Order Costs prices a prospective order for the recipient so the numbers are known before anything exists.

6

Printful: Create Order Draft assembles the order as a draft. Nothing is billed: the draft waits, and only a separately gated Printful: Confirm Order, behind an approval task in Mattering Productivity, ever charges the card.

Printful MCP questions, answered

What Printful operations are supported?

33 nodes on the stable v1 API: stores, the catalog (products, variants, size guides, categories), sync products and variants (create, read, update, delete), orders (draft, update, confirm, cancel, list, plus pure cost, shipping, and tax calculations), File Library additions by URL, the store webhook configuration, and countries and tax reference data. Deliberately not shipped: the Ecommerce Platform Sync API (a read-only mirror for platform-synced stores), the Mockup Generator, product template management, warehouse operations, and Printful's OAuth app flow, since Private Tokens cover automating your own store.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Can this connector charge real money by accident?

It is built so that it cannot do so silently. Printful only charges for confirmed orders. Printful: Create Order Draft cannot confirm: the connector does not expose Printful's confirm parameter and strips it if a workflow tries to pass it through, so drafting is always free. Printful: Confirm Order is the one node that submits an order for fulfillment and charges the store's card, and it is flagged so it can be gated behind a condition, an approval step, or a manual run. Printful: Cancel Order exists, but cancellation becomes impossible once an order is in process, so gate the confirm step rather than counting on cancel.

What is store_id and when do I need it?

It depends on the token type. A store level token is bound to one store and needs nothing extra. An account level token can access several stores, so Printful requires it to say which store each call targets; the store-scoped nodes take an optional store_id field for exactly this, and Printful returns a 400 asking for it if it is missing. Printful: List Stores returns the ids.

Can a Printful order trigger a workflow?

Not as a trigger node in this connector. The webhook nodes manage the store's webhook configuration rather than receiving events, so there is no inbound Printful trigger. The honest pattern today is polling: run Printful: List Orders on a schedule, filter by status, and act on what changed. The configuration you manage can point Printful's events at any URL you operate.

How do file uploads work?

By URL only. Printful: Add File gives Printful a publicly reachable URL and Printful fetches the artwork server-side into the File Library; the v1 API has no multipart upload anywhere, so there is no base64 fallback to bloat workflow payloads. The returned file id is what sync product print files reference.

Why did my token stop working after months of use?

Printful Private Tokens carry an expiration date chosen when they are created, and an expired token cannot be refreshed, only replaced. Generate a new token in the Developer Portal and update the credential on the connector. When creating tokens for long-lived automations, pick a generous expiry and note the date somewhere the team will see it.

What do orders cost and where do the numbers come from?

The connector never invents prices: Printful: Estimate Order Costs returns Printful's own itemized numbers (product, print, shipping, tax) for a prospective order, and Printful: Calculate Shipping Rates prices each shipping method separately. Both are free, side-effect-free calculations you can run as often as needed before drafting anything.

33 nodes waiting on the canvas

Put Printful to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Printful is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products