Connect Colorado Information Marketplace to DocuPipe

Both apps 21Colorado Information Marketplace 5DocuPipe 16

• Trigger
  New record

  Polling trigger: fires when a new row appears in a specified Colorado Information Marketplace (Socrata SODA API) dataset. GET https://data.colorado.gov/resource/{dataset_id}.json ordered by a rowid/created/updated system field ($order=:id DESC or an updated_at column) with $limit, dedup by the row's system id (:id) or an updated_at watermark since datasets vary in whether they expose a stable update timestamp column.

• Action
  Find datasets

  Search the Colorado Information Marketplace open-data catalog for datasets by keyword/category. GET https://data.colorado.gov/api/catalog/v1?q={query}&limit=... (Socrata Discovery API) returning dataset id, name, description, category, and update timestamps. Used to locate the dataset identifier that other ops (List/Get/Find records) require as input.

• Action
  Find records by criteria

  Query a Colorado Information Marketplace (Socrata SODA API) dataset with a SoQL $where/$select/$order filter. GET https://data.colorado.gov/api/v3/views/{dataset_id}/query.json (or resource/{dataset_id}.json on older SODA2 endpoints) with SoQL query params ($where, $select, $order, $limit, $offset). Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu) as input plus the SoQL clauses.

• Action
  Get record

  Get a single row from a Colorado Information Marketplace (Socrata SODA API) dataset by its row identifier. GET https://data.colorado.gov/resource/{dataset_id}/{row_id}.json (or a $where=:id='{row_id}' query when the dataset has no explicit row identifier). Requires dataset_id and row_id.

• Action
  List records

  List all rows in a Colorado Information Marketplace (Socrata SODA API) dataset, paginated. GET https://data.colorado.gov/resource/{dataset_id}.json with $limit/$offset params. Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu).

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