In short: Connect Tiro to Zapier once, pick an inbox – and every finished document starts a Zap with all fields and line items. The other way round, a Zap drops files from Gmail, Dropbox or your CRM into an inbox. No code, no polling, no credits for the delivery.
The app is in beta access: add Tiro to your Zapier account – after that it is available in the Zap editor like any other app. Listing in the public Zapier directory is under way.
What the Zapier app is for
Webhooks are the shortest way into your own system – but they need someone to provide a URL. Zapier is the shortest way into other people's systems: Google Sheets, Airtable, Notion, HubSpot, Pipedrive, Slack, an ERP with a Zapier connector. You click the path together and Tiro delivers the data.
Typical Zaps:
- Order confirmations → Google Sheets: trigger “New Row”, action “Create Spreadsheet Row”. Every line item becomes a row, order number and supplier travel along on each one.
- Portal leads → CRM: trigger “New Extract”, action “Create Contact” in HubSpot or Pipedrive. Name, address, property and preferred date are ready-made fields.
- Gmail attachments → Tiro: trigger “New Attachment” in Gmail, action “Upload Document” in Tiro. If you cannot use Tiro's e-mail intake, this is your route.
- Failures → Slack: trigger “Document Failed”, action “Send Channel Message”. Nothing fails silently.
Triggers and actions
| Building block | What it does |
|---|---|
| New Extract (trigger) | Starts when a document has been extracted. Delivers all header fields, the line items, filename, pages, credits and links to the document and its downloads. |
| New Row (trigger) | Starts once per line item; the header fields are on every row. Made for spreadsheets. |
| Document Failed (trigger) | Starts when a document could not be processed after all attempts – with the error message and a link. |
| Upload Document (action) | Puts a file from a previous step into an inbox. Returns document ID and status; extraction runs in the background. |
| Find Extract (search) | Fetches the result of a document by ID – for “Upload → Delay → Find” in a single Zap. |
The fields in the Zap editor carry the names you gave them in the inbox. If you change the inbox's fields, refresh the Zap's fields – Zapier reads them fresh from Tiro on every call.
How it works under the hood
When you turn a Zap on, the app creates a destination of type Zapier in Tiro – you see it in the inbox under “Destinations” next to your webhooks. As soon as a result is finished, Tiro sends a signed call to Zapier, with the same retries on failure as every webhook: after 1, 5 and 15 minutes, then after 1, 3, 6 and 12 hours. Every attempt shows in the document's history. Turn the Zap off and the destination disappears again.
If you delete the destination in Tiro by hand, the Zap waits in vain – turn it off and on in Zapier and it creates a new destination.
Good to know
- Review: if the inbox reviews, Zapier waits for the release. “Approve all” in the app fires the waiting Zaps at once.
- Reprocessing: reprocess a document and the Zap fires again – with the new values. Zapier tells the new run apart by its own ID.
- Downloads: the CSV and Excel links in the Zap point to the REST API and need your API key as a bearer header – they are not meant for a direct click from a sheet; get the file in the app instead.
- Alternatives without Zapier: webhooks for your own system, the REST API for code, MCP for your AI assistant. Make and n8n work today through their HTTP triggers with a Tiro webhook; dedicated apps follow.