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
Two ways, both without printer code: have your system POST a JSON object to a LabelInn workflow trigger URL (https://labelinn.com/v1/workflows/{id}/trigger/{token}), or let a workflow poll your API on a timer and print one label per new item. The posted fields become the label data.

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 |
PUSH: THE TRIGGER URL
What the webhook accepts and refuses
The contract below was checked by running the real authorizeTrigger function from the cloud code with each case.
# unsigned trigger (the token in the URL is the credential)
curl -X POST "https://labelinn.com/v1/workflows/WORKFLOW_ID/trigger/TOKEN" \
-H "Content-Type: application/json" \
-d '{"sku":"00417","qty":4}'
# signed trigger: HMAC-SHA256 of the raw body, hex, sent as X-LabelInn-Signature
SECRET=whsec_...
BODY='{"sku":"00417","qty":4}'
SIG="sha256=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$SECRET" -hex | sed 's/^.* //')"
curl -X POST "https://labelinn.com/v1/workflows/WORKFLOW_ID/trigger/TOKEN" \
-H "Content-Type: application/json" -H "X-LabelInn-Signature: $SIG" -d "$BODY"| What you send | Answer | Why |
|---|---|---|
| A JSON object, token correct | run starts; fields become {{sku}}, {{qty}} | Plus _triggeredBy, _triggerNodeId, _triggeredAt added to the record. |
| Signed token, header missing or wrong | 401 INVALID_SIGNATURE | The HMAC must be over the exact raw body. |
| A JSON array or a bare value | 400 INVALID_PAYLOAD | Only an object has field names. To print many rows, send one request per row. |
{} | 400 EMPTY_PAYLOAD | Nothing to print. |
| Unknown, revoked or other-workflow token | 404 TRIGGER_NOT_FOUND | All three look identical on purpose. |
| Workflow switched off | 409 WORKFLOW_DISABLED | A silent 200 would swallow orders. |
| More than 512 KB | 413 PAYLOAD_TOO_LARGE | |
| More than one request every 250 ms on one token | 429 RATE_LIMITED | A flood brake per token. |
The openssl line above produced the same sha256= value as the cloud function's own HMAC for the same body and secret on 17 October 2026.
PUSH, POLL OR REST
When to use the trigger URL and when the REST API
| Workflow trigger URL | REST print API | |
|---|---|---|
| Credential | The token in the URL (optionally plus an HMAC secret) | A Bearer API key |
| What picks the design and printer | The workflow: Router, Lookup and Print nodes | Your request: printer_id, design_id |
| Counts against the API quota | No, the call does not authenticate with an API key | Yes, every request |
| Rows per request | One record | Up to 1000 in data, 100 jobs per batch |
| Plan | Webhook sources need the Webhooks feature: Pro ($24.90/month) or the trial; the workflow itself needs Starter or above | Pro or the trial |
| Best when | The sender is a PLC gateway, a form, Zapier or an ERP rule that can only call a URL | You own the code and want full control per job |
The REST route is on Label printing API; starting a workflow from code is on trigger a workflow from code.
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.
What is the URL of a LabelInn webhook trigger?
https://labelinn.com/v1/workflows/{workflowId}/trigger/{token}. You create the token in the workflow editor; the URL is POST only and the posted JSON object becomes the label data.
How do I sign a webhook so it cannot be forged?
Mint the trigger with a secret and send X-LabelInn-Signature: sha256=<hex>, the HMAC-SHA256 of the raw request body with that secret. A missing or wrong signature is refused with 401.
Can one webhook call print several labels?
The trigger takes one JSON object per call. For several rows in one request use the REST API (data as an array of up to 1000 rows) or loop inside the workflow with a For Each node.
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