Skip to main content

uip is activities

uip is activities lists the operations a connector exposes. Activities are the named actions (CreateTicket, ListAllRecords, etc.) that an automation can drive against a connector — they map onto HTTP methods and connector objects under the hood. Results are cached per-connector-and-tenant; pass --refresh to re-fetch.

Synopsis​

uip is activities <verb> [options]

Verbs​

VerbPurpose
listList the activities a connector exposes. With --triggers, list trigger activities only.

uip is activities list​

List activities for a connector. By default, trigger activities are excluded; pass --triggers to list only triggers.

Arguments​

NameRequiredPurpose
<connector-key>yesConnector key, for example uipath-zoho-desk.

Options​

ShortLongValueDefaultDescription
-t--tenantnamesession defaultOverride the tenant.
—--refreshflagoffForce re-fetch from the API, ignoring cache.
—--triggersflagoffList trigger activities only. Switches Code to TriggerActivityList.

Examples​

uip is activities list uipath-zoho-desk

# Trigger activities only
uip is activities list uipath-zoho-desk --triggers

# Just the activity names
uip is activities list uipath-zoho-desk \
    --output-filter 'Data[].Name'

Data shape (--output json)​

{
  "Code": "ActivityList",
  "Data": [
    {
      "Name": "CreateTicket",
      "DisplayName": "Create Ticket",
      "Description": "Create a new ticket in Zoho Desk.",
      "ObjectName": "create_ticket",
      "MethodName": "POST",
      "Operation": "N/A",
      "IsCurated": "Yes"
    },
    {
      "Name": "ListAllRecords",
      "DisplayName": "List Records",
      "Description": "Retrieve and list records from Zoho Desk.",
      "ObjectName": "N/A",
      "MethodName": "N/A",
      "Operation": "List",
      "IsCurated": "No"
    }
  ]
}

With --triggers, the response uses Code: "TriggerActivityList" and the same per-row shape.

See also​