惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

J
Java Code Geeks
G
Google Developers Blog
有赞技术团队
有赞技术团队
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客
博客园 - 聂微东
V
Visual Studio Blog
博客园_首页
D
DataBreaches.Net
腾讯CDC
I
InfoQ
F
Fortinet All Blogs
量子位
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 【当耐特】
Google DeepMind News
Google DeepMind News
人人都是产品经理
人人都是产品经理
云风的 BLOG
云风的 BLOG
月光博客
月光博客
Recent Announcements
Recent Announcements
MongoDB | Blog
MongoDB | Blog
C
Check Point Blog

Chat SDK Documentation

History | Chat SDK History | Chat SDK List a vendor-official adapter | Chat SDK Vercel Connect | Chat SDK Teams Low-Level APIs | Chat SDK CLI | Chat SDK Platform Adapters | Chat SDK State Adapters | Chat SDK Cards | Chat SDK Getting Started | Chat SDK Introduction | Chat SDK Modals | Chat SDK Slack Low-Level APIs | Chat SDK Streaming | Chat SDK Testing | Chat SDK Overview | Chat SDK toAiMessages | Chat SDK Cards | Chat SDK Overview | Chat SDK Markdown | Chat SDK Modals | Chat SDK AI SDK Tools | Chat SDK Types | Chat SDK Message Subject | Chat SDK Conversation History | Chat SDK Transcripts | Chat SDK Slack bot with Next.js and Redis Actions | Chat SDK Direct Messages | Chat SDK Emoji | Chat SDK
Approvals | Chat SDK
Vercel · 2026-07-22 · via Chat SDK Documentation

Pause a durable workflow until a human approves it in chat.

requestApproval from chat/workflow posts a card with Approve/Deny buttons and suspends a Workflow SDK workflow until a user clicks. The wait can last seconds or days and survives deploys and restarts. You don't need an approvals table, an onAction handler, or a polling loop.

import { requestApproval } from "chat/workflow";
import type { Thread } from "chat";

export async function deployApproval(opts: { thread: Thread; version: string }) {
  "use workflow";

  const { approved, user, timedOut } = await requestApproval(opts.thread, {
    title: `Deploy ${opts.version}?`,
    fields: { Version: opts.version },
    timeout: "24h",
  });

  if (approved) {
    await deploy(opts.version);
  }
}

async function deploy(version: string) {
  "use step";
  // Trigger your deploy here.
}

Start the workflow from any handler. Thread instances serialize across the workflow boundary automatically:

import { start } from "workflow/api";
import { deployApproval } from "@/workflows/deploy";

bot.onNewMention(async (thread, message) => {
  await start(deployApproval, [{ thread, version: "v1.2.3" }]);
});

Install the optional workflow peer dependency and configure your framework for Workflow SDK. Then register your Chat instance as a singleton at startup so threads can be revived on the other side of the workflow boundary:

chat.registerSingleton();
OptionTypeDescription
titlestringCard title (required)
subtitlestringRendered under the title
descriptionstringBody text (markdown) above the fields
fieldsRecord<string, string>Key/value pairs rendered as a bold-label list
approveLabel / denyLabelstringButton labels. Default: "Approve" / "Deny"
timeoutnumber | `${number}${"ms"|"s"|"m"|"h"|"d"}`Give up after this long. Omit to wait indefinitely
approversstring[]User IDs allowed to decide. Clicks from others post a notice and keep waiting
PropertyTypeDescription
approvedbooleanTrue when the approve button was clicked
timedOutbooleanTrue when timeout elapsed with no decision
user{ id: string; name?: string }Who decided. Absent on timeout

Once a decision lands (or the timeout elapses), the card is edited in place: the buttons are removed and replaced with an outcome line, leaving an audit trail in the thread and preventing stale clicks.

Anyone who can see the card can decide the approval. The click itself is trustworthy: Chat SDK verifies the platform's signature on the incoming event, and the button's callback URL never reaches the client. So the user.id on the result really is the person who clicked.

If only certain people should decide, pass approvers with their user IDs. When anyone else clicks, the bot posts a notice in the thread and the workflow keeps waiting:

await requestApproval(thread, {
  title: `Deploy ${version}?`,
  approvers: ["U_ALICE", "U_BOB"],
});

Set approvers for anything consequential.

The card builders are exported for cases the wrapper doesn't cover, such as posting an approval card whose buttons target a webhook you manage yourself:

import { buildApprovalCard, buildResolvedCard } from "chat/workflow";

const card = buildApprovalCard(
  { title: "Deploy?", fields: { Version: "v1.2.3" } },
  webhookUrl
);

The Human-in-the-Loop guide walks through the underlying pattern, including multi-stage approvals and validating approvers with createHook().

PreviousActionsNextSlash Commands