Connect Airparser to Harness.io

Both apps 21Airparser 10Harness.io 11

• Trigger
  Document Parsed

  Triggers when Airparser finishes parsing a document in the chosen inbox, giving you the extracted data.

• Action
  Create an Inbox

  Creates a new Airparser inbox that documents can be sent to for parsing.

• Action
  Create or Update Extraction Schema

  Sets which fields Airparser should pull out of documents sent to an inbox, replacing whatever schema was there before.

• Action
  Delete an Inbox

  Deletes an Airparser inbox and the documents stored in it.

• Action
  Extract Data From a Document

  Sends a document to an Airparser inbox, waits for it to be parsed, and returns the extracted data.

• Action
  Extract Data From a Document (Async)

  Sends a document to an Airparser inbox and returns straight away without waiting for parsing. Use the Document Parsed trigger or Get Document to pick up the result.

• Action
  Get a Document

  Returns a parsed Airparser document, including the data extracted from it.

• Action
  Get an Inbox

  Returns one Airparser inbox with its settings, its email address prefix and its current extraction schema.

• Action
  List Documents

  Lists the documents in an Airparser inbox, with the data extracted from each one.

• Action
  List Inboxes

  Lists all the Airparser inboxes in the connected account.

• Action
  Add Connector

  Create a new connector (e.g. GitHub, Kubernetes, Docker registry). POST /ng/api/connectors

• Action
  Add Environment

  Create a new deployment environment in a project. POST /ng/api/environmentsV2

• Action
  Add Secret

  Create a new secret (text/file/SSH key) in a scope. POST /ng/api/v2/secrets

• Action
  Create Project

  Creates a new project in Harness.

• Action
  Execute Pipeline

  Trigger a pipeline execution. POST /pipeline/api/pipeline/execute/{pipelineIdentifier}

• Action
  Get Pipeline

  Fetch a single pipeline definition by identifier. GET /pipeline/api/pipelines/{pipelineIdentifier}

• Action
  Get Pipeline Execution

  Fetch a pipeline execution's status and details by execution id. GET /pipeline/api/pipelines/execution/{planExecutionId}

• Action
  Get Project

  Fetch a single project by identifier. GET /ng/api/projects/{identifier}

• Action
  List Pipeline Executions

  List pipeline executions for a project. POST /pipeline/api/pipelines/execution/summary

• Action
  List Pipelines

  List pipelines for a project. POST /pipeline/api/pipelines/list

• Action
  List Projects

  List projects in the account/org. GET /ng/api/projects

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.