Skip to main content

8. System tasks

Activities

Each activity type on page 5 is implemented by an activity function in the engine. Activities are the only place the engine calls anything outside itself. Every activity is idempotent on (run id, task reference, attempt): running it twice with the same key has the same effect as once.

ActivityWhat it callsNotes
HttpActivityAny URL, through the gatewayAlso reaches Logic Apps connectors and Document Intelligence.
JsonActivityNothingJSONPath extraction and object construction.
LlmActivityA Foundry model, through the gateway's AI policiesPage 14.
ToolActivityThe gateway's tool endpoint for the workflow's trust tierSends header x-yml-workflow: name@version. Page 14.
AgentActivityAn agent registered on the gateway, over the A2A protocolSends the goal, then polls the agent until it reports a terminal state. Page 14.
EventActivityAn Event Grid or Service Bus topic
QueueActivityThe Service Bus queue for a worker task typeUsed internally for WORKER tasks.
RecordActivityAzure SQLWrites run and task history rows. Publishes status events when enabled.

Output cache

A task with cacheConfig: {key, ttlInSecond} reuses a previous output for the same key within the TTL. For LLM_CHAT the cache is the gateway's semantic cache. For other activities it is the task_cache table in Azure SQL.

Outbound restrictions

HttpActivity calls go through the gateway, which allows only registered destinations. LlmActivity and ToolActivity call only the gateway. No activity opens a connection to an arbitrary address.

Systems without an API

NeedHow
A SaaS system such as Xero, SharePoint, Outlook, DataverseA Logic Apps Standard workflow with the connector, exposed as an HTTP endpoint, called with HTTP.
Text and fields from a PDF or imageAzure AI Document Intelligence, called with HTTP.
A business action on the organisation's dataA tool on the action service, called with CALL_TOOL.
Anything elseA worker. Page 9.