Use Integration Service with coding agents

Manage Integration Service connections, run connector operations, and diagnose failures from an AI coding agent using the UiPath CLI and UiPath skills.

A coding agent with UiPath skills installed can work with Integration Service from your terminal. You describe the outcome, and the agent runs the uip is commands that get you there. Once set up, your coding agent can:

• Find connectors and check which activities, objects, and triggers they expose
• List, test, create, and re-authenticate connections
• Read, create, update, and delete records in a connected application through a connection
• Look up trigger metadata and webhook URLs for event-driven automations
• Diagnose connection, activity, and trigger failures

Voraussetzungen

• UiPath CLI and UiPath skills installed for your coding agent. See Install and set up in the Coding Agents documentation.
• A logged-in CLI session (uip login) for the organization and tenant that hold your connections.
• The Integration Service tool for the CLI. It installs automatically the first time the agent runs a uip is command. To install it manually, run uip tools install is.

Hinweis:

After a CLI upgrade, run uip skills update --agent <name> to pick up the latest version of the skills.

The skills behind it

Two skills cover Integration Service work:

Fähigkeit	Was es tut
uipath-platform	Discovers connectors, manages connections, runs connector operations, and reads trigger and webhook metadata.
uipath-troubleshoot (preview)	Diagnoses Integration Service failures, such as expired connection tokens, failed activities, and triggers that don't fire.

Skills that build automations also use Integration Service when what you build calls a connector. For example, uipath-agents adds connector tools to an agent, and uipath-maestro-flow adds connector nodes to a flow. For availability and the full list, see the Skills catalog.

How the agent works with connections

The uipath-platform skill follows a fixed sequence: find the connector, choose a connection, test the connection, discover the operation, resolve reference fields, then run the operation. In practice, this means:

• The agent tests a connection before it uses it, even when the connection shows as enabled.
• The agent asks you to confirm the connection and any reference values, such as an account or a department, even when there is only one option.
• The agent refers to connections, connectors, and folders by name rather than by ID.
• If the connector has no activity for the operation you want, the agent works with the connector's objects directly. If no connector exists for the application, the agent can fall back to the HTTP connector.
• Creating or re-authenticating a connection opens the application's sign-in page in your browser. You complete the sign-in yourself.

Wichtig:

Record operations run against live data in the connected application, with the permissions of the connection's account. Review what the agent plans to change before it creates, updates, or deletes records.

Was Sie den Agenten fragen können

Beschreiben Sie in einfacher Sprache, was Sie benötigen. Der Agent wählt die entsprechenden uip is Befehle aus.

Discover connectors and operations

Ziel	Beispiel für einen Prompt
Find a connector	"Is there a connector for Zendesk, and do I already have a connection for it?"
Explore operations	"What can I do with the Salesforce connector? List its activities and the objects I can create or update."
Inspect fields	"Which fields are required to create a Jira issue?"

Manage connections

Ziel	Beispiel für einen Prompt
Zustandsprüfung	"Test every Salesforce connection across my folders and tell me which ones aren't working."
Erstellen Sie eine Verbindung	"Create a Slack connection for me."
Re-authenticate	"My Gmail connection expired. Re-authenticate it."
Change settings	"Make my Outlook connection the default for that connector and set its polling interval to 15 minutes."
Audit	"Export all connections in this tenant so I can review them."

Work with records

Ziel	Beispiel für einen Prompt
Read records	"List the open Zendesk tickets assigned to me."
Create records	"Create a HubSpot contact for each attendee in this CSV file."
Update records	"Change the priority of the Jira issue [issue key] to High."

Triggers and webhooks

Ziel	Beispiel für einen Prompt
Explore trigger events	"Which events can a Salesforce trigger watch on the Opportunity object, and which fields can I filter on?"
Get a webhook URL	"Get the webhook URL for the webhook trigger on my [connector] connection."

Fehlersuche und ‑behebung

These prompts use the uipath-troubleshoot skill, which is in preview and may change.

Ziel	Beispiel für einen Prompt
Verbindungsfehler	„Warum gibt meine Salesforce-Verbindung einen 401 zurück?“
Trigger not firing	"My Jira trigger hasn't started its process since yesterday. Find out why."
Failed activity	"My job failed on the Outlook Send Email activity. Find the cause and tell me how to fix it."

Siehe auch

• uip is reference: full command reference for the Integration Service tool.
• Install and set up: install the CLI and skills.
• Skills catalog: the full list of available UiPath skills.
• Connections: how connections work in Integration Service.
• Triggers: how Integration Service triggers start automations.