Menu

Mattering Automations Printful integration

Connect Printful to Mattering Automations: catalog, sync products, order drafts, cost estimates, files, and webhook config as workflow steps, authenticated with a Printful Private Token.

The Mattering Automations Printful integration adds Printful to your automation canvas: browse the product catalog with variants, size guides, and categories, create and manage the sync products in a store, draft and confirm orders, estimate costs, shipping, and tax before anything exists, add files by URL, and manage the store's webhook configuration.

Setup takes a few minutes: create a Private Token in Printful's Developer Portal, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.

The money model is draft-first by construction. Printful: Create Order Draft cannot confirm an order: the integration does not expose Printful's confirm shortcut and strips it if a workflow tries to pass it through, so drafting is always free. Printful: Confirm Order is the single node that submits an order for fulfillment and charges the store's card. Keep it behind a condition, an approval step, or a manual run, and verify the integration with read nodes only.

Before you start

  • A Printful account with a store. Store-scoped nodes need one: either a store connected to a sales channel such as Shopify or Etsy, or a Manual order platform / API store.
  • Access to Printful's Developer Portal (developers.printful.com) to create a Private Token.
  • A Mattering workspace with access to the Automations app.
  • For order flows: a payment method on the Printful account, since confirmed orders are charged to it.

Create a Printful Private Token

Mattering authenticates to Printful with a Private Token, sent as a bearer credential on every request. Private Tokens are Printful's path for automating your own store, with no OAuth flow involved; you choose the token's scopes and expiration date when creating it.

Open Printful's Developer Portal and go to Tokens (developers.printful.com/tokens).
Create a Private Token, select the scopes your automations need, and choose an expiration date.
Copy the token.
Printful Private Tokens expire on the date chosen at creation and cannot be refreshed, only replaced. Pick a generous expiry for long-lived automations and note the date somewhere the team will see it: when the token lapses, every Printful node starts returning 401s at once.

Connect Printful to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Printful from the list.
Click Create new credential, paste your Private Token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls Printful's stores endpoint and confirms the token authenticates.
Click Connect. All 33 Printful nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Printful section should list the query and action nodes. Drop Printful: List Stores onto the canvas and run a test step. It takes no parameters and is a safe, read-only call; a successful response lists the stores the token can reach with their ids. If the token is account level, note the store id, because the store-scoped nodes need it.

To confirm the rest of the surface, run Printful: List Catalog Products for the catalog, or Printful: Estimate Order Costs with a test recipient and item, which prices an order without creating anything. Everything in the verify path is read-only or a pure calculation; nothing here can reach Printful: Confirm Order, which is the only node that spends money.

Node reference

33 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 20

Printful: Calculate Shipping Rates

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

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

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

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

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

printful_get_category

Get a single catalog category by numeric id.

Printful: Get File

printful_get_file

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

Printful: Get Order

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

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

printful_get_store

Get basic information about one store by its numeric id.

Printful: Get Sync Product

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

printful_get_sync_variant

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

Printful: Get Webhook Config

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

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

printful_list_categories

List all catalog categories (a tree via parent_id).

Printful: List Countries

printful_list_countries

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

Printful: List Orders

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

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

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

printful_list_tax_countries

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

Action nodes 13

Printful: Add File

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

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

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

printful_create_order

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

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

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

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

printful_delete_sync_variant

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

Printful: Disable Webhooks

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

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

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

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

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.

Using the integration

On the automation canvas

Printful nodes chain with every other node: a scheduled Printful: List Orders sweep can close a task in Mattering Productivity when an order reaches fulfilled, new artwork can become a sync product with a review task attached, and Printful: Calculate Shipping Rates can quote delivery options before an order exists.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can browse the catalog, price prospective orders, and read order status through the same nodes your workflows use. The catalog, size guide, and estimate nodes are read-only or pure calculations, which makes them the safest Printful surface to hand an agent.

The draft-first order model

Printful only charges for confirmed orders, and the integration leans into that: Printful: Create Order Draft assembles a complete order that sits unbilled, and the confirm shortcut is structurally blocked on both create and update, so a draft cannot slip into fulfillment. Printful: Confirm Order is the deliberate second step that submits for fulfillment and charges the card. Printful: Cancel Order exists but stops working once an order is in process, so gate the confirm step rather than planning to cancel.

store_id on account level tokens

Printful tokens come in two shapes. A store level token is bound to one store and needs nothing extra. An account level token spans stores, so Printful requires each store-scoped call to name its target: the store-scoped nodes carry an optional store_id field for this, and Printful answers 400 asking for it when it is missing. Printful: List Stores returns the ids once; reuse the value across the workflow.

Files by URL, referenced by id

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 at all, so URL is the only path and workflow payloads stay light. The returned file id is what sync product and order item print files reference, and Printful: Get File reports processing status and previews.

One webhook config per store

Printful models webhooks as a single configuration object per store, not a subscription list. Printful: Get Webhook Config reads the delivery URL and enabled event types, Printful: Set Webhook Config replaces the whole object, and Printful: Disable Webhooks clears it. There is no inbound Printful trigger in this integration; to react to order changes, poll Printful: List Orders on a schedule.

Troubleshooting

Test Connection fails with a 401
The token is invalid, expired, or picked up stray whitespace when pasted. Printful Private Tokens expire on the date set at creation and cannot be refreshed, so if this integration worked before and suddenly every node fails with 401s, expiry is the first suspect. Create a fresh token in the Developer Portal and update the credential on the connector.
Test Connection passes but a node returns a 403 or permission error
The token is under-scoped. The connection test only lists stores, so a token missing other scopes passes it while the nodes needing those scopes are refused. Scopes are fixed at creation: create a new token with the scopes your automations need and update the credential.
A node returns a 400 mentioning the store id
The token is account level and the node did not say which store it targets. Set the node's store_id field with a value from Printful: List Stores. Store level tokens never need this, which is why the same workflow can behave differently across credentials.
An order draft was created but nothing is being fulfilled
That is the design working. Printful: Create Order Draft leaves the order unconfirmed and unbilled on purpose; fulfillment starts only when Printful: Confirm Order submits it. If the draft was reviewed and should ship, run the confirm node; if drafts are piling up unreviewed, route their ids into an approval task so a person clears them.
Printful: Cancel Order is refused
Cancellation only works while an order has not entered production; once its status is inprocess the API can no longer cancel it, and a canceled order can only be resubmitted, not reopened. Check status with Printful: Get Order first. This narrow window is the reason to gate Printful: Confirm Order rather than relying on cancel as an undo.
Printful: Add File fails when given a URL
Printful fetches the file server-side, so the URL must be publicly reachable: no login, no expired signed link, and a direct file response. Fix the URL or host the file somewhere public. There is no base64 alternative, because the v1 API has no multipart upload; URL is the only path.
An order or file lookup by external id returns a 404
External id references must be prefixed with @ in the id field (for example @my-order-123); without the prefix Printful treats the value as its own numeric id and finds nothing. Also confirm the record belongs to the same store the token or store_id points at.
A boolean filter behaves as if it were always true
Printful's API parses the literal string "false" as true, so the integration serializes booleans as 1 and 0 on the wire. If a hand-built HTTP call outside these nodes shows that behavior, that is why. Within the Printful nodes, set booleans with the actual toggle rather than typing text into an expression.

Printful is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products