Alteryx · Schema

ScheduleDetail

Detailed representation of a schedule

AnalyticsAutomationData EngineeringData PreparationData ScienceETLMachine-LearningPredictive Analytics

Properties

Name	Type	Description
id	string	Unique schedule identifier
name	string	Name of the schedule
workflowId	string	ID of the associated workflow
versionId	string	Specific workflow version ID
ownerId	string	ID of the schedule owner
runDateTime	string	Next scheduled run date and time
comment	string	Comments about the schedule
enabled	boolean	Whether the schedule is active
priority	string	Execution priority
workerTag	string	Worker tag for execution routing
status	string	Current status of the schedule
credentialId	string	Credential used for execution
creationTime	string	When the schedule was created
lastRunTime	string	When the schedule last executed
state	string	Current state of the schedule
runCount	integer	Total number of times the schedule has executed
frequency	string	Human-readable frequency description
lastError	string	Last error message if any
cpuName	string	Name of the worker node
lastModifiedId	string	ID of the user who last modified the schedule
lastModifiedDate	string	Date of last modification
canEdit	boolean	Whether the current user can edit this schedule
timeZone	string	Time zone for the schedule
questions	array	Analytic app question values

View JSON Schema on GitHub

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "ScheduleDetail",
  "type": "object",
  "description": "Detailed representation of a schedule",
  "properties": {
    "id": {
      "type": "string",
      "description": "Unique schedule identifier"
    },
    "name": {
      "type": "string",
      "description": "Name of the schedule"
    },
    "workflowId": {
      "type": "string",
      "description": "ID of the associated workflow"
    },
    "versionId": {
      "type": "string",
      "description": "Specific workflow version ID"
    },
    "ownerId": {
      "type": "string",
      "description": "ID of the schedule owner"
    },
    "runDateTime": {
      "type": "string",
      "description": "Next scheduled run date and time"
    },
    "comment": {
      "type": "string",
      "description": "Comments about the schedule"
    },
    "enabled": {
      "type": "boolean",
      "description": "Whether the schedule is active"
    },
    "priority": {
      "type": "string",
      "description": "Execution priority"
    },
    "workerTag": {
      "type": "string",
      "description": "Worker tag for execution routing"
    },
    "status": {
      "type": "string",
      "description": "Current status of the schedule"
    },
    "credentialId": {
      "type": "string",
      "description": "Credential used for execution"
    },
    "creationTime": {
      "type": "string",
      "description": "When the schedule was created"
    },
    "lastRunTime": {
      "type": "string",
      "description": "When the schedule last executed"
    },
    "state": {
      "type": "string",
      "description": "Current state of the schedule"
    },
    "runCount": {
      "type": "integer",
      "description": "Total number of times the schedule has executed"
    },
    "frequency": {
      "type": "string",
      "description": "Human-readable frequency description"
    },
    "lastError": {
      "type": "string",
      "description": "Last error message if any"
    },
    "cpuName": {
      "type": "string",
      "description": "Name of the worker node"
    },
    "lastModifiedId": {
      "type": "string",
      "description": "ID of the user who last modified the schedule"
    },
    "lastModifiedDate": {
      "type": "string",
      "description": "Date of last modification"
    },
    "canEdit": {
      "type": "boolean",
      "description": "Whether the current user can edit this schedule"
    },
    "timeZone": {
      "type": "string",
      "description": "Time zone for the schedule"
    },
    "questions": {
      "type": "array",
      "description": "Analytic app question values"
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this

find_json_schemasBrowse and filter every JSON Schema 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 JSON Schema

curl "https://apis.io/api/v1/json-schemas/alteryx-server-v3-schedule-detail"

All schemas

curl "https://apis.io/api/v1/json-schemas?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.

GitHub Google LinkedIn

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