Design of the Action Connector Layer in Enterprise Agentic Workflow Automation Platforms

An enterprise agent may produce a valid tool call while the connected system rejects the request, accepts it for later processing, or changes a record without returning confirmation. The action connector layer must preserve these distinctions. This article develops a design model for that layer by analyzing recent research on Application Programming Interface (API) use, stateful tool execution, and agent security. It specifies an action contract with typed inputs, preconditions, an authority scope, an expected effect, and defined outcomes. The model classifies integrations by credential ownership and the extent of control over the service interface. It then relates validation errors, authorization failures, provider rejections, and uncertain execution states to permissible agent responses. A versioned contract provides multiple agents with a common definition of an action, while the connector enforces permissions and interprets the external response. The proposed specifications support connector review, provider changes, and the diagnosis of failures across enterprise workflows.

Authors

Publication Details

Journal
International Journal of Computer (IJC)
Published
2026-11-13
Primary Topic
Service-Oriented Architecture and Web Services
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
article

Design of the Action Connector Layer in Enterprise Agentic Workflow Automation Platforms

Nitin Garg
International Journal of Computer (IJC)
Service-Oriented Architecture and Web Services
article

Design of the Action Connector Layer in Enterprise Agentic Workflow Automation Platforms

Nitin Garg
article en

Abstract

An enterprise agent may produce a valid tool call while the connected system rejects the request, accepts it for later processing, or changes a record without returning confirmation. The action connector layer must preserve these distinctions. This article develops a design model for that layer by analyzing recent research on Application Programming Interface (API) use, stateful tool execution, and agent security. It specifies an action contract with typed inputs, preconditions, an authority scope, an expected effect, and defined outcomes. The model classifies integrations by credential ownership and the extent of control over the service interface. It then relates validation errors, authorization failures, provider rejections, and uncertain execution states to permissible agent responses. A versioned contract provides multiple agents with a common definition of an action, while the connector enforces permissions and interprets the external response. The proposed specifications support connector review, provider changes, and the diagnosis of failures across enterprise workflows.

International Journal of Computer (IJC)
Service-Oriented Architecture and Web Services
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon