DataHub · Arazzo Workflow

DataHub Add Glossary Terms to a Dataset

Version 1.0.0

Confirm a dataset, attach glossary terms via its glossaryTerms aspect, then review the change in the entity timeline.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Data CatalogData DiscoveryData GovernanceData LineageMetadataArazzoWorkflows

Provider

datahub

Workflows

add-glossary-terms
Attach glossary terms to a dataset and confirm the change in its timeline.
Verifies a dataset exists, writes the glossaryTerms aspect to associate business terms with it, then reads the entity timeline to confirm the change landed.
3 steps inputs: entityUrn, glossaryTerms, token outputs: changeTransactions, termedUrn
1
confirmEntity
Retrieve the latest aspects for the dataset URN to confirm the entity exists before attaching glossary terms.
2
attachTerms
Upsert the glossaryTerms aspect for the dataset URN to associate the supplied business glossary terms with the dataset.
3
reviewTimeline
Query the entity timeline for the glossaryTerms aspect to confirm the term association was recorded.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: DataHub Add Glossary Terms to a Dataset
  summary: Confirm a dataset, attach glossary terms via its glossaryTerms aspect, then review the change in the entity timeline.
  description: >-
    Linking datasets to a business glossary is a key semantic-layer workflow in
    DataHub. The flow first reads the latest aspects for the target dataset to
    confirm it exists, then upserts the glossaryTerms aspect to attach one or more
    glossary term associations, and finally queries the entity timeline to surface
    the glossaryTerms change that was just recorded. Every step spells out its
    request inline so the flow can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: entitiesApi
  url: ../openapi/datahub-entities-api-openapi.yml
  type: openapi
- name: timelineApi
  url: ../openapi/datahub-timeline-api-openapi.yml
  type: openapi
workflows:
- workflowId: add-glossary-terms
  summary: Attach glossary terms to a dataset and confirm the change in its timeline.
  description: >-
    Verifies a dataset exists, writes the glossaryTerms aspect to associate
    business terms with it, then reads the entity timeline to confirm the change
    landed.
  inputs:
    type: object
    required:
    - token
    - entityUrn
    - glossaryTerms
    properties:
      token:
        type: string
        description: DataHub personal access token passed as a Bearer token.
      entityUrn:
        type: string
        description: The dataset URN to attach glossary terms to.
      glossaryTerms:
        type: object
        description: The glossaryTerms aspect value listing the glossary term associations.
  steps:
  - stepId: confirmEntity
    description: >-
      Retrieve the latest aspects for the dataset URN to confirm the entity
      exists before attaching glossary terms.
    operationId: getEntityLatestAspects
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    - name: urns
      in: query
      value: $inputs.entityUrn
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      confirmedUrn: $response.body#/0/entityUrn
    onSuccess:
    - name: entityExists
      type: goto
      stepId: attachTerms
      criteria:
      - context: $response.body
        condition: $.length > 0
        type: jsonpath
  - stepId: attachTerms
    description: >-
      Upsert the glossaryTerms aspect for the dataset URN to associate the
      supplied business glossary terms with the dataset.
    operationId: upsertEntities
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    requestBody:
      contentType: application/json
      payload:
      - entityUrn: $steps.confirmEntity.outputs.confirmedUrn
        entityType: dataset
        aspectName: glossaryTerms
        aspect: $inputs.glossaryTerms
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      termedUrn: $response.body#/0/entityUrn
  - stepId: reviewTimeline
    description: >-
      Query the entity timeline for the glossaryTerms aspect to confirm the
      term association was recorded.
    operationId: getTimeline
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.token
    - name: urn
      in: query
      value: $steps.attachTerms.outputs.termedUrn
    - name: aspectNames
      in: query
      value:
      - glossaryTerms
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      changeTransactions: $response.body#/changeTransactions
  outputs:
    termedUrn: $steps.attachTerms.outputs.termedUrn
    changeTransactions: $steps.reviewTimeline.outputs.changeTransactions

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/datahub-add-glossary-terms-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.