Add a Data Source of kind webhook to the workflow and create a trigger token for it.
INTEGRATION / WEBHOOKS / REST
Connect Any API to a Label Printer, in Either Direction
Have any system push data to a LabelInn webhook, or let LabelInn poll an external API every few minutes and print one label per new item. No middleware, no printer code.
FREE PLAN · NO CREDIT CARD · WINDOWS / MAC / LINUX / WEB
THE PROBLEM
Your shop system, your 3PL portal or an internal tool has the data for the label, and it has an API. What is missing is the piece in between: something that gets that data to a thermal printer without your developers writing printer code or running a server for it.
A LabelInn workflow can be that piece. Data can be pushed to it, or it can pull the data itself.
🔗 If it has an API, it can print. Push to a webhook or let LabelInn poll. Start free →
01 / WEBHOOK
Push: your system calls LabelInn
Have your system POST a JSON object to the trigger URL when something happens.
The object becomes the record. Its fields fill the design; Router, Lookup and the rest work as usual.
The token starts only that workflow's entry node, so a leaked URL cannot start anything else. Prefer to send print jobs directly? The REST API takes a design and data in one call.
02 / REST API
Pull: LabelInn polls your API
When the other system cannot call out, or you do not control it, let LabelInn ask instead. An HTTP Fetcher node with polling switched on calls the URL on a timer (every 5 minutes by default) and starts a run for each new item.
- Items path: where the list is in the response, for example
$.orders. - Key field: what identifies an item, for example
order_id. Items already seen never print again. - Headers: for API keys or tokens.
- Extractions: JSONPath expressions that pick out extra fields.
- Timeout: 1 to 120 seconds, so a slow API fails the step instead of hanging.
03 / POLLING
Report back
A Webhook node at the end can POST the result to any HTTPS endpoint, for example to tell your system the label printed. It runs from LabelInn's cloud, and it only calls public HTTPS addresses.
04 / INTEGRATION
Which one to choose
| Situation | Use |
|---|---|
| Your system can send a webhook | Push to a webhook trigger |
| You can only read their API | Poll with the HTTP Fetcher |
| Your developers want full control per job | REST API |
| Your system writes files, not API calls | Hot folder |
QUESTIONS / FAQ
Frequently asked questions
Can a webhook trigger label printing?
Yes. Add a webhook Data Source to a workflow, create a trigger token, and any system that POSTs JSON to the trigger URL starts a run that prints the label.
Can LabelInn poll an API and print new items?
Yes. An HTTP Fetcher node with polling on calls the URL on a timer, starts one run per new item in the list you point it at, and remembers item keys so nothing prints twice.
How often does polling run?
Every 5 minutes by default; you set the interval on the node.
Can LabelInn tell my system that the label printed?
Yes. A Webhook node can POST the result to any public HTTPS endpoint.
KEEP GOING
Related
NEXT STEP / LABELINN
Your API, your printer, nothing in between
Connect the system you already have to the printer you already have. · Webhook triggers · API polling with dedup · Results posted back