Operations & Internal Tools
Connect PrintNode and Bubble
A Bubble app that prints straight to the right printer on the shop floor, without a dialog box for every job.
- Data flows
- 4 automated, two-way where safe
- Built with
- PrintNode, Bubble, Cloudflare Workers
- Timeline
- Live in 2 to 8 weeks from scope
- Owned by
- You, with accounts, credentials and code in your name.
Connecting PrintNode to Bubble lets an app send labels and documents straight to a local printer, without a browser print dialog. SBD built a Bubble dashboard for a copper wire manufacturer with Cloudflare Workers, Render and PrintNode in the stack, for work that happens on a production floor.
What runs between PrintNode and Bubble
Each line is one automated workflow, with the same checks, logs and alerts on all of them.
-
Production labels from a web app
WhenA worker completes a production step
ThenCreate the label data with the batch and item details
-
Dispatch documents printed on demand
WhenA label is ready
ThenA backend call sends it to PrintNode for the printer at that station
-
Printer routing by station
WhenA printer is chosen
ThenRoute the job by station or department, without asking the user
-
Reprints with a record
WhenA job fails or a printer goes offline
ThenShow it in the app, alert the supervisor and allow a reprint
Where the simple setup breaks down
A one-step Zap connects PrintNode and Bubble in an afternoon. This is what goes wrong once volume grows.
Browser printing slows the floor down
Printing from Bubble normally opens a dialog where staff confirm the job and pick a printer. That is tolerable once, but not hundreds of times a shift, and the wrong printer gets chosen.
The API key does not belong in the browser
Calling PrintNode from client-side code exposes the key to anyone using the page. The call should go through a Bubble backend workflow or a small service such as a Cloudflare Worker.
Bubble is not ideal for producing the file
Precise labels depend on exact sizes and fonts. Generating the PDF or label data in a small service can be more dependable than building it inside the app.
A sent job may not have printed
A printer can be offline or out of labels after the API accepts the job. Unless the app tracks job state, staff assume the label exists and the problem appears at dispatch.
Used for
- Production labels from a web app
- Dispatch documents printed on demand
- Printer routing by station
- Reprints with a record
- PrintNode API from Bubble
- Cloudflare Workers for print jobs
- Barcode labels on the shop floor
- Failed print alerts
- No print dialog on the floor
- Warehouse document printing
Built with
PrintNode
Bubble- Cloudflare Workers
Render
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
Where we have done this
What people ask about this pair
What do we install?
The PrintNode client runs on a computer connected to the printers, and the app talks to PrintNode through its API. We set up and test each station.
What happens if the internet drops?
Jobs cannot reach the printer until the connection returns. We agree what staff should do, and the app shows which jobs did not print.
Does this only work with Bubble?
No. PrintNode has a JSON API that any backend can call. This page covers Bubble because that is where we have built it.
Related pairs
-

Airtable and Retool
Airtable is a good database with a limited interface. Retool adds the screens and permissions it lacks.
-

Retool and Supabase
Screens in Retool, data in a Postgres database you own and can expose safely.
-

WhatsApp and Airtable
Reach customers where they reply, with the conversation logged against the record.
- Solution
Manufacturing
The workflows we automate for this kind of team.
Connect PrintNode and Bubble
A Bubble app that prints straight to the right printer on the shop floor, without a dialog box for every job.
Start with a discovery call











