Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Airparser

Extract structured data from emails, PDFs, or documents with Airparser.

CategoryProductivity
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Airparser with Flows360

Extract structured data from emails, PDFs, or documents with Airparser.

Use the Airparser connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 1 trigger.

Available actions

  • Get Data from Document
  • Upload Document

Available triggers

  • Document Parsed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Airparser
  • Package: @activepieces/piece-airparser@0.1.7
  • Exact artifact digest: sha256:c1e625bb1e3299c0c34a2c56bb33a4bb891ba5f6b076b9e1a791a8e7565ad465
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Data from Document (extract_data_from_document), Retrieves parsed JSON data from a specific document. Classification: read.
  • Upload Document (upload_document), Upload a document to an Airparser inbox for parsing. Classification: read.

Trigger contracts

  • Document Parsed, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Data from Document Yes No Retrieves parsed JSON data from a specific document.
Upload Document Yes No Upload a document to an Airparser inbox for parsing.
Document Parsed Yes No webhook trigger declared by the pinned package.

Supported actions

Get Data from Document · Read

Retrieves parsed JSON data from a specific document.

extract_data_from_document · Risk: low · Retry: safe

Inputs

  • inboxId · string · Required
  • documentId · string · Required
Upload Document · Read

Upload a document to an Airparser inbox for parsing.

upload_document · Risk: low · Retry: safe

Inputs

  • inboxId · string · Required
  • file · object · Required, The document file to upload for parsing.
  • fileName · string · Optional
  • meta · object · Optional, Optional metadata to associate with the document.

Triggers

Document Parsed · Webhook

Triggers when a new document is parsed in a specific inbox.

Inputs

  • inboxId · string
  • markdown · string

Setup

Setup

  1. Add the Airparser connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-airparser@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Airparser connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-airparser@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com