External Invocations
A log of the calls made from outside ByteChef through your MCP servers and A2A servers: which tool or skill ran, how it ended, and how long it took.
When an AI client calls a tool on one of your MCP servers, or another agent calls a skill on one of your A2A servers, ByteChef records the call. External Invocations lists those records, so you can see which tools and skills are being used, which ones fail, and how long they take. Open it from External Invocations in the left sidebar, next to Workflow Executions.
The page is available on Enterprise Edition only.
A record holds the identity and outcome of a call only: which tool or skill ran, through which server, how it ended, and how long it took. The input parameters and the output are never stored.
What is recorded
A record is written for every call that comes in through one of two sources:
| Source | Calls recorded |
|---|---|
| MCP | Tool calls an AI client makes through an MCP server in the workspace: component tools, a component action exposed as a tool such as Slack's Send Message, and workflow tools, a project workflow exposed as a tool. |
| A2A | Skill calls another agent makes through an A2A server in the workspace. Each skill runs a project workflow. |
The call is recorded whether it succeeds or fails. A call to a tool, a skill or a server that is turned off is rejected before it runs and is not recorded.
For a workflow tool or an A2A skill, the record also carries the id of the workflow execution the call started, so you can find the run in Workflow Executions.
Calls to the management MCP server, such as listProjects or
buildWorkflow, are not recorded.
The page lists automation calls only. Calls made through an embedded integration are recorded separately and appear on the embedded External Invocations page.
Tool calls an AI Agent makes while a workflow runs are not recorded here either. They appear in the run's execution view, in the agent's call list, together with any approval a reviewer gave or refused.
The invocations table
Each call is one row, newest first:
| Column | What it shows |
|---|---|
| Status | How the call ended, for example SUCCESS, ERROR or TIMEOUT. |
| Name | The tool name the AI client called, or the name of the A2A skill. |
| Type | What was called: a Component tool or a Workflow tool through MCP, or a Skill through A2A. |
| Source | Where the call came in: MCP or A2A. |
| Server | The MCP server or the A2A server the call came through. |
| Target | What ran: the component and operation of a component tool, such as slack / sendMessage, or the name of the workflow a workflow tool or a skill ran. |
| Duration | How long the call took, in milliseconds. |
| Date | When the call was made. |
| Actions | View opens the workflow run a workflow tool or skill started, with the input and output of each step. Stop stops that run while it is still going: the call ended with TIMEOUT, APPROVAL_REQUIRED or SUSPENDED. Both are unavailable for component tool calls, which start no workflow run. |
The list shows 50 rows per page. Click the refresh button in the page header to load the latest calls.
How a workflow call ends
A workflow tool or an A2A skill starts a workflow run and waits for it. The status reflects where the run was when the call returned:
| Status | The workflow run |
|---|---|
SUCCESS | Completed, and the call returned its output. |
ERROR | Failed, could not start, or was stopped before it finished. |
TIMEOUT | Was still running when the call stopped waiting for it. |
APPROVAL_REQUIRED | Paused at an approval step and waits for a person to decide. |
SUSPENDED | Paused at a step such as a delay and continues on its own later. |
Filter invocations
| Filter | Narrows the list to |
|---|---|
| Source | Calls that came in through one source: MCP Servers or A2A Servers. |
| Status | Calls that ended one way: Success, Error, Connection required, Timeout, Approval required, Approval denied or Suspended. |
| MCP Server | Calls made through one MCP server. The filter appears when the workspace has at least one MCP server. |
| A2A Server | Calls made through one A2A server. The filter appears when the workspace has at least one A2A server. |
| Start date / End date | Calls made within a date range. |
Scope
The list is scoped to the current workspace and the current environment. Switching either one in the left sidebar reloads the list and clears the filters. A call made through a server in Production does not appear while you are looking at Development.
Who can see it
Organization admins see every workspace's invocations. Other users see a workspace's invocations when their workspace role lets them view workflows, which the built-in Viewer, Editor and Admin roles all do. Connected users of an embedded integration cannot read the log.
Retention
Records are deleted after 90 days. A cleanup job runs once a day, at 02:30 server time. In a multi-tenant installation it cleans up every tenant's records, and one tenant's failure does not stop the others.
| Property | Purpose |
|---|---|
bytechef.external-invocation-log.retention-days | How many days a record is kept. Defaults to 90. |
Related
- MCP Servers - expose component actions and workflows as tools to AI clients.
- A2A Servers - expose workflows as skills to other agents.
- Workflow Executions - the runs started when an AI client calls a workflow tool or an agent calls a skill.
How is this guide?
Last updated on