Connect Printix

Printix is cloud print management. It replaces print servers, routes jobs to printers through a small client on each computer, and can hold a job until someone releases it at the device with a card tap or a PIN. A Printix customer environment is called a tenant. StackJack talks to Printix through its Cloud Print API, the same interface Printix documents for integrations.

Connecting Printix to StackJack gives your AI assistant a family of printix_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• See which printers are down — every print queue with the connection status, model, serial number, vendor and location of the printer behind it
• Find a lost print job — jobs across the whole environment, jobs waiting on one printer, and the full detail of a single job
• Answer "who can print to what" — users and guests, the groups that scope printer access, and which user a secure-release card belongs to
• Map the print estate — the sites, the networks behind them, and the SNMP settings printer discovery runs on
• Check the client computers — which workstations are connected and when each one last checked in

It can also make changes, on the Pro tier:

• Send a document to a printer, and clear jobs that were submitted but never printed
• Hand a waiting job to a real person so they can release it themselves at the device
• Set someone up — create a user or a visitor account, and give a person a new sign-in code when they forget theirs
• Manage badges — register a secure-release card against a user, or remove a lost one immediately
• Edit the print estate — create, change and remove groups, sites, networks and the SNMP settings printer discovery runs on

Reading is free. Every change needs the Pro tier, and the ones that cannot be undone are labelled so your AI assistant asks before running them.

Before you start: creating a key can break an integration you already have

This is the most important thing about the Printix connector and it is unusual enough to say first.

Printix allows only one set of Cloud Print API credentials at a time. Creating a new set immediately stops the old one working. If a third-party print integration, a scan workflow or one of your own scripts already uses that key, it will break the moment you create a key for StackJack — with no warning from Printix, and no way for StackJack to detect it.

Check what already uses your Cloud Print API key before you go any further. If something does, plan the switch rather than discovering it.

How StackJack authenticates to Printix

Printix gives you a Client ID and a Client Secret, created in Printix Administrator. You paste both into StackJack.

There is no web address to enter. Printix runs one shared service for every customer and identifies yours by an ID that StackJack reads automatically the first time it connects. The address of the form https://yourcompany.printix.net is the Printix Administrator website you sign in to, not the interface StackJack uses, so there is nowhere to put it and nothing is lost by that.

Behind the scenes StackJack exchanges your Client ID and Secret for a short-lived key roughly once an hour and keeps it fresh on its own. There is nothing to renew on a schedule and nothing for you to rotate.

Choose the application type carefully

Printix does not have permission tick-boxes. Instead it has five separate application types, and each part of the API accepts only some of them. This is the second thing worth understanding before you start, because one set of credentials cannot reach every tool:

Every type can list your Printix environments, which is the first call any of the tools makes.

Most customers start with Cloud Print API, which covers the majority of the tools. If you also want the workstation tools, the single-user and card lookups, or card and user changes, create a second application of that type in Printix and add it to StackJack as its own connection. A customer who wants everything ends up with four connections — that is Printix's design, not a StackJack limitation, and the connections page is built for it.

StackJack asks you which type you created and records your answer so it can show you what that connection reaches. Printix itself decides what each call is allowed to do, so the answer is guidance rather than a restriction.

Steps

1. Check what already uses your Cloud Print API key, as described above. This is the step people skip.
2. Decide which application type you need from the table above.
3. Create the application in Printix Administrator. Sign in as an administrator and create an application of that type. Printix shows you a Client ID and a Client Secret.
4. Copy the Client Secret straight away. Printix shows it when the application is created. Treat it as a password.
5. Check your Secure Print setting. If your environment is set so that all users must print securely, the API will not work at all. Printix's own guidance is to scope that setting with groups instead. Change it before you connect, or the connection test fails for a reason that has nothing to do with your credentials.
6. Enter the details in StackJack. Open Connectors, choose Printix, paste the Client ID and Client Secret, and pick the application type you created.
7. Run a Test Connection. A failure usually means the secret was truncated on copy, the Secure Print setting is blocking the API, or a newer key has already replaced this one.

What to know before your AI uses this connector

Most tools need Printix Premium

Most of what this connector reads requires the Printix Premium product on your Printix environment. Without it the connection still authenticates, but most tools are refused. If everything fails the same way while the connection test passes, this is the first thing to check.

A refusal usually means the wrong application type, not a bad key

If one family of tools is refused while the rest work, the cause is almost always the application type rather than the credentials. The workstation tools are the clearest example: nothing but a Workstation monitoring application can read them, so a Cloud Print API connection is refused every time, no matter how correct the key is. The fix is a second Printix application, added as a second connection — not a new secret.

Reads change nothing; the changes are labelled

The reads change nothing, but they do return your customers' printer, user and network detail, so grant them deliberately.

