Workflows d’API (Aperçu)

Autopilot as a coding agent for API workflow projects in Studio Web: what you can do and the tools it uses.

Autopilot in Studio Web builds and edits API workflows using natural language — the same coding agent that ships with Studio Desktop, adapted to the API workflow project type.

Utilisez Autopilot pour:

• Build an API workflow from a plain-language description — Sequence, Assign, JavaScript, If, ForEach, DoWhile, TryCatch, Wait, and Response activities, including nested control flow.
• Look up and wire HTTP requests or Integration Service connector activities, such as Gmail, Outlook, GitHub, or Slack, using a pinged connection.
• Handle files as attachments — convert a file to base64 for an API call, or a base64 payload back into a file.
• Validate the workflow before you run it.
• Run it locally and test it against an eval set, looping until every case passes.
• Package and publish the workflow to Orchestrator.
• Operate a published workflow — invoke it, manage its Integration Service connections, and check job logs.

Outils

Before making changes, Autopilot reads the API workflow skill for the open project. It scaffolds, validates, packages, and publishes projects through the api-workflow and solution UiPath CLI (uip) command groups. It discovers and wires connector activities through the workflow's own registry lookup.

It also uses the platform skill for connections, assets, queues, and jobs on a published workflow. Running the workflow with authentication, or publishing it, can send real requests or ship to your tenant, so Autopilot asks for your confirmation first. It can also read, edit, and search project files, and create new API workflow projects at the solution level.

Limites connues

Support for API workflows in Studio Web is experimental: review generated workflows before you run or publish them. You can switch back to the classic Autopilot agent experience for API workflows from the chat title bar at any time.