Automation
Workflow graph for event- and schedule-triggered tasks, workspace settings, and run history.
How to use this capability
Ways to interact with this capability — pick a path to jump to the relevant section below.
SDK
Call actions from Node or React apps using the Ossy SDK — typed payloads and workspace context built in.
View section ↓
MCP
Connect Cursor to http://localhost:3006/mcp when MCP tools are available for automation.
View section ↓
HTTP
Call actions over HTTP with Bearer token authentication — create a token in Profile for scripts and automation.
View section ↓
Background tasks
Event-driven and scheduled handlers run in the background — triggered by the platform, not invoked like actions.
View section ↓
Actions
Invokable intents — call directly via SDK, POST /actions, or MCP tools. This is the agent-facing surface, not background jobs.
Get Task Instance
@ossy/automation/actions/get-task-instance
Invoke @ossy/automation/actions/get-task-instance
MCP: ossy_automation_get_task_instance
sdk.invoke('@ossy/automation/actions/get-task-instance', { … })POST /actions
{ "action": "@ossy/automation/actions/get-task-instance", "payload": { … } }Background tasks
Background and scheduled handlers — triggered by events or cron, not called via SDK, POST /actions, or MCP. Ids use the tasks/ path (distinct from actions/).
Get Task Instance
@ossy/automation/tasks/get-task-instance
List Task Instances
@ossy/automation/tasks/list-task-instances
Save Task Instance
@ossy/automation/tasks/save-task-instance
Resource types
Structured entities and templates registered for resources.
Task Instance
@ossy/automation/schema/task-instance