Microsoft Azure Functions · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for WebApps API Client Workflow Trigger Histories API

4 actions 4 updates phrasing extends openapi/microsoft-azure-functions-workflowtriggerhistories-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Microsoft Azure Functions's API. It is a proposal applied on top of the contract, not a document Microsoft Azure Functions publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories'].get
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories/{historyName}'].get
$.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories/{historyName}/resubmit'].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 WebApps API Client Workflow Trigger Histories API
  version: 1.0.0
extends: openapi/microsoft-azure-functions-workflowtriggerhistories-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories'].get
  update:
    x-apievangelist-phrasing:
      intent: List a workflow trigger's history
      effect: read
      questions:
      - When did a trigger in my Logic Apps Standard workflow last fire, and did it succeed?
      - Can I limit or filter the trigger history I get back for a workflow?
      instructions:
      - text: List the history of trigger {triggerName} in workflow {workflowName} on app {name}.
        slots:
          triggerName: path.triggerName
          workflowName: path.workflowName
          name: path.name
      - text: Show the last {top} firings of trigger {triggerName} in workflow {workflowName} matching {filter}.
        slots:
          top: query.$top
          triggerName: path.triggerName
          workflowName: path.workflowName
          filter: query.$filter
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories/{historyName}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get one workflow trigger history entry
      effect: read
      questions:
      - What inputs and outputs did one specific trigger firing record?
      - Can I inspect a single trigger history entry by its name?
      instructions:
      - text: Get history entry {historyName} for trigger {triggerName} in workflow {workflowName} on app {name}.
        slots:
          historyName: path.historyName
          triggerName: path.triggerName
          workflowName: path.workflowName
          name: path.name
      - text: Show trigger firing {historyName} of {triggerName} in workflow {workflowName}.
        slots:
          historyName: path.historyName
          triggerName: path.triggerName
          workflowName: path.workflowName
      method: generated
      generated: '2026-10-01'
- target: $.paths['/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/hostruntime/runtime/webhooks/workflow/api/management/workflows/{workflowName}/triggers/{triggerName}/histories/{historyName}/resubmit'].post
  update:
    x-apievangelist-phrasing:
      intent: Resubmit a workflow run from trigger history
      effect: write
      questions:
      - Can I rerun a workflow using the same trigger event that fired before?
      - How do I replay a failed run from its trigger history?
      instructions:
      - text: Resubmit the run from history {historyName} of trigger {triggerName} in workflow {workflowName} on app {name}.
        slots:
          historyName: path.historyName
          triggerName: path.triggerName
          workflowName: path.workflowName
          name: path.name
      - text: Replay trigger firing {historyName} of {triggerName} in workflow {workflowName}.
        slots:
          historyName: path.historyName
          triggerName: path.triggerName
          workflowName: path.workflowName
      method: generated
      generated: '2026-10-01'

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay 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 overlay
curl "https://apis.io/api/v1/overlays/microsoft-azure-functions-workflowtriggerhistories-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?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.