Airparser integration | Zervanor
← All connectors

Airparser

Also an agent tool
data-analytics

AI document/email parser — extract structured data from PDFs, emails, and images. Public REST API over a single host (https://api.airparser.com): inbox (mailbox) management (list/get/create/delete), document retrieval (compact + extended) and listing, and extraction-schema management (set/clone). API-key auth (custom X-API-Key header). Real signed completion webhook (airparser-signature HMAC-SHA256 base64 over raw body, generic_hmac) emitting a single document-parsed trigger; webhook registration is a manual operator step in the Airparser UI (airparser-03). Binary document upload (upload-sync/upload, multipart file part) is deferred to the platform binary file-I/O engine theme (Theme 9, airparser-02).

9 actions · 1 triggers

The Airparser integration lets you connect Airparser to your automations with 9 actions and 1 triggers — and every action is also a tool an AI agent can call. Examples: List Inboxes, Get Inbox, Create Inbox, Delete Inbox, Get Document (Compact). No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 1

Events in Airparser that can start a workflow.

webhook

Document Parsed

Fires when a document in the inbox finishes parsing. Airparser POSTs the parsed document JSON (signed with airparser-signature) to the configured receive URL. Webhook registration is a manual operator step in the Airparser inbox UI (airparser-03); exact payload field names confirmed against a live delivery at build (airparser-08).

Actions 9

What Zervanor can do in Airparser.

Inboxes7

GET

List Inboxes

List all inboxes (mailboxes) in the account (Airparser: GET /inboxes). Safe, idempotent identity/connectivity probe — connector READ test target.

GET

Get Inbox

Fetch a single inbox including its parsing configuration and extraction schema (Airparser: GET /inboxes/{inbox_id}).

POST

Create Inbox

Create a new inbox (Airparser: POST /inboxes/create). Body: name (required), llm_engine (optional: text|vision).

DELETE

Delete Inbox

Delete an inbox and its documents (Airparser: DELETE /inboxes/{inbox_id}). Destructive — not a safe test target.

GET

List Documents

List documents in an inbox with paging, date range, search, and status filters (Airparser: GET /inboxes/{inbox_id}/docs).

POST

Set Extraction Schema

Create or replace the extraction schema (field definitions) for an inbox (Airparser: POST /inboxes/{inbox_id}/schema). Returns true on success.

POST

Clone Extraction Schema

Copy an inbox's extraction schema into another inbox (Airparser: POST /inboxes/{inbox_id}/schema-clone). Returns a boolean.

Docs2

GET

Get Document (Compact)

Fetch the webhook-style parsed JSON for a document; poll this to detect completion (Airparser: GET /docs/{document_id}). Returns _id, name, status, json, credits. Path canonical per Knowledge Base; confirm /docs vs /documents at build (airparser-06).

GET

Get Document (Extended)

Fetch enriched document detail including inbox_id, img_preview, pages, nextId (Airparser: GET /docs/{document_id}/extended).

Automations using Airparser

Build your own automation with Airparser in the visual builder.

Frequently asked questions

What can I automate with Airparser?

9 actions are available — for example: List Inboxes, Get Inbox, Create Inbox, Delete Inbox, Get Document (Compact), and more.

Which Airparser events can start a workflow?

1 triggers — for example: Document Parsed.

Can Airparser be used as an AI agent tool?

Yes. Every Airparser action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Airparser integration modelled?

Airparser is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.