Headless integration flows that call endpoints and connectors, branch over results, and route data between services without a user interface.

API workflows connect systems together — transforming and routing data between services without a user interface. With a coding agent, you describe the integration and it produces a runnable workflow.

API workflows are headless integration flows: they call HTTP endpoints and Integration Service connectors, branch and loop over the results, and return a response. They suit work that runs behind the scenes — enriching a payload, fanning out calls across a list, or wiring one system to another. The agent authors the workflow and can validate and publish it for you.

To run an API workflow as one step in a longer, stateful process, a Maestro Flow can call it alongside approvals, people, and other systems.

This work is powered by the uipath-api-workflow skill, which authors and publishes API workflows. You can see it in the Skills catalog.

A first request might look like this:

"Build an API workflow that receives a webhook, enriches the payload from our Customer Relationship Management (CRM) system, and forwards it to the billing system."

You then refine the activities, control flow, and error handling in conversation with the agent.

For the full picture of connections and integrations, see the Integration Service documentation.