integration-service
latest
false
- 入门指南
- 通知
- 许可
- 故障排除
- 连接器生成器
- Act! 365
- ActiveCampaign
- Active Directory - 预览版
- Adobe Acrobat Sign
- Adobe PDF 服务
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- 亚马逊 SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI 文档智能
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- 清除位
- Confluence Cloud
- Constant Contact
- Coupa
- CrewAI – 预览版
- Customer.io
- 数据库 Hub - 预览版
- Databricks智能体
- Datadog
- 深度查找
- Deputy
- Discord - 预览
- DocuSign
- 水滴
- Dropbox
- Dropbox Business
- Egnyte
- Eventbrite
- 汇率
- Exchange Server - 预览
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- 获取响应
- GitHub
- Gmail
- 谷歌云平台
- Google 文档
- Google 云端硬盘
- Google 表单 - 预览
- Google Maps
- Google 表格
- Google 语音转文本
- Google 文本转语音
- Google Tasks - 预览
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP
- About the HTTP connector
- HTTP connector authentication
- HTTP Webhook - 预览
- HubSpot CRM
- HubSpot Marketing
- HyperV - 预览
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- 邮件
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive 和 SharePoint
- Microsoft Outlook 365
- Microsoft Power Automate – 预览版
- Microsoft Sentiment
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- 奥克塔
- OpenAI
- 符合 OpenAI V1 的 LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- 贝宝
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce 代理强制和流程 – 预览
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - 预览
- 探戈卡
- Todoist
- Trello
- Twilio
- UiPath Apps - Preview
- UiPath Data Fabric – 预览
- UiPath 生成式 AI 活动
- UiPath Orchestrator
- X(以前称为 Twitter)
- Xero
- WatsonX.ai
- WhatsApp Business
- WOO COMMERCE
- 可行
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- 缩放
- Zoom 信息
重要 :
请注意,此内容已使用机器翻译进行了本地化。
Integration Service 中提供的连接器包采用的是机器翻译的译文。
新发布内容的本地化可能需要 1-2 周的时间才能完成。

Integration Service 用户指南
上次更新日期 2025年11月20日
HTTP Authentication
先决条件
To create a connection using the HTTP connector, you must provide the details needed for the selected authentication type. See the following sections for information on the details required for each authentication type. For information on how to retrieve these details, refer to the documentation of the API provider.
UiPath User Access Token
Establish a connection through supported UiPath services. No configuration required.
OAuth 2.0 授权代码
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
- Client secret - The confidential secret key for your application as provided by your OAuth provider.
- Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/authorize). - Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/token). - Scope - The required OAuth scopes based on your API provider or integration needs.
Additional configuration:
- Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g.
https://example.com/docs/oauth/refresh) - Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (
https://example.com/docs/oauth/revoke). - Refresh interval - Time in seconds between OAuth token refresh attempts.
- OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.
使用 PKCE 的 OAuth 2.0 授权代码
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
- Client secret - The confidential secret key for your application as provided by your OAuth provider.
- Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/authorize). - Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/token). - Scope - The required OAuth scopes based on your API provider or integration needs.
Additional configuration:
- Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g.
https://example.com/docs/oauth/refresh) - Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (
https://example.com/docs/oauth/revoke). - Refresh interval - Time in seconds between OAuth token refresh attempts.
- OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.
OAuth 2.0 客户端凭据
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
- Client secret - The confidential secret key for your application as provided by your OAuth provider.
- Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/token). - Scope - The required OAuth scopes based on your API provider or integration needs.
Additional configuration:
- Refresh interval - Time in seconds between OAuth token refresh attempts.
- OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.
OAuth 2.0 密码
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Username - The end-user's username credential for authentication.
- Password - The end-user's password credential for authentication.
- Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
- Client secret - The confidential secret key for your application as provided by your OAuth provider.
- Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/authorize). - Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/token). - Scope - The required OAuth scopes based on your API provider or integration needs.
Additional configuration:
- Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g.
https://example.com/docs/oauth/refresh). - Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (
https://example.com/docs/oauth/revoke). - Refresh interval - Time in seconds between OAuth token refresh attempts.
- OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.
基本身份验证
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Username - The username credential for your API account.
- Password - The password credential for your API account.
Additional configuration:
- Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g. /api/v1/me, /user/profile, /auth/validate). This API route should return a successful response when your credentials are valid.
API 密钥
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Parameter name - The exact name of the API key parameter as required by your API (e.g.
X-API-Key,api_key,Authorization). This will be used as either a header name or query parameter name based on your selection. - Value - Your complete API key value as provided by your API provider. This will be securely stored and used for authentication.
Additional configuration:
- Add to - Select whether to add the API key in the request header or as a query parameter. Header is recommended for better security.
- Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g. /api/v1/me, /user/profile, /auth/validate). This API route should return a successful response when your credentials are valid.
OAuth 2.0 JWT Bearer
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
- Client secret - The confidential secret key for your application as provided by your OAuth provider.
- JWT base64 encoded key - Your Base64-encoded private key. Ensure you follow your API provider's instructions for key generation and encoding.
- Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/authorize). - Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g.
https://login.example.com/oauth2/token). - Scope - The required OAuth scopes based on your API provider or integration needs.
Additional configuration:
- Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g.
https://example.com/docs/oauth/refresh). - Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (
https://example.com/docs/oauth/revoke). - Refresh interval - Time in seconds between OAuth token refresh attempts.
- OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.
个人访问令牌
提供以下详细信息:
- Connection name - A descriptive name to help you identify this connection.
- Base URL - The base URL of your API (e.g.
https://api.example.com). - Token prefix - The token prefix (e.g.
Bearer,Token,Basic). This will be combined with your token in the Authorization header. Leave empty if no prefix is required. - Token - The complete personal access token value. This will be combined with the token type in the Authorization header (e.g.
Bearer your-token-here).
Additional configuration:
- Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g.
/api/v1/me,/user/profile,/auth/validate). This API route should return a successful response when your credentials are valid.
Add the HTTP connection
- 从左侧栏中选择“Integration Service”。
- From the Connectors list, select HTTP. You can also use the search bar to find the connector.
- Select the Connect to HTTP button.
- In the connection screen, provide the required details.
- Select Connect.
- 已添加您的连接。