Tray.ai · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Tray Ai Workflows API

5 actions 5 updates phrasing extends openapi/tray-ai-workflows-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Tray.ai's API. It is a proposal applied on top of the contract, not a document Tray.ai publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 5

$.info
$.paths['/graphql#exportWorkflows'].post
$.paths['/graphql#importWorkflows'].post
$.paths['/ '].post
$.paths['/ '].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Tray Ai Workflows API
  version: 1.0.0
extends: openapi/tray-ai-workflows-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 4
- target: $.paths['/graphql#exportWorkflows'].post
  update:
    x-apievangelist-phrasing:
      intent: Export workflows via GraphQL
      effect: read
      questions:
      - How do I export workflows from my embedded account to promote them from staging to production?
      - Can the GraphQL exportWorkflows mutation run with a master token?
      instructions:
      - text: Run the exportWorkflows GraphQL mutation with {variables}.
        slots:
          variables: requestBody.variables
      - text: Send GraphQL request {mutation} to export my staging workflows.
        slots:
          mutation: requestBody.query
      method: generated
      generated: '2026-09-26'
- target: $.paths['/graphql#importWorkflows'].post
  update:
    x-apievangelist-phrasing:
      intent: Import workflows via GraphQL
      effect: write
      questions:
      - Can I load exported workflows into my production embedded account over GraphQL?
      - What does the GraphQL importWorkflows mutation need as input?
      instructions:
      - text: Run the importWorkflows GraphQL mutation with exported data {variables}.
        slots:
          variables: requestBody.variables
      - text: Send GraphQL mutation {mutation} to import workflows into production.
        slots:
          mutation: requestBody.query
      method: generated
      generated: '2026-09-26'
- target: $.paths['/                  '].post
  update:
    x-apievangelist-phrasing:
      intent: Import workflows via the embedded root endpoint
      effect: write
      questions:
      - Is there an embedded root call that imports workflows with a master token?
      - Which embedded root request loads previously exported workflows?
      instructions:
      - text: Post an import-workflows request to the embedded root with {variables}.
        slots:
          variables: requestBody.variables
      - text: Load exported workflows through the embedded root endpoint.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/                   '].post
  update:
    x-apievangelist-phrasing:
      intent: Export workflows via the embedded root endpoint
      effect: read
      questions:
      - Can I export workflows by posting to the embedded root with a master token?
      - Which embedded root call pulls out workflow definitions?
      instructions:
      - text: Post an export-workflows request to the embedded root with {variables}.
        slots:
          variables: requestBody.variables
      - text: Pull workflow definitions out through the embedded root endpoint.
      method: generated
      generated: '2026-09-26'