Connect Buildkite and DocuPipe

Both apps 30Buildkite 14DocuPipe 16

• Trigger
  Build finished

  Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).

• Trigger
  New build

  Triggers when a new build is scheduled in a Buildkite pipeline.

• Action
  Add annotation

  Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.

• Action
  Add build

  Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.

• Action
  Add pipeline

  Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.

• Action
  Cancel build

  Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.

• Action
  Delete pipeline

  Permanently deletes a pipeline from your Buildkite organization.

• Action
  Get build

  Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.

• Action
  Get pipeline

  Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.

• Action
  List agents

  Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.

• Action
  List builds

  Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.

• Action
  List pipelines

  Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.

• Action
  Rebuild build

  Starts a new build that re-runs an existing build of a pipeline, and returns the new build.

• Action
  Update pipeline

  Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.

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