Connect Breezy HR and DocuPipe

Both apps 28Breezy HR 12DocuPipe 16

• Trigger
  New Candidate

  Triggers when a new candidate is added to the selected position in Breezy HR.

• Trigger
  New Candidate in Stage

  Triggers when a candidate on the chosen position is in the chosen pipeline stage.

• Action
  Add candidate note

  Adds an internal team note to a candidate's activity stream on a position. The note is not visible to the candidate.

• Action
  Add position

  Creates a new position (job opening) in a Breezy HR company and returns the created position.

• Action
  Find candidates by criteria

  Returns candidates across the whole Breezy HR company that match a free-text search on name, email, phone, headline, tags, questionnaire answers, work history, education or position location.

• Action
  Get position

  Returns a single Breezy HR position with its full details, including name, type, state, location, department, description, application form and salary.

• Action
  List candidate activity

  Returns a candidate's activity stream on a position: stage moves, notes, interviews, documents, questionnaires and other events, newest first.

• Action
  List candidates

  Returns the candidates on a Breezy HR position, with each candidate's name, contact details, pipeline stage, source and score.

• Action
  List pipelines

  Returns the hiring pipelines configured for a Breezy HR company, including each pipeline's stages.

• Action
  List positions

  Returns the positions (job openings) in a Breezy HR company, optionally limited to one state such as published or draft.

• Action
  Update candidate stage

  Moves a candidate to a different stage in their position's hiring pipeline and returns the updated candidate.

• Action
  Update position

  Updates an existing Breezy HR position (job requisition). Only the details you fill in are changed; everything else on the position is left as it is.

• Trigger
  Document Processed

  Triggers when a document finishes parsing and OCR is complete.

• Action
  Add schema

  Creates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.

• Action
  Analyze document

  Asks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.

• Action
  Classify Document

  Sends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.

• Action
  Delete document

  Removes a document from your DocuPipe account.

• Action
  Delete schema

  Removes an extraction schema from your DocuPipe account.

• Action
  Extract Data From Document

  Pulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.

• Action
  Find documents by criteria

  Finds documents in your DocuPipe account whose file name or document ID matches what you search for.

• Action
  Get Document

  Returns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.

• Action
  Get Extraction Result

  Returns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.

• Action
  Get schema

  Returns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.

• Action
  List documents

  Returns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.

• Action
  List extractions

  Returns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.

• Action
  List schemas

  Returns the extraction schemas in your DocuPipe account.

• Action
  Upload and Extract Data

  Sends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.

• Action
  Upload Document

  Sends a file to DocuPipe to be read and turned into a document you can extract data from.

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