> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/cards-overview/and/logic/send-https-request.md).

# 发送 HTTPS 请求

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-5b9196562959f136ec666e39bd56a05505374d78%2Fimage%20(47).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## **用途：**

此 DocBits 卡片用于向指定 URL 发送 HTTPS 请求，以便与外部系统交互。它可以通过 API 调用执行数据检索、更新或删除等操作，确保与外部服务无缝集成。

## **功能：**

* \*\*执行 HTTPS 请求：\*\*卡片使用配置的 HTTP 方法（例如 GET、POST、PUT、DELETE）向指定 URL 发送请求。
* \*\*请求头和参数：\*\*用户可以添加自定义请求头和查询参数，以确保请求符合外部 API 的要求。
* \*\*请求数据：\*\*用户可以定义随请求发送的数据载荷（如适用），例如 JSON 数据或表单编码数据。
* \*\*响应评估：\*\*工作流会检查收到的状态码是否与预期值匹配，确保通信成功后再继续。
* **支持的 HTTP 方法：**
  * GET：从指定 URL 获取数据。
  * POST：向指定 URL 提交数据以创建资源。
  * PUT：更新指定 URL 上的现有资源。
  * DELETE：删除指定 URL 上的资源。

## **用法：**

当工作流需要与外部 API 交换数据时，此卡片尤其有用，例如向 CRM 发送更新、检索订单状态，或向数据库提交新条目。

## **示例场景：**

* 用户配置此卡片，向外部订单管理系统发送 POST 请求，并在请求载荷中包含新订单详情。用户添加自定义请求头，以包含 API 身份验证令牌。卡片设置为仅在响应状态码为 201（Created）时继续。如果状态码不同，工作流会触发错误通知，以便人工介入。

使用“发送 HTTPS 请求”卡片，组织可以自动化外部集成、改善系统间通信，并简化复杂工作流。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/cards-overview/and/logic/send-https-request.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
