[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-zh-\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api":3},{"page":4,"surround":635},{"id":5,"title":6,"authors":7,"badge":10,"body":11,"date":620,"demo-cta":621,"description":622,"extension":623,"genre":624,"heroOrder":625,"icp":626,"image":629,"meta":630,"navigation":243,"no-translate":621,"path":631,"rank-country":625,"rank-keywords":625,"rank-tag":625,"seo":632,"stem":633,"updated":625,"video":243,"__hash__":634},"blog_zh\u002Fblog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api.md","如何将会议总结发送至您的 CRM、帮助台或电子表格：Zapier、Webhook 或 API（2026）",[8],{"name":9},"The Mind.com Team","Guide",{"type":12,"value":13,"toc":609},"minimark",[14,19,28,31,35,122,125,129,142,146,194,197,200,206,209,251,274,337,345,374,378,385,476,487,490,497,500,503,509,515,524,539,552,555,593,605],[15,16,18],"h1",{"id":17},"如何将会议纪要发送至您的-crm客服系统或电子表格zapierwebhook-或-api-2026","如何将会议纪要发送至您的 CRM、客服系统或电子表格：Zapier、Webhook 或 API (2026)",[20,21,22,23,27],"p",{},"客户通话纪要只有在下一位查看者会去寻找的地方才能发挥作用：CRM 中的商机、客服系统中的工单、团队已维护的表格行中。如果您搜索过“自动将会议笔记发送至 HubSpot”或“Zapier 会议纪要”，对于 InterMIND 的简短回答是：通过 API 密钥将其连接至 Zapier 一次，",[24,25,26],"strong",{},"Meeting Recap Ready"," 触发器就会在每次您主持的会议生成摘要的瞬间触发。本指南是完整版——包括无代码方式、Webhook、API、每种方式携带的内容，以及完全无需集成的方式。",[20,29,30],{},"首先说明每份纪要的一个特性，因为它会影响进入 CRM 的内容：摘要以阅读者的语言送达，每位参与者都能以自己的语言阅读。下方的有效载荷以单一语言（主持人的语言）携带摘要，并在有效载荷中注明了语言。",[32,33,34],"h2",{"id":34},"四种接入方式",[36,37,38,54],"table",{},[39,40,41],"thead",{},[42,43,44,48,51],"tr",{},[45,46,47],"th",{},"方式",[45,49,50],{},"适用对象",[45,52,53],{},"您需要设置的",[55,56,57,71,84,109],"tbody",{},[42,58,59,65,68],{},[60,61,62],"td",{},[24,63,64],{},"通过电子邮件发送纪要副本",[60,66,67],{},"任何人；无需集成",[60,69,70],{},"将工具的入站地址添加为会议或频道的纪要副本收件人",[42,72,73,78,81],{},[60,74,75],{},[24,76,77],{},"Zapier",[60,79,80],{},"无需代码",[60,82,83],{},"一个 API 密钥，然后在触发器和操作上配置 Zaps",[42,85,86,95,98],{},[60,87,88],{},[24,89,90,91],{},"Webhook ",[92,93,94],"code",{},"recap.ready",[60,96,97],{},"开发者，或 Make \u002F n8n \u002F Pipedream",[60,99,100,101,104,105,108],{},"一个带有公开 ",[92,102,103],{},"https:\u002F\u002F"," URL 的 ",[92,106,107],{},"POST \u002Fwebhooks"," 订阅",[42,110,111,116,119],{},[60,112,113],{},[24,114,115],{},"API",[60,117,118],{},"开发者，AI 代理",[60,120,121],{},"一个个人密钥，三个端点，OpenAPI 3.1",[20,123,124],{},"所有四种方式在每个注册账户上均可用。访客无法创建密钥。",[32,126,128],{"id":127},"无需集成的方式纪要副本","无需集成的方式：纪要副本",[20,130,131,132,135,136,141],{},"大多数 CRM、客服系统和跟踪工具都有一个入站电子邮件地址，可将邮件转换为笔记或工单。将该地址添加为会议或频道的",[24,133,134],{},"纪要副本收件人","，每次会话结束后摘要都会通过电子邮件发送至此——每位主持人最多可设置十个地址，每个地址通过一次测试邮件确认，可应用于您的所有会议或特定频道或会议。详情请参阅",[137,138,140],"a",{"href":139},"\u002Fdocs\u002Fmeetings\u002Frecap","纪要文档","。如果这已满足您的工具需求，您可以在此停止。",[32,143,145],{"id":144},"zapier触发器和操作","Zapier：触发器和操作",[147,148,149,172,182,188],"ol",{},[150,151,152,155,156,159,160,163,164,167,168,171],"li",{},[24,153,154],{},"创建密钥。"," 打开 ",[24,157,158],{},"Settings","，找到 ",[24,161,162],{},"API keys"," 卡片，点击 ",[24,165,166],{},"Create key","，将其标记为“Zapier”并复制密钥。它以 ",[92,169,170],{},"imk_"," 开头，仅显示一次——InterMIND 仅存储其哈希值。每个账户最多可有十个密钥；可随时在同一卡片中吊销密钥。",[150,173,174,177,178,181],{},[24,175,176],{},"连接。"," 在 Zapier 中，将 ",[24,179,180],{},"InterMIND"," 应用添加到 Zap 中，并在提示时粘贴密钥。连接将以您的账户电子邮件进行标记。",[150,183,184,187],{},[24,185,186],{},"触发器：Meeting Recap Ready。"," 在您主持的每次会议结束且摘要生成后触发一次。字段包括：会议标题和链接、纪要链接、转录链接、Markdown 格式的摘要、摘要语言、开始和结束时间、参与者姓名和电子邮件、主持人。",[150,189,190,193],{},[24,191,192],{},"操作：Create Meeting Link。"," 创建一个您拥有的临时会议并返回其 URL——将其放入 CRM 商机、支持工单或日历邀请中。任何打开该链接的人都是在敲门，您可以在会议室中准入他们。",[20,195,196],{},"典型 Zaps：纪要 → HubSpot 商机上的新笔记；纪要 → Zendesk 工单上的内部评论；纪要 → Google Sheets 中的行；新的 Pipedrive 商机 → 将会议链接写回该商机。",[20,198,199],{},"通过 Make、n8n 或 Pipedream 的通用 Webhook 和 HTTP 模块，利用下文的 Webhook 和 API 也能实现相同的集成。",[32,201,203,204],{"id":202},"webhookrecapready","Webhook：",[92,205,94],{},[20,207,208],{},"订阅一次：",[210,211,216],"pre",{"className":212,"code":213,"language":214,"meta":215,"style":215},"language-http shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","POST https:\u002F\u002Fintermind.com\u002Fapi\u002Fv1\u002Fwebhooks\nAuthorization: Bearer imk_…\nContent-Type: application\u002Fjson\n\n{ \"target_url\": \"https:\u002F\u002Fexample.com\u002Fhooks\u002Fintermind\", \"event\": \"recap.ready\" }\n","http","",[92,217,218,226,232,238,245],{"__ignoreMap":215},[219,220,223],"span",{"class":221,"line":222},"line",1,[219,224,225],{},"POST https:\u002F\u002Fintermind.com\u002Fapi\u002Fv1\u002Fwebhooks\n",[219,227,229],{"class":221,"line":228},2,[219,230,231],{},"Authorization: Bearer imk_…\n",[219,233,235],{"class":221,"line":234},3,[219,236,237],{},"Content-Type: application\u002Fjson\n",[219,239,241],{"class":221,"line":240},4,[219,242,244],{"emptyLinePlaceholder":243},true,"\n",[219,246,248],{"class":221,"line":247},5,[219,249,250],{},"{ \"target_url\": \"https:\u002F\u002Fexample.com\u002Fhooks\u002Fintermind\", \"event\": \"recap.ready\" }\n",[20,252,253,254,257,258,261,262,265,266,269,270,273],{},"响应为 ",[92,255,256],{},"201","，包含订阅的 ",[92,259,260],{},"id"," 和一个 ",[92,263,264],{},"secret","。此后，每当",[24,267,268],{},"您主持","的会议生成带有非空摘要的最终纪要时，InterMIND 就会向目标 URL 发送一次每次会议会话的 ",[92,271,272],{},"POST"," 请求，包含以下标头：",[36,275,276,286],{},[39,277,278],{},[42,279,280,283],{},[45,281,282],{},"标头",[45,284,285],{},"值",[55,287,288,299,313,325],{},[42,289,290,295],{},[60,291,292],{},[92,293,294],{},"X-InterMIND-Event",[60,296,297],{},[92,298,94],{},[42,300,301,306],{},[60,302,303],{},[92,304,305],{},"X-InterMIND-Delivery",[60,307,308,309,312],{},"事件的唯一 ID（",[92,310,311],{},"\u003Cmeeting id>.\u003Csession id>","）——用于去重",[42,314,315,320],{},[60,316,317],{},[92,318,319],{},"X-InterMIND-Signature",[60,321,322],{},[92,323,324],{},"sha256=\u003C使用订阅的 secret 对原始正文进行 HMAC-SHA256 计算的结果>",[42,326,327,332],{},[60,328,329],{},[92,330,331],{},"User-Agent",[60,333,334],{},[92,335,336],{},"InterMIND-Webhooks\u002F1",[20,338,339,340,344],{},"正文携带会议信息（id、标题、url、类型）、纪要（url、转录 url、Markdown 格式的摘要、其语言）、会话的开始和结束时间、参与者姓名和电子邮件，以及主持人。完整示例请参阅 ",[137,341,343],{"href":342},"\u002Fdocs\u002Fintegrations\u002Fapi-zapier","API 文档","。",[20,346,347,348,351,352,355,356,359,360,355,363,366,367,370,371,373],{},"交付规则，确保不会静默丢失任何内容：您的端点需在 8 秒内响应 ",[92,349,350],{},"2xx","；网络错误、",[92,353,354],{},"5xx"," 或 ",[92,357,358],{},"429"," 将立即重试一次；",[92,361,362],{},"410",[92,364,365],{},"404"," 会删除订阅；任何其他失败都会被记录且不再重发该事件——纪要电子邮件和纪要页面将作为持久记录。",[92,368,369],{},"target_url"," 必须为 ",[92,372,103],{}," 且可公开访问；私有网络地址将被拒绝。每个账户允许二十个订阅。",[32,375,377],{"id":376},"api三个端点和一个契约","API：三个端点和一个契约",[20,379,380,381,384],{},"基础 URL 为 ",[92,382,383],{},"https:\u002F\u002Fintermind.com\u002Fapi\u002Fv1","，输入输出均为 JSON 格式，密钥作为 Bearer 令牌。密钥仅在这些端点上有效；它们绝不会授予对 Web 应用程序自身 API 的访问权限。",[36,386,387,400],{},[39,388,389],{},[42,390,391,394,397],{},[45,392,393],{},"方法",[45,395,396],{},"路径",[45,398,399],{},"用途",[55,401,402,417,438,452],{},[42,403,404,409,414],{},[60,405,406],{},[92,407,408],{},"GET",[60,410,411],{},[92,412,413],{},"\u002Fme",[60,415,416],{},"密钥的所有者：id、电子邮件、姓名",[42,418,419,423,428],{},[60,420,421],{},[92,422,272],{},[60,424,425],{},[92,426,427],{},"\u002Fmeetings",[60,429,430,431,434,435,437],{},"创建临时会议链接；可选 ",[92,432,433],{},"{ \"title\": \"…\" }","；返回 ",[92,436,256],{}," 及 id、url、标题",[42,439,440,444,449],{},[60,441,442],{},[92,443,408],{},[60,445,446],{},[92,447,448],{},"\u002Frecaps?limit=3",[60,450,451],{},"您的最新纪要（1–10 条），按最新排序，格式与 Webhook 有效载荷相同",[42,453,454,464,473],{},[60,455,456,458,459,458,461],{},[92,457,408],{}," \u002F ",[92,460,272],{},[92,462,463],{},"DELETE",[60,465,466,469,470],{},[92,467,468],{},"\u002Fwebhooks",", ",[92,471,472],{},"\u002Fwebhooks\u002F{id}",[60,474,475],{},"列出、订阅、取消订阅",[20,477,478,479,482,483,344],{},"机器可读的契约——适用于 Make、n8n、Pipedream 和 AI 代理的 OpenAPI 3.1——位于 ",[92,480,481],{},"https:\u002F\u002Fintermind.com\u002Fapi\u002Fv1\u002Fopenapi.json","。支持 MCP 的 AI 助手（Claude、ChatGPT、Copilot、Gemini）无需密钥即可创建会议链接并读取纪要——该路径请参阅 ",[137,484,486],{"href":485},"\u002Fblog\u002Fmcp-servers-for-meeting-tools","MCP 指南",[32,488,489],{"id":489},"交付内容及其语言",[20,491,492,493,496],{},"有效载荷中的摘要是单一语言的一段文本——即主持人的摘要语言，在 ",[92,494,495],{},"recap.language"," 字段中注明。从有效载荷链接到的纪要页面是每位参与者打开的页面，在那里每位已登录的参与者都能以自己的语言阅读摘要。因此 CRM 笔记是主持人的版本；其上的链接会打开适合每位阅读者语言的版本。",[20,498,499],{},"纪要和转录链接对已登录的会议参与者开放。会议的访客既不会获得链接也不会收到电子邮件——正是账户的存在使得通话后的部分能够被触达。",[32,501,502],{"id":502},"常见问题",[20,504,505,508],{},[24,506,507],{},"我可以不通过集成将会议摘要导入 HubSpot 或 Zendesk 吗？","\n可以。将工具的入站电子邮件地址添加为会议或频道的纪要副本收件人——每次会话后摘要都会通过电子邮件发送至此，无需密钥和 Zap。",[20,510,511,514],{},[24,512,513],{},"如何将 InterMIND 连接到 Zapier？","\n在 Settings → API keys 中创建一个 API 密钥，将 InterMIND 应用添加到 Zap 中并粘贴密钥。使用 Meeting Recap Ready 触发器和 Create Meeting Link 操作。",[20,516,517,520,521,523],{},[24,518,519],{},"Webhook 会对我仅参加的会议触发吗？","\n不会。",[92,522,94],{}," 仅针对您主持的会议发送，每次会话一次，且在摘要非空时发送。",[20,525,526,529,530,355,532,534,535,538],{},[24,527,528],{},"如果纪要生成时我的端点宕机了怎么办？","\n网络错误、",[92,531,354],{},[92,533,358],{}," 将立即重试一次。如果重试失败，该事件将被记录且不再重发；纪要电子邮件和纪要页面将作为记录保留，",[92,536,537],{},"GET \u002Frecaps"," 可按需返回最新的十条。",[20,540,541,544,545,548,549,551],{},[24,542,543],{},"Webhook 是否有签名？","\n是的。每次交付都携带 ",[92,546,547],{},"X-InterMIND-Signature: sha256=\u003C使用您的订阅 secret 对原始正文进行 HMAC-SHA256 计算的结果>"," 以及一个唯一的 ",[92,550,305],{}," ID 用于去重。",[32,553,554],{"id":554},"试试看",[556,557,558,567,576,584],"ul",{},[150,559,560,566],{},[24,561,562],{},[137,563,565],{"href":564},"\u002Fblog\u002Fhow-to-get-a-copy-of-every-meeting-recap-in-your-crm-by-email","如何通过电子邮件将每份会议纪要的副本导入您的 CRM"," —— 无需集成路线的详细说明：字段、确认、通讯录。",[150,568,569,575],{},[24,570,571],{},[137,572,574],{"href":573},"\u002Fdemo","尝试实时演示"," —— 在浏览器中体验真实的 InterMIND 会议，无需注册。",[150,577,578,583],{},[24,579,580],{},[137,581,582],{"href":342},"API 和 Zapier"," —— 完整的有效载荷、所有端点、限制说明。",[150,585,586,592],{},[24,587,588],{},[137,589,591],{"href":590},"\u002Fblog\u002Fmeeting-recap","会议纪要：通话后您会得到什么"," —— 纪要的落地位置及接收者。",[20,594,595],{},[596,597,598,599,604],"em",{},"来源：",[137,600,603],{"href":481,"rel":601},[602],"nofollow","InterMIND API 契约, OpenAPI 3.1","。 已于 2026 年 9 月核对。",[606,607,608],"style",{},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":215,"searchDepth":228,"depth":234,"links":610},[611,612,613,614,616,617,618,619],{"id":34,"depth":228,"text":34},{"id":127,"depth":228,"text":128},{"id":144,"depth":228,"text":145},{"id":202,"depth":228,"text":615},"Webhook：recap.ready",{"id":376,"depth":228,"text":377},{"id":489,"depth":228,"text":489},{"id":502,"depth":228,"text":502},{"id":554,"depth":228,"text":554},"2026-09-10",false,"InterMIND 生成的每份会议总结均可直接送达您的工作工具，无需任何人手动复制。三种接入方式：使用 Zapier 的 Meeting Recap Ready 触发器和 Create Meeting Link 操作；使用 HMAC 签名的 recap.ready webhook；或使用 API 配合个人密钥、三个端点以及面向 Make、n8n、Pipedream 和 AI 代理的 OpenAPI 契约。涵盖有效载荷包含的内容、交付规则、限制——以及一种完全无需集成的方式：将入站电子邮件地址作为会议总结副本的收件人。","md","editorial",null,{"role":627,"spend":628},"sales-lead","incumbent-subscription","\u002Fblog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api.svg",{},"\u002Fblog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api",{"title":6,"description":622},"blog\u002Fhow-to-send-meeting-recaps-to-your-crm-with-zapier-or-the-api","cpEvH6nt3xK48qEqYjTSZEQaNOZE5fc9UTLzWeDGBJQ",[636,641],{"title":637,"path":638,"stem":639,"description":640,"children":-1},"如何查看谁在使用您的翻译分钟数和存储空间——并在达到上限前收到邮件 (2026)","\u002Fblog\u002Fhow-to-see-who-uses-your-translation-minutes-and-storage","blog\u002Fhow-to-see-who-uses-your-translation-minutes-and-storage","每项 InterMIND 额度均按会议主持人进行计量：您所创建会议中的语音翻译分钟数、参会者的聊天翻译字数、已翻译文档以及团队共享存储空间。账单页面会显示每项计量在 30 天滚动周期内的使用情况，当您接近存储上限或首次达到翻译分钟上限时，您将收到一封邮件。各项计量的统计内容、达到上限后的情况——会议继续进行，翻译暂停——以及 30 天周期如何自动恢复。",{"title":642,"path":643,"stem":644,"description":645,"children":-1},"如何从 iPhone、Android 或 Mac 上的任意应用将文件、照片或链接分享到您的团队聊天中 (2026)","\u002Fblog\u002Fhow-to-share-a-file-into-your-team-chat-from-any-app","blog\u002Fhow-to-share-a-file-into-your-team-chat-from-any-app","InterMIND 位于您手机的分享面板和 Mac 的分享菜单中。从任意应用中选取内容——一张照片、一个 PDF、一个链接或一段文本——并选择其去向：您自己的收件箱或某个频道。每个最大 25 MB 的文件会作为消息送达，文档会自动生成摘要，而频道的每位成员都能以自己的语言阅读文本。各平台提供的功能、收件箱的来源、桌面端和浏览器分别执行的操作，以及计入存储空间的内容。"]