integration-service
latest
false
重要 :
请注意,此内容已使用机器翻译进行了本地化。 Integration Service 中提供的连接器包采用的是机器翻译的译文。 新发布内容的本地化可能需要 1-2 周的时间才能完成。
UiPath logo, featuring letters U and I in white

Integration Service 用户指南

上次更新日期 2025年11月19日

Flex 许可

备注:

The information on this page applies to you if you are on Flex. If you are on Unified Pricing, refer to Unified Pricing licensing.

Integration Service 许可证和权利

下表列出了允许您访问 Integration Service 的许可证、与每个许可证关联的计划及其启用的权利。

表格 1. 许可计划

功能社区空闲Pro企业
访问连接器

Table 2. API calls allotment per platform tier

Platform Tier层级Integration activities or Platform Units granted
User tierUiPath - Flex - Action Center - Named User​3,000 API calls per month
User tierUiPath - Flex - Attended - Named User3,000 API calls per month
User tierUiPath - Flex - Automation Developer - Named User5,000 API calls per month
User tierUiPath - Flex - Citizen Developer - Named User3,000 API calls per month
Robot tierUiPath - Cloud - Robot Units Bundle - 72K ​5,000 API calls per month
Robot tierUiPath - Flex - Unattended Robot ​5,000 API calls per month
Robot tierUiPath - Flex - Unattended Robot - Test​3,000 API calls per month
Platform tierUiPath - Flex - Platform - Standard ​
Platform tierUiPath - Flex - Platform - Enterprise ​
Platform Individual SKUsUiPath - Flex - Integration Service API Calls Bundle - 3M​3 million per year
Platform Individual SKUsUiPath - Flex - Integration Service API Calls Bundle - 6M​6 million per year

Integration Service uses Service licenses, which can be distributed to your organizations and tenants. They target a specific metric, in this case, service consumption units, represented by Integration Service API calls.

消耗单位

Integration Service uses API calls as a measure of consumption for executed Integration Activities. The consumption of API calls occurs in the following way: for every 1 executed activity, 5 API calls are used.

Table 2. Consumption rates based on process source

流程来源消耗率
API 工作流1 个活动 = 5 次 API 调用
智能体1 个活动 = 5 次 API 调用
Maestro1 个活动 = 5 次 API 调用
RPA Workflows (executed by attended, unattended, or serverless robots)1不计量

1 Integration Activities used in RPA Workflows, executed by attended, unattended, or serverless robots, are charged via the robot’s runtime licensing and are not metered separately.

每当 Integration Service 向外部第三方应用程序发出请求时,都会使用一次 API 调用,无论是手动启动、通过 Attended 自动化还是通过 Unattended 流程启动。已执行的活动可能涉及多次 API 调用。例如,单个连接器活动可能调用多个端点或执行重试,从而消耗多个 API 调用。

过度消耗

如果超出分配的月度或年度 API 调用分配量:

  • 不强制执行执行块机制。即使在超出 API 调用配额后,自动化也会继续运行。过度使用的 API 调用目前不会产生费用。

许可证类型

您的组织主要通过两种方式使用 Integration Service API 调用:

  • Bundled with License: This pool represents the Integration Service API calls included with the user-based and robot-based licenses (e.g., Developer, Attended, Unattended, or Autopilot-related tiers) that your organization has subscribed to. These API calls are allocated monthly and typically reset on the first day of each month. The number of calls included varies by license type and edition.
    • Enterprise license: along with API Calls allocated for User and Bot, this pool includes the additional 100K API calls allocated from the Autopilot Express license.
    • Pro and ProTrial licenses: along with API Calls allocated for User and Bot, this pool includes the additional 25K API calls allocated from the Autopilot Express license.
    • Free license: The pool includes the 0-25K API calls allocated from the Autopilot Express license.
  • Dedicated API Call Bundles: This pool represents the Platform SKU your organization has licensed. The API Calls allocated on your plan are from licensing one of the following Platform Individual SKUs:
    • UiPath - Flex - Integration Service API Calls Bundle - 3M
    • UiPath - Flex - Integration Service API 调用捆绑包 - 6M
备注:

For details regarding all SKUs relevant to Integration Service, refer to the UiPath licensing platform.

检查许可证分配

要查看组织范围内的许可证分发情况,请登录 Automation Cloud TM ,然后转到“管理员” > “您的组织” > “许可证”

The Licenses dashboard shows the number of all purchased licenses in your organization. You can switch to the Consumables tab to view license information for Integration Service.

API 调用优先级逻辑

每当通过 Integration Service 向外部第三方应用程序发出请求时,均可视为已使用 API 调用。无论请求的启动方式是手动触发、通过 Attended 自动化还是 Unattended 流程触发,都根据此类请求的总数计算消耗量。

以下示例展示了如何在 Flex 许可计划中计算 API 调用使用情况以及如何确定 API 调用使用情况的优先级。它说明了组织如何从基于许可证的捆绑包和其他 API 调用捆绑包中利用其分配的 API 调用,以及使用情况如何影响每月使用量的未来可用性。

如果捆绑包和专用捆绑包都可用:

  • 首先从包月捆绑许可证池中使用。
  • 一旦用完,即可继续使用专用捆绑包。

示例:

  • 您的组织拥有:
    • 10 个 Automation Developer 许可证(10 * 5,000 = 50,000 次 API 调用)
    • 10 个无人值守机器人许可证(10 * 5,000 = 50,000 次 API 调用)
    • 3M API 调用捆绑包(年度)

每月总数:100,000 次捆绑调用。

2023 年 10 月,使用了 125,000 次调用:

  • 100,000 个取自捆绑许可证
  • 25,000 个从专用捆绑包中获取

从 11 月 1 日开始,捆绑包数量将重置为 100,000,3M 池减少到 2,975,000。

  • Integration Service 许可证和权利
  • 消耗单位
  • 过度消耗
  • 许可证类型
  • 检查许可证分配
  • API 调用优先级逻辑

此页面有帮助吗?

获取您需要的帮助
了解 RPA - 自动化课程
UiPath Community 论坛
Uipath Logo
信任与安全
© 2005-2025 UiPath。保留所有权利。