API workflows (Preview)

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.

What you build

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.

The skill behind it

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 typical starting prompt

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.

More prompts to try

• Build an API workflow that fetches the 10 most recent pull requests from a GitHub repo via the GitHub connection.
• Create an API workflow that validates an input, classifies it, and falls back on error.
• Create an API workflow that loops over a list of records and posts each to an HTTP endpoint.

Go deeper

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