Pixfizz
E-commercePixfizz is a web-to-print ecommerce platform for personalized products. Agents bring orders in from an outside storefront and start print fulfillment, render personalized product images and production PDFs, and manage galleries, promo codes and gift vouchers.
What This Integration Enables
Most commerce connectors end at a warehouse shelf. Pixfizz ends at a printing press. A wrong SKU can be restocked, while a wrong personalized mug is scrap carrying a customer's misspelled name, so every risk in the workflow reorders around that one fact. FlowRunner agents work the whole path from storefront to press. They hand a customer from your own site into the Pixfizz editor, then read back exactly what that customer typed into the design. They render proofs, start production files, poll them to a real finish, and confirm the order that commits the print run.
The catalog, voucher and calendar surfaces round that out, so a promotion issued in your CRM and a birthday held in another system both reach Pixfizz without anyone retyping them. What FlowRunner adds on top is a clear rule about where the machine stops. Reads, matches and renders run at machine speed. The operations that commit ink, spend a billed render, or issue a voucher whose value can never be edited wait for a person, which is what human-in-the-loop means on a page like this one.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
From storefront to press without a proofing inbox
A personalized order closes in Shopify carrying the Pixfizz project id the customer built in the editor. The agent calls Get Project to confirm the project is saved and its theme and product codes resolve, then Get Project Text Elements to read every word the customer typed. Text that clears the store's review rules goes straight to Create External Order, which confirms the order and starts print fulfillment in a single call. Anything the rules flag stops there and posts to the production channel in Slack with the customer's wording beside the image from Get Project Preview. The clean orders stop waiting behind the questionable ones, which is the whole point.
-
A production pipeline that reports its own failures
Pixfizz spells a failed render "Error ocurred", with one letter missing, and that misspelling is the real value on the wire. A polling loop written against the correct spelling waits forever. The agent calls List Orders on a schedule and Get Production File Status for each open project, then branches on the finished and errored flags this connector supplies rather than on the vendor's spelling. Finished renders hand their download links to the fulfillment step. Failures post to the team with the project and the order behind them. Pixfizz permits one production file per project and refuses Delete Production File outside its own windows, so the agent reports the wait honestly rather than burning a billed render on a retry that would be rejected anyway.
-
Vouchers issued from the campaign that owns them
A loyalty campaign in Airtable holds the customer list and the credit each person is owed. The agent resolves each customer, then calls Create Gift Voucher so the amount behaves as spendable balance across several orders rather than as a single discount. The value is the part that belongs to a person. A voucher balance is immutable once created, and Delete Promocode is refused until the code has expired, so an amount typed one digit too wide can neither be corrected nor withdrawn. The agent posts the full issue list with its totals before it writes anything, a marketing owner approves the run, and codes issued in error are stopped with Update Promocode, which is the only lever Pixfizz actually offers.
Human-in-Loop Highlight
Create External Order is the point of no return in this connector. It confirms the order, moves it into fulfillment, and causes production files to be generated and pushed to the store's configured destination, with no route that undoes any of it. So the proofing agent never calls it on a flagged project. It reads the typed text with Get Project Text Elements, pulls the free preview with Get Project Preview, and posts both into the production channel: "Order 8842, canvas print. Line one reads Happpy Birthday Nan. Send to press, or return it to the customer for a correction?" A person answers, because the agent can read the string and cannot know whether it is a typo or a family joke. The distance between those two answers is one printed object with no second buyer, and a render Pixfizz will not let the flow repeat, because only one production file is permitted per project and Delete Production File is refused outside the vendor's windows. Here the recovery from a bad decision is a wait, not a retry, which is exactly the kind of decision that should have a name attached to it.
Agent Capabilities
63 actionsUsers
3- Get Current User Reads the account the connection is signed in as, along with the links to that user's galleries, projects, orders and promocodes. This connector treats an anonymous answer as a failure rather than handing a flow a null user, because Pixfizz returns one with a success code when credentials are wrong.
- List Users Lists the store's users a page at a time. It needs an administrator connection and is the reliable proof that the connection actually has administrator rights.
- Sync External User Creates, updates and signs in a Pixfizz user from your own system's record in one idempotent call. This is the handoff a custom storefront is built on, and it is deliberately scoped to storefront handoffs only, because a user reached this way can never sign in with an email and password afterwards.
Projects
8- List User Projects Lists the personalized projects belonging to one customer, which Pixfizz calls books on the wire. Useful for account pages and for retention flows that surface unfinished designs.
- List My Projects Lists the projects of the user the connection is signed in as. On an administrator connection that is the administrator's own projects rather than the whole store.
- Get Project Reads one project with its name, saved and ordered flags, theme and product codes, and chosen variants. The step a fulfillment flow runs before it commits anything.
- Create Project Creates a personalized project from a design and a product and returns the id that goes into the editor URL. This is how a workflow hands a customer into the editor with the right product already loaded.
- Update Project Renames a project or marks it saved or ordered. Only the three fields that are safe to write are exposed, because writing a project's structure through this route corrupts it in the editor.
- Copy Project Copies a project into a new and fully independent one and returns the new id. Used for reorders and for versioning a design without disturbing the original.
- Get Project Text Elements Reads the text a customer typed into a project, element by element. This is the read that makes proofing possible before anything reaches a press.
- Get Project Preview Fetches a project's preview image and stores it in FlowRunner so a later step or an email can use the URL. It is a small proofing thumbnail rather than a print file.
Production Files
3- Create Production File Starts the render of a project into a print ready production PDF and returns the job to poll. Most Pixfizz contracts bill this per call, so a workflow should reach it once with intent rather than inside a retry loop.
- Get Production File Status Reads the state of a project's render and, once it finishes, the download links for each generated file. This connector adds explicit finished and errored flags so a flow can branch without matching the vendor's misspelled failure status.
- Delete Production File Deletes a project's production file, which is the only way to make room for a re render. Pixfizz allows it only inside narrow windows, so a repair flow has to wait rather than retry.
Orders
6- List Orders Lists orders across the whole store a page at a time, on an administrator connection. The scheduled read behind production monitoring and reconciliation.
- Get Order Reads one order with its status, paid flag, totals, order lines and custom fields.
- Create Order From Cart Turns an existing Pixfizz cart into an order for one customer. This is the route for a storefront running on Pixfizz itself, where the cart already carries its lines.
- Update Order Updates an order's notes, status, paid flag or custom fields. Pixfizz ignores any other field while still answering with a success, so this operation exposes only what actually takes effect and a flow reads the order back when the change matters.
- Mark Order Shipped Sets an order to the shipped status, which is what triggers Pixfizz's own completion work including the customer emails the store has enabled. It is separate from Update Order because it has effects beyond the field it writes and cannot be undone by setting the status back.
- Create External Order Creates an order from an outside storefront, moves it to confirmed and starts fulfillment. This is the most consequential operation in the service: production files are generated and pushed to the store's fulfillment destination as a result, and the API offers no way back.
Galleries and Images
8- List User Galleries Lists the image galleries belonging to one customer. Every gallery in Pixfizz belongs to a user, so this is how galleries are found.
- List My Galleries Lists the galleries of the user the connection is signed in as.
- Create Gallery Creates an image gallery for one customer, which is where uploaded photos live before they are placed into a project.
- Get Gallery Reads one gallery with its name, owning user and the links to its images.
- Update Gallery Renames a gallery. The name is the only field Pixfizz accepts, so a gallery cannot be moved between users.
- Upload Gallery Image Downloads an image from a URL and uploads it into a gallery, tagging it on the way in. Tags are the only practical way to find an image again in a large gallery, so a flow sets them here.
- List Gallery Images Lists the images in a gallery and optionally filters them by tag. The tag filter has to be sent in one exact shape or the whole gallery comes back instead, which this operation handles.
- Get Image Reads one image's metadata, including its dimensions, tags and owning gallery.
Catalog and Design
6- List Products Lists the store's products with their codes, categories, prices, variants and inventory. The product code on each row is what Create Project takes.
- Get Product Reads one product with its full variant list, pricing, inventory and custom fields, which beats paging the whole catalog to find it.
- Get Design Preview Renders a design with variants and personalization applied without creating a project, and stores the image in FlowRunner. This is how a catalog page or a proof email shows a customer their own name or color before anything is saved.
- List Color Palettes Lists the color palettes available in the store's editor with their named color values. Palettes are read only.
- List Font Palettes Lists the font palettes available in the editor and the fonts each one groups together.
- List Fonts Lists the individual fonts available in the editor with their preview images, which is the flat view rather than the palette grouping.
Promocodes and Gift Vouchers
8- Create Promocode Creates a store wide discount code any customer can use at checkout. The value fields are fixed at creation, so a promotion whose amount later needs correcting has to be recreated rather than edited.
- Create Gift Voucher Creates a voucher for one customer, modeled as a promocode with credit reuse so the amount behaves as a spendable balance across several orders. The balance cannot be topped up afterwards.
- List Promocodes Lists every promocode and gift voucher on the store a page at a time, on an administrator connection.
- Get Promocode Reads one promocode or gift voucher by its numeric id, with its value, usage state and validity window.
- Get Promocode By Code Looks a code up by the string a customer typed rather than by id, which is what a checkout validation step needs. Pixfizz returns expired and spent codes rather than refusing them, so the flow reads the usage fields to decide.
- List User Promocodes Lists the promocodes and vouchers issued to one customer, which is how a remaining voucher balance is found.
- Update Promocode Changes a code's name, spent flag or validity window. Setting a code spent is the practical way to stop a live promotion, because deletion is not permitted until it has expired.
- Delete Promocode Deletes a promocode or gift voucher, which Pixfizz permits only after the code has expired. Order history referencing the code is retained.
Calendars
12- List Site Calendars Lists the store wide calendars an administrator publishes for every customer to use in a calendar product.
- List User Calendars Lists the personal calendars belonging to one customer.
- List My Calendars Lists the calendars of the user the connection is signed in as.
- Create User Calendar Creates a personal calendar for one customer, ready for their own dates.
- Create Site Calendar Creates a store wide calendar every customer can use, such as a public holiday set. It needs an administrator connection and a code.
- Get Calendar Reads one calendar with its name, owning user where it has one, and the link to its dates.
- Update Calendar Renames a calendar and leaves its dates untouched.
- Delete Calendar Deletes a calendar and every date on it, with no route that restores them. A flow that only wants to clear a calendar deletes its dates individually instead.
- List Calendar Dates Lists the dated entries on a calendar, each with its caption and start date.
- Get Calendar Date Reads one dated entry with its caption and start date.
- Create Calendar Date Adds a captioned date to a calendar, which is how birthdays and anniversaries reach a customer's calendar product from another system.
- Delete Calendar Date Removes one dated entry and leaves the calendar and its other dates in place.
Admin Content
9- List Custom Types Lists the store's custom content types, the record definitions a Pixfizz site uses for things like store locations or testimonials.
- Get Custom Type Reads one custom content type with the fields it defines, which is what tells a flow the field names an instance has to fill.
- List Custom Type Instances Lists the records stored under one custom content type.
- Create Custom Type Instance Creates one record under a custom content type, which is how an outside system publishes structured content onto a Pixfizz site. Unknown field names are dropped silently, so a flow reads back when the values matter.
- List Assets Lists the media assets in the store's admin library with the ids a content record references.
- Upload Asset Downloads a file from a URL and uploads it into the store's asset library, returning the asset id. This is the first half of publishing content with an image.
- Update Product Custom Fields Writes custom field values onto a product, which is how an outside catalog pushes its own attributes into Pixfizz. Fields that do not exist on the store are dropped without an error, so verify by reading back.
- Update Design Custom Fields Writes custom field values onto a design. Pixfizz calls a design a theme on the wire, and this operation sends the vendor's own key rather than the word the admin interface shows.
- Update Collection Custom Fields Writes custom field values onto a design collection, which Pixfizz calls a theme category internally.
Frequently Asked Questions
What can FlowRunner do with Pixfizz?
FlowRunner agents can run Get Current User, List Users, and Sync External User in Pixfizz, plus 60 more actions.
Does connecting Pixfizz to FlowRunner require OAuth?
No. Pixfizz connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Pixfizz trigger a FlowRunner workflow automatically?
Pixfizz doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other E-commerce integrations
Start building with Pixfizz
Free plan, no card required. Connect in minutes.