Connect Airparser and Doclift PDF

Both apps 22Airparser 10Doclift PDF 12

• 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.

• Trigger
  New PDF Document Generated

  Webhook trigger for Doclift's async document-generation completion callback (POST .../webhooks/doclift, X-Doclift-Signature: sha256=hmac). Delivery URL is configured manually on the external application in the Doclift dashboard — no register/list/delete API exists. Fires once per document_request (all its documents_generations resolved to success/error), payload includes id, tag, type, timestamp, documents_generations[] (generation_status, file{filename,url,size}).

• Action
  Add Template

  create a custom (HTML-body) template: title, description, content, orientation, margins, optional variables_attributes. Server forces category=custom.

• Action
  Add Variable

  create a variable on a custom template: title (unique, naming pattern), description, field_type (text/checkbox/radio/select/collection, default text), seed_value, allowed_values.

• Action
  Delete Template

  removes a custom template (scope restricted to category=custom, non-archived, same org).

• Action
  Get Document Request

  status and documents_generations detail (signed file url, valid 2 hours) for one document request.

• Action
  Get Template

  full template detail including variables and content (custom templates); works for any published template of the three categories.

• Action
  List Document Requests

  list document generation requests with id, tag, type, status, documents_generations (each with generation_status and file url).

• Action
  List Templates

  returns published, non-archived templates (custom/fillable_form/workflow) for the organization: id, title, description.

• Action
  List Variables

  all variables of a custom, non-archived template: id, title, description, field_type, allowed_values (no pagination, no seed_value).

• Action
  Publish Template

  marks a custom template published (usable for document generation).

• Action
  Unpublish Template

  marks a custom template unpublished.

• Action
  Update Variable

  update description/field_type/allowed_values/title of a variable; allowed_values replaces the stored array.

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