The changes are a different matter and are labelled accordingly, so your AI assistant asks first. Deleting anything cannot be undone from the API, sending a document puts ink on paper in someone's office, creating a user can email a real person, and giving someone a new sign-in code stops their old one working at every printer straight away.

Three changes replace a record rather than edit it. Updating a site, a network or an SNMP configuration sends the whole record back, so any field left out is cleared. For a network that means the gateway addresses, and a network with no gateways stops matching any printer. For SNMP it means the community strings and the version 3 keys — and Printix never gives the version 3 keys back on a read, so they have to be re-entered from your own records. Ask your AI assistant to read the record first and resend every value.

Printing takes three steps and your AI can only do two of them. It creates the job and gets a one-time upload address back, then something has to upload the actual document to that address — which is Microsoft's or Google's storage rather than Printix's, so StackJack has no tool for it — and only then does the last step release it to the printer. A job created but never uploaded sits in the queue until someone clears it.

Some results are secrets. Creating a user returns that person's PIN, password and sign-in code in plain text, and issuing a new sign-in code returns the code itself. The SNMP settings — read or written — can include the community string or the credentials Printix uses to reach printers. Treat all of those the way you would treat a password, and check before pasting one into a ticket or a report. StackJack does not record these results.

Lists start at page zero

Printix numbers pages from zero, so the first page of any list is page 0 rather than page 1. Each list tool says so, and StackJack asks for a sensible number of rows on your behalf. If a list looks like it is missing its beginning, that is the reason.

Plans and limits

Every read is available on the Free tier. Every change needs Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Printix tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Printix allows 100 requests a minute, shared across every part of the API rather than split per feature — reads, print jobs and bulk work such as a card import or a round of new sign-in codes all draw on the same budget. That is a low ceiling, and it is shared with any other integration running on the same Printix environment. StackJack paces itself below it and waits for the delay Printix asks for when it is throttled, which usually makes a wide read or a bulk job slower rather than failed. Pacing smooths a burst; it does not guarantee that every call arrives. Narrow the read if throttling persists. Raising the ceiling is a conversation with Printix support rather than a setting you can change. See Retrying a failed or timed-out write.

Several customers

One set of credentials covers one Printix environment. If you manage several customers on Printix, add one connection per customer from the connector's card, name each after the customer, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single customer.

The same applies when you need more than one application type for the same customer: add each Printix application as its own connection and name it so the difference is obvious. See Several connections of one connector.

Troubleshooting

"Printix rejected the Client ID and Client Secret" — most often a newer key replaced this one. Printix allows only one set of Cloud Print API credentials at a time, so anyone creating a new set, in Printix Administrator or through another integration, silently invalidates the set StackJack holds. Create a fresh application, paste the new pair in, and run a Test Connection. Also check the secret was not truncated on copy.

One family of tools is refused while everything else works — that is the application type, not the key. Check the table above for which type that family needs, create an application of that type in Printix, and add it as its own connection. This bites hardest on cards: looking one up and registering one need two different Printix application types.

"Printix says this already exists, or cannot be changed" — nothing is wrong with the credentials. Registering a card gives this when that card number is already registered on the environment; look it up first and check whose it is, because a card can only belong to one person. Creating a group gives it when a group with that external directory ID already exists, so reuse the existing one. Removing a group gives it when Printix will not let that group go, usually because something still depends on it.

A job vanished from the job list after you handed it to someone — that is expected. Jobs created through the API belong to a hidden API user, and the job list only shows that user's jobs, so changing the owner removes the job from it. The job has not been deleted; look it up by its ID instead.

Removing a site, a network or an SNMP discovery setting reported success but nothing changed — Printix does not report "not found" for those three, so a success message is not proof the record existed. Confirm the ID first, and read it back afterwards if it mattered. This bites hardest on SNMP: a discovery setting you believe you removed keeps polling printers with the community string you asked to retire.

Everything is refused although the connection test passes — check that the environment holds Printix Premium, and check that Secure Print is not set so that all users must print securely. Either one blocks the API while leaving the credentials perfectly valid.

Requests come back throttled — 100 requests a minute is shared across everything on that Printix environment, including other integrations. Ask for fewer rows per page, narrow the read, or space the work out. StackJack already waits for the delay Printix asks for.

A list appears to be missing its first entries — pages start at zero. Ask for page 0.

Nothing is found for an ID that looks right — every Printix call is scoped to one customer environment, so an ID from a different environment reads as missing rather than as refused. List the environments first, then list the parent collection, and use an ID that came back from it.

Printix tools

printix_ · 39 tools · Free 19 · Pro 20

Discovery

Printers and Queues

Print Jobs

Users

Groups

Cards

Sites

Networks

SNMP Configuration

Workstations