No-code connectors (Zapier / Make / n8n)
Wire Tagjet into Zapier, Make, or n8n with no code: trigger on a new receipt, send it to /v1/receipts, route the structured fields anywhere.
Why no-code
Many finance and accounting teams never touch the REST API directly. With Zapier, Make, or n8n you can connect Tagjet to email, cloud storage, spreadsheets, Slack, and accounting tools — wiring a receipt straight through to structured data without writing code. The pattern is always the same: a trigger captures a document, an HTTP step calls Tagjet, and downstream steps use the extracted fields.
The building block: one authenticated HTTP call
Every platform supports a generic "HTTP request" / "webhooks" action. Point it at a Tagjet endpoint, add your apikey header, and attach the file or a URL to it. For interactive flows use the synchronous /v1/receipts (simple) or /v1/receipts/verbose (full + confidences); for high volume use /v1/receipts/async with a callbackUrl back into the platform.
POST https://api.tagjet.app/v1/receipts/verbose
Headers:
apikey: tj_live_your_key_here
Body (multipart/form-data):
file: <the receipt or invoice file>Zapier
Use a trigger like "New Attachment in Gmail" or "New File in Google Drive". Add a "Webhooks by Zapier → POST" (or "Custom Request") action: set the URL to https://api.tagjet.app/v1/receipts/verbose, add the apikey header, and pass the file through as multipart form data. Map fields from the JSON response (for example data.merchantName.value, data.totalAmount.value) into later steps such as appending a row to Google Sheets or posting to Slack.
Make
Build a scenario whose first module watches an inbox or folder. Add an "HTTP → Make a request" module: method POST, URL https://api.tagjet.app/v1/receipts/verbose, a header named apikey with your key, and the document attached as a multipart form field named file. Make parses the JSON response so you can reference the data fields directly in downstream modules.
n8n
Start with a trigger node (Email, Google Drive, or a Webhook). Add an "HTTP Request" node: POST to https://api.tagjet.app/v1/receipts/verbose, send the file as form-data, and add the apikey header (store the key as an n8n credential, not inline). For large or slow documents, POST to /v1/receipts/async with a callbackUrl pointing at an n8n Webhook node, then continue the workflow when Tagjet calls back.
Async in a no-code flow
When you use /v1/receipts/async, give it a callbackUrl that resolves to your platform inbound webhook (Zapier Catch Hook, Make custom webhook, or an n8n Webhook node). Tagjet POSTs the finished verbose result to that URL with an X-Tagjet-Event: scan.completed header — let the second half of your flow handle that payload. If the platform cannot expose a public webhook, fall back to a scheduled step that polls GET /v1/receipts/{id}.
Recipe ideas
Email receipt → Tagjet → Google Sheets row. New Drive PDF → Tagjet → Slack summary card. Inbound webhook → Tagjet async → post coded totals to your accounting tool. Start from the verbose endpoint so you have confidences available to branch on (for example, route low-confidence scans to a human-review channel).