{ "Webhooks": "Webhook", "Logs": "日志", "Queue": "队列", "API Tokens": "API 令牌", "Credentials Vault": "凭据保险库", "External Cron": "外部 Cron", "Activity": "活动", "Settings": "设置", "Pro": "Pro", "Switch to light mode": "切换到浅色模式", "Switch to dark mode": "切换到深色模式", "Love the plugin?": "喜欢这个插件吗？", "Leave a review on WordPress.org": "在 WordPress.org 上发表评价", "Trigger webhooks on WordPress events": "在 WordPress 事件上触发 Webhook", "Add Webhook": "添加 Webhook", "Loading webhooks…": "正在加载 Webhook…", "No webhooks configured yet": "尚未配置任何 Webhook", "Create your first webhook": "创建你的第一个 Webhook", "Unchained": "未链接", "Delete": "删除", "Cancel": "取消", "Save": "保存", "Save changes": "保存更改", "Saving…": "正在保存…", "Delete chain": "删除链", "Delete chain “%s”?": "删除链“%s”？", "Delete “%s”?": "删除“%s”？", "This will permanently delete the webhook and all associated data. This action cannot be undone.": "这将永久删除该 Webhook 及所有相关数据。此操作无法撤销。", "The chain and all its links will be removed. Member webhooks stay, but lose their chain-link triggers.": "该链及其所有连接将被移除。成员 Webhook 会保留，但会失去其链接触发器。", "Downstream webhooks that lose their only trigger will be marked as orphans (no trigger assigned).": "失去唯一触发器的下游 Webhook 将被标记为孤立（未分配触发器）。", "Rename chain": "重命名链", "Chain name": "链名称", "My chain": "我的链", "no remaining triggers": "没有剩余触发器", "They will move to the Unchained section with “No trigger assigned”.": "它们将移至“未链接”部分，并显示“未分配触发器”。", "Enable Synchronous Execution?": "启用同步执行？", "This webhook will fire inline during the WordPress request that triggers it, bypassing the queue. Slow or unreachable endpoints can %1$sdelay page loads, form submissions, and other frontend interactions.%2$s": "该 Webhook 将在触发它的 WordPress 请求中内联触发，绕过队列。缓慢或无法访问的端点可能会%1$s延迟页面加载、表单提交及其他前端交互。%2$s", "The %1$srecommended approach is asynchronous delivery%2$s via the built-in system cron or an external cron job.": "%1$s推荐的方式是异步投递%2$s，通过内置系统 cron 或外部 cron 任务。", "Don't show this again": "不再显示", "Enable Anyway": "仍然启用", "Add a credential to securely reuse it across webhooks.": "添加凭据，以便在各个 Webhook 中安全地重复使用。", "Edit Webhook": "编辑 Webhook", "Create Webhook": "创建 Webhook", "Back to webhooks": "返回 Webhook 列表", "Loading…": "正在加载…", "Test": "测试", "Logs: %s": "日志：%s", "Webhook #%s": "Webhook #%s", "Total (7 days)": "总计（7 天）", "Success": "成功", "Errors": "错误", "Retries": "重试", "Event Replayed": "事件已重放", "A new delivery attempt has been queued. The result will appear in this log's attempt history on the next cron run.": "新的投递尝试已加入队列。结果将在下次 cron 运行时出现在该日志的尝试历史中。", "Execute Now": "立即执行", "Go to Queue": "前往队列", "Close": "关闭", "View webhook delivery logs": "查看 Webhook 投递日志", "All statuses": "所有状态", "Error": "错误", "Retry": "重试", "Pending": "待处理", "Skipped": "已跳过", "Permanently Failed": "永久失败", "All chains": "所有链", "Filter by X-Webhook-ID…": "按 X-Webhook-ID 筛选…", "Filter by event UUID…": "按事件 UUID 筛选…", "Filter by target URL…": "按目标 URL 筛选…", "From date & time": "起始日期和时间", "To date & time": "结束日期和时间", "%d selected": "已选择 %d 项", "Processing…": "正在处理…", "Clear selection": "清除选择", "Retry / Replay %d selected": "重试 / 重放所选的 %d 项", "Replay %d selected": "重放所选的 %d 项", "Retry %d selected": "重试所选的 %d 项", "Database-backed webhook job queue": "基于数据库的 Webhook 任务队列", "Process Now": "立即处理", "Refresh": "刷新", "Total": "总计", "Processing": "处理中", "Due Now": "现在到期", "Perm. Failed": "永久失败", "Loading queue…": "正在加载队列…", "No queued jobs": "没有排队的任务", "When webhooks are triggered, jobs will appear here for processing.": "当 Webhook 被触发时，任务将显示在此处以供处理。", "Unknown Webhook": "未知 Webhook", "Attempt %1$d/%2$d": "第 %1$d/%2$d 次尝试", "Due": "到期", "Trigger:": "触发器：", "Chain link #%1$s — %2$s": "链接 #%1$s — %2$s", "Chain link #%s (deleted)": "链接 #%s（已删除）", "Copy trigger name": "复制触发器名称", "X-Webhook-Id:": "X-Webhook-Id：", "Copy X-Webhook-Id": "复制 X-Webhook-Id", "Event UUID:": "事件 UUID：", "Copy Event UUID": "复制事件 UUID", "Copy scheduled time": "复制计划时间", "URL:": "URL：", "Copy URL": "复制 URL", "Locked by: %s": "锁定者：%s", "Execute now": "立即执行", "Execute": "执行", "Reset and retry": "重置并重试", "Remove from queue": "从队列中移除", "Showing %1$d to %2$d of %3$d": "显示第 %1$d 至 %2$d 项，共 %3$d 项", "Jobs are processed every minute by WP-Cron. Failed jobs are automatically retried with exponential backoff. Use “Process Now” to manually trigger batch processing.": "任务由 WP-Cron 每分钟处理一次。失败的任务会以指数退避自动重试。使用“立即处理”可手动触发批量处理。", "Upgrade to Pro": "升级到 Pro", "Automation Chains": "自动化链", "Reliable webhooks with queue & retries": "可靠的 Webhook，带队列和重试", "Delivery logs & replay": "投递日志和重放", "Test webhook delivery on demand": "按需测试 Webhook 投递", "Payload mapping": "数据映射", "Full REST API with API token authentication": "完整的 REST API，支持 API 令牌身份验证", "Activity Log": "活动日志", "External Cron (bypass WP-Cron)": "外部 Cron（绕过 WP-Cron）", "Priority support": "优先支持", "Get Pro": "获取 Pro", "Pro Plugin Installed": "已安装 Pro 插件", "The Pro plugin is installed but not activated in WordPress.": "Pro 插件已安装但未在 WordPress 中启用。", "Activate %1$sWebhook Actions Pro%2$s to continue.": "启用 %1$sWebhook Actions Pro%2$s 以继续。", "Activating…": "正在启用…", "Activate Plugin": "启用插件", "Activate License": "激活许可证", "Enter your license key to unlock Pro features on this site.": "输入你的许可证密钥以在本站点解锁 Pro 功能。", "License Key": "许可证密钥", "Don't have a license yet?": "还没有许可证？", "💡 Local installs (%1$slocalhost%2$s, %1$s*.local%2$s, %1$s*.test%2$s) don't count toward your site limit.": "💡 本地安装（%1$slocalhost%2$s、%1$s*.local%2$s、%1$s*.test%2$s）不计入你的站点限额。", "Pro License": "Pro 许可证", "Your license is active on this site.": "你的许可证已在本站点激活。", "Active": "已激活", "Sites used": "已用站点", "(local, not counted)": "（本地，不计入）", "Sites allowed": "允许的站点", "Renews / expires": "续订 / 到期", "Deactivating…": "正在停用…", "Deactivate License": "停用许可证", "Need help?": "需要帮助？", "Community support forum": "社区支持论坛", "%1$sPriority support%2$s — Pro subscribers get a direct response via email.": "%1$s优先支持%2$s — Pro 订阅者可通过电子邮件获得直接回复。", "Deactivate license?": "停用许可证？", "This will remove the license from this site and free up a slot. You can reactivate at any time.": "这将从本站点移除许可证并释放一个名额。你可以随时重新激活。", "Deactivate": "停用", "Starter": "入门版", "Business": "商业版", "Agency": "代理版", "Tokens allow external systems to access the REST API without a browser session. Token management is always admin-only regardless of scope.": "令牌允许外部系统无需浏览器会话即可访问 REST API。无论作用域如何，令牌管理始终仅限管理员。", "New token": "新建令牌", "No API tokens": "没有 API 令牌", "Create a token to enable programmatic API access.": "创建令牌以启用程序化 API 访问。", "Create first token": "创建第一个令牌", "Name": "名称", "Scope": "作用域", "Hint": "提示", "Created": "创建时间", "Expires": "到期时间", "Last used": "上次使用", "Actions": "操作", "%s…": "%s…", "Expired": "已过期", "Rotate token": "轮换令牌", "Change expiry": "更改到期时间", "Delete token": "删除令牌", "Scope reference": "作用域参考", "GET webhooks, logs, queue, health, triggers, schemas": "GET Webhook、日志、队列、健康状况、触发器、架构", "Read + toggle webhooks, retry/replay logs, execute/retry queue jobs": "读取 + 切换 Webhook、重试/重放日志、执行/重试队列任务", "Operational + create/update/delete webhooks, schemas, and queue jobs": "操作 + 创建/更新/删除 Webhook、架构和队列任务", "Full write power for AI assistants — but can never reveal auth headers or vault secrets": "为 AI 助手提供完整写入权限 — 但绝不会泄露认证标头或保险库密钥", "Delete token: %s": "删除令牌：%s", "This will permanently revoke the token. Any integrations using it will stop working immediately.": "这将永久吊销该令牌。任何使用它的集成都将立即停止工作。", "Deleting…": "正在删除…", "Admin and API action history": "管理员和 API 操作历史", "Delete old": "删除旧记录", "All actions": "所有操作", "Snippets": "代码片段", "Chains": "链", "Cron": "Cron", "Schemas": "架构", "Clear filters": "清除筛选", "From date": "起始日期", "To date": "结束日期", "Timestamp": "时间戳", "Actor": "操作者", "Action": "操作", "Object": "对象", "No activity recorded yet.": "尚未记录任何活动。", "User prompt": "用户提示", "AI reasoning": "AI 推理", "IP": "IP", "Token": "令牌", "User ID": "用户 ID", "Changes": "更改", "Previous": "上一页", "Next": "下一页", "Delete Old Activity": "删除旧活动", "Remove activity entries older than the specified number of days.": "移除早于指定天数的活动记录。", "Delete entries older than": "删除早于以下天数的记录", "Token: %s": "令牌：%s", "User #%s": "用户 #%s", "System": "系统", "Stats unavailable": "统计数据不可用", "Last ping failed:": "上次 ping 失败：", "Last stats pull: %s": "上次拉取统计：%s", "Pause": "暂停", "Resume": "恢复", "External Cron History": "外部 Cron 历史", "Enable External Cron": "启用外部 Cron", "Target": "目标", "Plugin queue endpoint": "插件队列端点", "%1$s/wp-json/fswa/v1/cron/process?token=…%2$s — processes only the webhook queue. Min interval: 20s.": "%1$s/wp-json/fswa/v1/cron/process?token=…%2$s — 仅处理 Webhook 队列。最小间隔：20 秒。", "WP-Cron": "WP-Cron", "%1$s/wp-cron.php?doing_wp_cron%2$s — runs all WordPress scheduled tasks. Min interval: 60s. %1$sDISABLE_WP_CRON%2$s is added to %1$swp-config.php%2$s automatically.": "%1$s/wp-cron.php?doing_wp_cron%2$s — 运行所有 WordPress 计划任务。最小间隔：60 秒。%1$sDISABLE_WP_CRON%2$s 会自动添加到 %1$swp-config.php%2$s。", "%1$sDISABLE_WP_CRON%2$s is active — WP-Cron auto-spawn is disabled.": "%1$sDISABLE_WP_CRON%2$s 已生效 — WP-Cron 自动触发已禁用。", "%1$sDISABLE_WP_CRON%2$s will be written to %1$swp-config.php%2$s on save.": "保存时 %1$sDISABLE_WP_CRON%2$s 将被写入 %1$swp-config.php%2$s。", "Interval": "间隔", "You might want to whitelist the External Cron IP for your WAF or server security: %1$s72.62.157.193%2$s": "你可能需要在 WAF 或服务器安全中将外部 Cron IP 加入白名单：%1$s72.62.157.193%2$s", "Queue batch size": "队列批量大小", "Jobs processed per cron run.": "每次 cron 运行处理的任务数。", "Unknown error": "未知错误", "Not configured": "未配置", "Paused": "已暂停", "%ds": "%d 秒", "%dm": "%d 分", "%dh": "%d 时", "%1$dm %2$ds": "%1$d 分 %2$d 秒", "%1$dh %2$dm": "%1$d 时 %2$d 分", "Store reusable authentication secrets once, then reference them from your webhooks. Secrets are encrypted at rest and are never shown again after saving — not even to you.": "一次性存储可重用的认证密钥，然后在你的 Webhook 中引用它们。密钥静态加密，保存后绝不会再次显示 — 即使对你也是如此。", "New credential": "新建凭据", "No saved credentials": "没有已保存的凭据", "Add first credential": "添加第一个凭据", "Type": "类型", "Header": "标头", "Edit credential": "编辑凭据", "Delete credential": "删除凭据", "Bearer token (PAT)": "Bearer 令牌（PAT）", "Sent as Authorization: Bearer ": "以 Authorization: Bearer 形式发送", "Basic auth (user + password)": "Basic 认证（用户名 + 密码）", "Authorization: Basic — incl. WP Application Passwords": "Authorization: Basic — 包含 WP 应用程序密码", "API key (custom header)": "API 密钥（自定义标头）", "A named header such as X-API-Key": "命名标头，例如 X-API-Key", "Custom Authorization value": "自定义 Authorization 值", "Raw value for any header — escape hatch": "任意标头的原始值 — 应急方案", "Finish moving the key into wp-config.php": "完成将密钥移入 wp-config.php", "%1$sFSWA_SECRET_KEY%2$s is defined and your credentials still work, but a copy of the old key remains in the database — so you don't yet get the full benefit. Re-encrypt now to seal every secret with the wp-config key and delete the database key.": "%1$sFSWA_SECRET_KEY%2$s 已定义且你的凭据仍可用，但数据库中仍保留旧密钥的副本 — 因此你尚未获得完整的保护。立即重新加密，用 wp-config 密钥封存每个密钥并删除数据库中的密钥。", "Migrated %1$s · failed %2$s": "已迁移 %1$s · 失败 %2$s", "· database key removed": "· 数据库密钥已移除", "Re-encrypting…": "正在重新加密…", "Re-encrypt & remove database key": "重新加密并移除数据库密钥", "Maximum protection": "最高保护", "The encryption key lives in %1$swp-config.php%2$s (%1$sFSWA_SECRET_KEY%2$s) and is not stored in the database. A database-only dump cannot decrypt your secrets.": "加密密钥位于 %1$swp-config.php%2$s（%1$sFSWA_SECRET_KEY%2$s）中，不存储在数据库中。仅有数据库转储无法解密你的密钥。", "How secrets are protected": "密钥如何受保护", "Secrets are encrypted at rest (AES-256-GCM) and never returned by the API — only a masked hint is shown.": "密钥静态加密（AES-256-GCM）且 API 绝不返回 — 仅显示掩码提示。", "An %1$sagent%2$s API token can assign credentials to webhooks but can never read their values.": "%1$sagent%2$s API 令牌可以将凭据分配给 Webhook，但绝不能读取它们的值。", "Optional: harden with %1$sFSWA_SECRET_KEY%2$s": "可选：使用 %1$sFSWA_SECRET_KEY%2$s 加固", "By default the encryption key is generated and stored in the database. For stronger protection — so a database-only dump can't decrypt secrets — move the key into %1$swp-config.php%2$s:": "默认情况下，加密密钥会生成并存储在数据库中。为获得更强的保护 — 使仅有数据库转储无法解密密钥 — 请将密钥移入 %1$swp-config.php%2$s：", "%1$sFormat:%2$s any long, random, secret string (64+ characters recommended). Generate one from the %3$sWordPress salt generator%4$s or with %5$swp_generate_password(64, true, true)%6$s.": "%1$s格式：%2$s 任意长的随机机密字符串（推荐 64 个以上字符）。可使用 %3$sWordPress 盐值生成器%4$s 或 %5$swp_generate_password(64, true, true)%6$s 生成。", "%1$sSafe to add anytime:%2$s existing credentials keep working immediately. After adding it, return here and click the %3$sRe-encrypt%4$s button that appears to finish the move and remove the database key.": "%1$s随时可安全添加：%2$s 现有凭据会立即继续工作。添加后，返回此处并点击出现的 %3$s重新加密%4$s 按钮以完成迁移并移除数据库密钥。", "%1$sKeep it stable & backed up:%2$s don't change or lose this value once credentials are sealed with it, or they become unrecoverable.": "%1$s保持稳定并备份：%2$s 一旦凭据用此值封存，请勿更改或丢失它，否则将无法恢复。", "Update this credential. Leave secret fields blank to keep the existing value.": "更新此凭据。将密钥字段留空可保留现有值。", "Secrets are encrypted on save and never shown again.": "密钥在保存时加密，且绝不会再次显示。", "e.g. HubSpot PAT, Stripe key": "例如 HubSpot PAT、Stripe 密钥", "Header name": "标头名称", "Username": "用户名", "WordPress username or API user": "WordPress 用户名或 API 用户", "Password": "密码", "Leave blank to keep current": "留空以保留当前值", "Password or application password": "密码或应用程序密码", "Hide password": "隐藏密码", "Show password": "显示密码", "Hide": "隐藏", "Show": "显示", "Secret value": "密钥值", "Paste the token / key": "粘贴令牌 / 密钥", "Hide secret": "隐藏密钥", "Show secret": "显示密钥", "Create credential": "创建凭据", "Delete credential: %s": "删除凭据：%s", "This permanently removes the stored secret.": "这将永久移除已存储的密钥。", "Force delete & detach": "强制删除并分离", "Name is required.": "名称为必填项。", "Failed to rename chain.": "重命名链失败。", "Failed to fetch chains": "获取链失败", "Failed to fetch health stats": "获取健康统计失败", "Failed to fetch schemas": "获取架构失败", "Failed to fetch snippets": "获取代码片段失败", "Failed to fetch trigger snippet": "获取触发器代码片段失败", "Failed to save trigger snippet": "保存触发器代码片段失败", "Failed to fetch user triggers": "获取用户触发器失败", "Every Minute": "每分钟", "Failed to encode payload as JSON": "将数据编码为 JSON 失败", "Webhook not found.": "未找到 Webhook。", "You don't have permissions to see it.": "你没有查看它的权限。", "Webhook name is required.": "Webhook 名称为必填项。", "Invalid endpoint URL.": "无效的端点 URL。", "Failed to create webhook.": "创建 Webhook 失败。", "Failed to update webhook.": "更新 Webhook 失败。", "Failed to delete webhook.": "删除 Webhook 失败。", "Failed to toggle webhook status.": "切换 Webhook 状态失败。", "Webhook has no triggers configured.": "该 Webhook 未配置触发器。", "Chain not found.": "未找到链。", "Chain name is required.": "链名称为必填项。", "A chain with that name already exists.": "已存在同名的链。", "Failed to create chain.": "创建链失败。", "Both source_webhook_id and target_webhook_id are required.": "source_webhook_id 和 target_webhook_id 均为必填项。", "Source webhook does not exist.": "源 Webhook 不存在。", "Target webhook does not exist.": "目标 Webhook 不存在。", "A webhook cannot trigger itself.": "Webhook 不能触发自身。", "That link would create a cycle in the chain graph.": "该连接会在链图中形成循环。", "Failed to create chain link (it may already exist).": "创建链接失败（它可能已存在）。", "Chain link not found.": "未找到链接。", "Token name is required.": "令牌名称为必填项。", "Invalid scope. Must be read, operational, full, or agent.": "无效的作用域。必须是 read、operational、full 或 agent。", "Failed to create API token.": "创建 API 令牌失败。", "API token not found.": "未找到 API 令牌。", "Failed to rotate API token.": "轮换 API 令牌失败。", "Failed to delete API token.": "删除 API 令牌失败。", "Credential name is required.": "凭据名称为必填项。", "A credential with this name already exists.": "已存在同名的凭据。", "Invalid credential type.": "无效的凭据类型。", "A secret value is required.": "密钥值为必填项。", "Basic auth requires a username and password.": "Basic 认证需要用户名和密码。", "Authorization header value.": "Authorization 标头值。", "Failed to create credential.": "创建凭据失败。", "Credential not found.": "未找到凭据。", "No data to update.": "没有要更新的数据。", "Failed to delete credential.": "删除凭据失败。", "Insufficient token scope. This endpoint requires \"%s\" scope or higher.": "令牌作用域不足。此端点需要“%s”作用域或更高。", "Invalid cron token.": "无效的 cron 令牌。", "Cron secret not configured.": "未配置 cron 密钥。", "Log not found.": "未找到日志。", "Failed to delete log.": "删除日志失败。", "Only failed log entries can be retried.": "只有失败的日志条目才能重试。", "Only successful or skipped log entries can be replayed.": "只有成功或已跳过的日志条目才能重放。", "No queue job found for this log entry.": "未找到该日志条目对应的队列任务。", "Queue job not found.": "未找到队列任务。", "Cannot delete a job that is currently being processed.": "无法删除正在处理中的任务。", "Only pending or permanently failed jobs can be retried.": "只有待处理或永久失败的任务才能重试。", "Could not lock job for processing.": "无法锁定任务以进行处理。", "Failed to retry queue job.": "重试队列任务失败。", "Failed to delete queue job.": "删除队列任务失败。", "Job has already been completed.": "任务已完成。", "Job is currently being processed.": "任务正在处理中。", "Job has invalid payload data.": "任务的数据数据无效。", "Job executed successfully.": "任务执行成功。", "Job failed and has been rescheduled for retry.": "任务失败，已重新安排重试。", "Job failed and has exceeded maximum retry attempts.": "任务失败，且已超过最大重试次数。", "Job failed with a non-retryable error.": "任务因不可重试的错误而失败。", "Job deleted successfully.": "任务删除成功。", "Job has been queued for retry.": "任务已加入队列以重试。", "Failed to update schema.": "更新架构失败。", "Failed to delete schema.": "删除架构失败。", "Failed to reset capture.": "重置捕获失败。", "Conditions are not met with current settings — event would be skipped.": "当前设置不满足条件 — 事件将被跳过。", "No archive files found or failed to create ZIP.": "未找到归档文件或创建 ZIP 失败。", "All logs have been cleared.": "所有日志已清除。", "Activity log entry not found.": "未找到活动日志条目。", "Parameter older_than_days is required.": "参数 older_than_days 为必填项。", "Failed to retry job.": "重试任务失败。", "Pro plugin not found.": "未找到 Pro 插件。", "Processed %1$d jobs: %2$d succeeded, %3$d failed, %4$d rescheduled.": "已处理 %1$d 个任务：%2$d 个成功，%3$d 个失败，%4$d 个已重新安排。", "%1$s %2$d min": "%1$s %2$d 分", "%1$s %2$ds": "%1$s %2$d 秒", "%1$sAvailable variables:%2$s %3$s$payload%4$s (mapped array), %3$s$args%4$s (%5$s$payload['args']%6$s)": "%1$s可用变量：%2$s %3$s$payload%4$s（映射数组）、%3$s$args%4$s（%5$s$payload['args']%6$s）", "%1$sAvailable variables:%2$s %3$s$payload%4$s (sent), %3$s$originalPayload%4$s (pre-mapping), %3$s$responseCode%4$s, %3$s$responseBody%4$s": "%1$s可用变量：%2$s %3$s$payload%4$s（已发送）、%3$s$originalPayload%4$s（映射前）、%3$s$responseCode%4$s、%3$s$responseBody%4$s", "%1$sShorthand:%2$s works for any variable, e.g. %3$s{{ $args.0.field }}%4$s → %3$s$args[0]['field']%4$s, %3$s{{ $payload.key }}%4$s → %3$s$payload['key']%4$s": "%1$s简写：%2$s 适用于任意变量，例如 %3$s{{ $args.0.field }}%4$s → %3$s$args[0]['field']%4$s、%3$s{{ $payload.key }}%4$s → %3$s$payload['key']%4$s", "%1$sShorthand:%2$s works for any variable, e.g. %3$s{{ $originalPayload.args.0.id }}%4$s → %3$s$originalPayload['args'][0]['id']%4$s": "%1$s简写：%2$s 适用于任意变量，例如 %3$s{{ $originalPayload.args.0.id }}%4$s → %3$s$originalPayload['args'][0]['id']%4$s", "%d available": "%d 个可用", "%s Retry": "第 %s 次重试", "%s auth": "%s 认证", "(last attempt)": "（上次尝试）", "(no output)": "（无输出）", "(param name)": "（参数名称）", "(value)": "（值）", "A new token will be generated. The current token will be %1$simmediately invalidated%2$s and all existing integrations using it will stop working.": "将生成一个新令牌。当前令牌将%1$s立即失效%2$s，所有使用它的现有集成都将停止工作。", "ALL (AND)": "全部（AND）", "AND": "AND", "ANY (OR)": "任意（OR）", "Active/Total": "活动/总计", "Add": "添加", "Add Mapping": "添加映射", "Add condition": "添加条件", "Add group": "添加组", "Add mapping for this field": "为该字段添加映射", "Add row": "添加行", "Add rule": "添加规则", "Additional URL Query Parameters": "额外的 URL 查询参数", "After saving, the value is encrypted at rest and never shown again.": "保存后，该值将被静态加密，且绝不会再次显示。", "Agent (AI)": "Agent（AI）", "Also update expiry": "同时更新到期时间", "Alternatively, %1$sAuthorization: Bearer <token>%2$s works on most servers (requires %1$sCGIPassAuth On%2$s on Apache).": "或者，%1$sAuthorization: Bearer <token>%2$s 在大多数服务器上有效（在 Apache 上需要 %1$sCGIPassAuth On%2$s）。", "Any unsaved changes on this form will be lost.": "此表单上任何未保存的更改都将丢失。", "Appended to the URL alongside the JSON body. Values support dot-notation paths or static strings.": "与 JSON 主体一起附加到 URL。值支持点号路径或静态字符串。", "Attempt #%d": "第 #%d 次尝试", "Attempt History": "尝试历史", "Attempted At": "尝试时间", "Authorization (optional)": "授权（可选）", "Automatically enrich payload with user profile information": "自动用用户资料信息丰富数据", "Available Fields": "可用字段", "Avg attempts": "平均尝试次数", "Avg ping": "平均 ping", "Avg response": "平均响应", "Backoff Strategy": "退避策略", "Base Delay (s)": "基础延迟（秒）", "Base seconds used to calculate the retry delay. Acts as a multiplier for exponential, interval for linear, and constant wait for fixed.": "用于计算重试延迟的基础秒数。在指数策略中作为乘数，在线性策略中作为间隔，在固定策略中作为恒定等待。", "Browse Library": "浏览库", "Cannot evaluate": "无法评估", "Cap on the wait between retries. Prevents exponential backoff from growing indefinitely — any delay above this value is clamped to it.": "重试之间等待的上限。防止指数退避无限增长 — 超过此值的任何延迟都会被限制到该值。", "Capture an example payload to enable live preview.": "捕获示例数据以启用实时预览。", "Captured": "已捕获", "Captured + Mapping": "已捕获 + 映射", "Captured payload with field mapping applied": "应用了字段映射的已捕获数据", "Cast": "转换", "Chain": "链", "Chain mode links this webhook to upstream webhooks, which requires a saved webhook record. %1$sSave the webhook first%2$s (with or without WP-hook triggers — they'll be cleared when you pick upstream webhooks), then choose your chain sources on the next screen.": "链模式将该 Webhook 与上游 Webhook 关联，这需要已保存的 Webhook 记录。%1$s请先保存 Webhook%2$s（是否带 WP-hook 触发器均可 — 选择上游 Webhook 时它们会被清除），然后在下一屏选择你的链来源。", "Change expiry: %s": "更改到期时间：%s", "Clear assignment": "清除分配", "Click to select or browse • + to select an array/object": "点击以选择或浏览 • + 选择数组/对象", "Client Error": "客户端错误", "Code Glue": "Code Glue", "Comments": "评论", "Conditions": "条件", "Conditions are evaluated against the payload — use the 'Evaluate conditions against' toggle above to choose original or transformed.": "条件根据数据进行评估 — 使用上方的“评估条件依据”开关选择原始或转换后。", "Copy code": "复制代码", "Copy endpoint URL": "复制端点 URL", "Copy headers": "复制标头", "Copy original payload": "复制原始数据", "Copy payload": "复制数据", "Copy response body": "复制响应主体", "Copy to clipboard": "复制到剪贴板", "Create API Token": "创建 API 令牌", "Create token": "创建令牌", "Creating…": "正在创建…", "Credential name": "凭据名称", "Custom": "自定义", "Custom Payload": "自定义数据", "Custom Request Headers": "自定义请求标头", "Date": "日期", "Delay preview": "延迟预览", "Delete log?": "删除日志？", "Disabled": "已禁用", "Disabled webhooks still capture payload examples for mapping and conditions configuration.": "已禁用的 Webhook 仍会捕获数据示例，以供映射和条件配置使用。", "Discard": "放弃", "Does not match example payload": "与示例数据不匹配", "Done": "完成", "Dot-path (e.g. event.id) or static text": "点号路径（例如 event.id）或静态文本", "Duration": "耗时", "Edit": "编辑", "Enable conditional dispatch": "启用条件投递", "Enabled Webhook": "已启用 Webhook", "Endpoint URL": "端点 URL", "Endpoint URL is required": "端点 URL 为必填项", "Enter an Authorization header value first.": "请先输入 Authorization 标头值。", "Enter custom hook name...": "输入自定义钩子名称…", "Error Message": "错误信息", "Evaluate conditions against": "评估条件依据", "Event UUID": "事件 UUID", "Example payload captured": "已捕获示例数据", "Example payload would %1$s%2$s%3$s": "示例数据将%1$s%2$s%3$s", "Exclude entire %s": "排除整个 %s", "Exclude field": "排除字段", "Excluded Fields": "已排除字段", "Executes synchronously (blocking)": "同步执行（阻塞）", "Expires at": "到期时间", "Exponential": "指数", "Fail": "失败", "Failed": "失败", "Field Mappings": "字段映射", "Fixed": "固定", "Full": "完整", "Full write power, but can never reveal auth headers or vault secrets": "完整写入权限，但绝不会泄露认证标头或保险库密钥", "Generate a new API token for programmatic access.": "生成新的 API 令牌以进行程序化访问。", "Give this credential a name.": "为此凭据命名。", "Go to Pro": "前往 Pro", "Group does not match example payload": "组与示例数据不匹配", "Group matches example payload": "组与示例数据匹配", "HTTP %s": "HTTP %s", "HTTP Code": "HTTP 代码", "HTTP Method": "HTTP 方法", "Head to the Pro tab?": "前往 Pro 选项卡？", "Headers": "标头", "How to calculate the wait between retries. Overrides the global setting.": "如何计算重试之间的等待时间。覆盖全局设置。", "I've saved it elsewhere": "我已将其保存到别处", "IF": "如果", "Include User Data": "包含用户数据", "Include field": "包含字段", "Include unmapped fields": "包含未映射的字段", "Invalid JSON": "无效的 JSON", "Invalid URL format": "无效的 URL 格式", "Key": "键", "Key must only contain letters, numbers, hyphens, or underscores": "键只能包含字母、数字、连字符或下划线", "Last captured payload for this trigger": "该触发器上次捕获的数据", "Last hour": "上一小时", "Last successful response (used as preview context)": "上次成功的响应（用作预览上下文）", "Linear": "线性", "Load": "加载", "Loading last log…": "正在加载上一条日志…", "Loading...": "正在加载…", "Log Details": "日志详情", "Make sure to update all systems that use this token before rotating.": "轮换前请确保更新所有使用该令牌的系统。", "Manual dot-notation for all fields": "对所有字段使用手动点号表示法", "Manual header": "手动标头", "Mapped": "已映射", "Mapping & Conditions": "映射与条件", "Mapping Applied": "已应用映射", "Match:": "匹配：", "Matches example payload": "与示例数据匹配", "Max Attempts": "最大尝试次数", "Max Delay (s)": "最大延迟（秒）", "Media": "媒体", "Method": "方法", "Move this value into the encrypted Credentials Vault": "将此值移入加密的凭据保险库", "Must %1$sreturn $payload;%2$s — the returned array replaces the payload before dispatch.": "必须 %1$sreturn $payload;%2$s — 返回的数组会在投递前替换数据。", "My Webhook": "我的 Webhook", "N/A": "不适用", "Name is required": "名称为必填项", "New chain name": "新链名称", "New chain…": "新建链…", "Next attempt scheduled for %s": "下次尝试计划于 %s", "No": "否", "No Payload Captured Yet": "尚未捕获数据", "No body sent": "未发送主体", "No captured payload — trigger the webhook once to preview the resolved URL.": "未捕获数据 — 触发一次 Webhook 以预览解析后的 URL。", "No example payload captured yet.": "尚未捕获示例数据。", "No field mappings configured. Fields will be sent as-is.": "未配置字段映射。字段将原样发送。", "No fields found": "未找到字段", "No fields found in payload": "数据中未找到字段", "No heartbeat data yet": "尚无心跳数据", "No logs found": "未找到日志", "No other webhooks exist yet — create at least one webhook to use it as a chain source.": "尚不存在其他 Webhook — 请至少创建一个 Webhook 以将其用作链来源。", "No saved credentials yet. Add one in the": "尚无已保存的凭据。请在以下位置添加", "No snippet assigned": "未分配代码片段", "No snippets found": "未找到代码片段", "No successful dispatches found for this webhook — run a test first.": "未找到该 Webhook 的成功投递 — 请先运行测试。", "No trigger assigned": "未分配触发器", "No triggers configured for this webhook.": "该 Webhook 未配置触发器。", "No triggers found": "未找到触发器", "No webhooks match “%s”.": "没有 Webhook 匹配“%s”。", "Not sent as request body for GET / DELETE. Without URL parameters configured, the full payload is appended as %1$s?payload=<json>%2$s.": "对于 GET / DELETE 不作为请求主体发送。在未配置 URL 参数的情况下，完整数据会以 %1$s?payload=<json>%2$s 形式附加。", "OK": "确定", "OR": "OR", "On a successful (2xx) response from any of these webhooks, this webhook fires with the upstream response, sent payload, and original pre-mapping payload available as %1$sargs[0]%2$s.": "当这些 Webhook 中任意一个返回成功（2xx）响应时，该 Webhook 将被触发，上游响应、已发送数据和原始映射前数据均可通过 %1$sargs[0]%2$s 获得。", "Operational": "操作", "Operational + create/update/delete webhooks, schemas, queue jobs": "操作 + 创建/更新/删除 Webhook、架构、队列任务", "Options": "选项", "Or select from available hooks...": "或从可用钩子中选择…", "Original": "原始", "Original Payload": "原始数据", "Other": "其他", "Output (stdout)": "输出（stdout）", "Override the global retry limit for this webhook. Leave empty to use the global setting.": "覆盖该 Webhook 的全局重试上限。留空则使用全局设置。", "Override the retry delay strategy for this webhook. Leave empty to use the global setting.": "覆盖该 Webhook 的重试延迟策略。留空则使用全局设置。", "PHP Code": "PHP 代码", "PHP runs after successful dispatch; %1$s$responseBody%2$s and %1$s$originalPayload%2$s available": "PHP 在成功投递后运行；可使用 %1$s$responseBody%2$s 和 %1$s$originalPayload%2$s", "Pages": "页面", "Param name": "参数名称", "Path not found in payload": "在数据中未找到路径", "Payload": "数据", "Payload Example Captured": "已捕获数据示例", "Payload Mapping": "数据映射", "Pick date & time": "选择日期和时间", "Plugins": "插件", "Post Glue": "投递后 Glue", "Post-dispatch": "投递后", "Post-dispatch Code Glue": "投递后 Code Glue", "Post-dispatch Code Glue preview ran but is not saved. Save or discard before continuing.": "投递后 Code Glue 预览已运行但未保存。请在继续前保存或放弃。", "Posts": "文章", "Pre Glue": "投递前 Glue", "Pre-dispatch": "投递前", "Pre-dispatch Code Glue": "投递前 Code Glue", "Pre-dispatch Code Glue preview is active. Save or discard it before saving Mapping & Conditions.": "投递前 Code Glue 预览处于活动状态。请在保存映射与条件前保存或放弃它。", "Preview active": "预览已激活", "Preview failed": "预览失败", "Query Parameters": "查询参数", "Queue Test": "将测试加入队列", "Queue appears stuck — there are pending deliveries older than 10 minutes. Check your cron setup.": "队列似乎卡住 — 存在超过 10 分钟的待处理投递。请检查你的 cron 设置。", "Queue processor has never run. Ensure WP-Cron is active or configure an external cron job for reliable delivery.": "队列处理器从未运行。请确保 WP-Cron 处于活动状态，或配置外部 cron 任务以实现可靠投递。", "Queuing…": "正在加入队列…", "Re-capture": "重新捕获", "Read": "读取", "Read + toggle webhooks, retry/replay logs, execute queue jobs": "读取 + 切换 Webhook、重试/重放日志、执行队列任务", "Ready to send some data?": "准备好发送一些数据了吗？", "Redirect": "重定向", "Replay": "重放", "Request": "请求", "Request Headers": "请求标头", "Request Payload": "请求数据", "Response": "响应", "Response (ms)": "响应（毫秒）", "Response Body": "响应主体", "Result Preview": "结果预览", "Return value is ignored — use for side effects: %1$supdate_post_meta()%2$s, %1$swp_mail()%2$s, %1$serror_log()%2$s, follow-up API calls, etc.": "返回值会被忽略 — 用于副作用：%1$supdate_post_meta()%2$s、%1$swp_mail()%2$s、%1$serror_log()%2$s、后续 API 调用等。", "Revive token": "恢复令牌", "Revive token: %s": "恢复令牌：%s", "Reviving…": "正在恢复…", "Rotate token: %s": "轮换令牌：%s", "Rotating…": "正在轮换…", "Run Preview": "运行预览", "Run Test Now": "立即运行测试", "Running…": "正在运行…", "Samples": "样本", "Save & Assign": "保存并分配", "Save & continue to chain setup": "保存并继续链设置", "Save & use credential": "保存并使用凭据", "Save Changes": "保存更改", "Save Glue": "保存 Glue", "Save credential to vault": "将凭据保存到保险库", "Save failed": "保存失败", "Save to vault": "保存到保险库", "Save webhook first": "请先保存 Webhook", "Saved credential": "已保存的凭据", "Search fields…": "搜索字段…", "Search snippets…": "搜索代码片段…", "Search triggers...": "搜索触发器…", "Search webhooks by name or URL…": "按名称或 URL 搜索 Webhook…", "Select a saved credential": "选择已保存的凭据", "Select an existing chain or enter a new chain name": "选择现有链或输入新链名称", "Select at least one upstream webhook to trigger this one": "至少选择一个上游 Webhook 以触发该 Webhook", "Select chain or create new": "选择链或新建", "Select field…": "选择字段…", "Select this field": "选择此字段", "Select trigger": "选择触发器", "Sending…": "正在发送…", "Sent today": "今日已发送", "Server Error": "服务器错误", "Set expiration date": "设置到期日期", "Show full": "显示完整", "Show less": "显示更少", "Skipped:": "已跳过：", "Snippet Name": "代码片段名称", "Snippet saved and assigned.": "代码片段已保存并分配。", "Source": "源", "Source path (e.g., args.0.user_id)": "源路径（例如 args.0.user_id）", "Status": "状态", "Success Rate": "成功率", "Success rate 24h": "24 小时成功率", "Switch to field selector": "切换到字段选择器", "Switch to manual input": "切换到手动输入", "Sync": "同步", "Synchronous Execution": "同步执行", "Synchronous execution": "同步执行", "Tags (comma-separated)": "标签（以逗号分隔）", "Target URL": "目标 URL", "Target path (e.g., user_id)": "目标路径（例如 user_id）", "Taxonomy": "分类法", "Test Webhook": "测试 Webhook", "Test failed.": "测试失败。", "Test queued — it will run on the next cron cycle.": "测试已加入队列 — 它将在下个 cron 周期运行。", "The URL where webhook payloads will be sent. Supports %1$s{{ field.path }}%2$s templates — resolved against the final payload, after code glue applied.": "Webhook 数据将发送到的 URL。支持 %1$s{{ field.path }}%2$s 模板 — 在应用 code glue 之后，根据最终数据进行解析。", "The secret is resolved securely at delivery time and never exposed. Manage credentials in the": "密钥在投递时安全解析，绝不暴露。请在以下位置管理凭据", "These are the primary way to send data for %1$s requests. If none are set, the mapped payload is sent as %2$s?payload=<json>%3$s.": "这是 %1$s 请求发送数据的主要方式。如果未设置，则映射后的数据会以 %2$s?payload=<json>%3$s 形式发送。", "This action cannot be undone.": "此操作无法撤销。", "This moves the Authorization value into the encrypted vault and references it by name. The webhook keeps working unchanged.": "这会将 Authorization 值移入加密保险库并按名称引用。该 Webhook 将照常工作，不受影响。", "This token is %1$sexpired%2$s. Rotating will issue a new secret — but you must also extend the expiry, otherwise the token will remain invalid immediately after rotation.": "该令牌%1$s已过期%2$s。轮换将颁发新密钥 — 但你还必须延长到期时间，否则令牌在轮换后将立即保持无效。", "This token will only be shown once. Copy it now — you won't be able to see it again.": "该令牌只会显示一次。请立即复制 — 你将无法再次看到它。", "This webhook executes synchronously. Slow or unreachable endpoints will delay page loads and frontend interactions.": "该 Webhook 同步执行。缓慢或无法访问的端点将延迟页面加载和前端交互。", "This webhook will run on every trigger.": "该 Webhook 将在每次触发时运行。", "Time": "时间", "Today": "今天", "Token created": "令牌已创建", "Token name": "令牌名称", "Token will never expire.": "令牌将永不过期。", "Total (7d)": "总计（7 天）", "Total delivery attempts for this webhook, including the first try. Overrides the global setting. Once reached the job is permanently failed.": "该 Webhook 的总投递尝试次数，包括首次尝试。覆盖全局设置。一旦达到，任务即永久失败。", "Total sent": "已发送总计", "Transformed": "转换后", "Transformed Payload (Sent)": "转换后数据（已发送）", "Trigger": "触发器", "Trigger this event to capture an example payload for mapping.": "触发该事件以捕获用于映射的示例数据。", "Trigger this webhook when the following webhooks complete": "当以下 Webhook 完成时触发该 Webhook", "Triggers": "触发器", "URL Query Parameters": "URL 查询参数", "URL must be HTTP or HTTPS": "URL 必须是 HTTP 或 HTTPS", "Unsaved changes": "未保存的更改", "Untitled": "无标题", "Update Snippet": "更新代码片段", "Update when this token expires. Removing the expiry makes it valid indefinitely.": "更新该令牌的到期时间。移除到期时间将使其无限期有效。", "Upgrade": "升级", "Use %1$sX-FSWA-Token: %2$s%3$s in your requests.": "在你的请求中使用 %1$sX-FSWA-Token: %2$s%3$s。", "Use global setting": "使用全局设置", "Use other Webhooks as triggers": "使用其他 Webhook 作为触发器", "User trigger": "用户触发器", "Users": "用户", "Value for the Authorization header (e.g., \"Bearer your_token_goes_here\" or \"Basic your_encoded_base64(username:password)\"). For better security, store secrets in the": "Authorization 标头的值（例如“Bearer your_token_goes_here”或“Basic your_encoded_base64(username:password)”）。为获得更好的安全性，请将密钥存储在", "Values support dot-notation paths into the outgoing payload (e.g. %1$sevent.id%2$s) or static strings.": "值支持指向传出数据的点号路径（例如 %1$sevent.id%2$s）或静态字符串。", "View full log": "查看完整日志", "View in Logs": "在日志中查看", "View logs": "查看日志", "View webhooks, logs, queue, health, triggers, schemas": "查看 Webhook、日志、队列、健康状况、触发器、架构", "Wait %s": "等待 %s", "Waiting for trigger to capture example payload...": "正在等待触发器以捕获示例数据…", "Webhook": "Webhook", "Webhook Actions by Flow Systems: Your webhooks have been migrated to the new database format.": "Webhook Actions by Flow Systems：你的 Webhook 已迁移到新的数据库格式。", "Webhook auth": "Webhook 认证", "When enabled, this webhook fires inline during the WordPress request that triggers it, bypassing the queue. May slow down your site if the endpoint is slow.": "启用后，该 Webhook 会在触发它的 WordPress 请求中内联触发，绕过队列。如果端点较慢，可能会拖慢你的站点。", "Will Retry": "将重试", "WordPress actions that will trigger this webhook": "将触发该 Webhook 的 WordPress 操作", "Write your own JSON payload": "编写你自己的 JSON 数据", "Yes": "是", "You have unsaved changes. The test will run against the %1$ssaved%2$s version of this webhook.": "你有未保存的更改。测试将针对该 Webhook 的%1$s已保存%2$s版本运行。", "array contains": "数组包含", "auto": "自动", "be skipped": "被跳过", "bool": "布尔", "contains": "包含", "dispatch": "投递", "does not contain": "不包含", "does not equal": "不等于", "e.g. CI pipeline, n8n integration": "例如 CI 流水线、n8n 集成", "e.g. HubSpot PAT": "例如 HubSpot PAT", "e.g. Order to HubSpot": "例如 订单同步到 HubSpot", "empty": "为空", "equals": "等于", "excluded via parent": "通过父级排除", "excludes": "排除", "greater than": "大于", "has item": "含项", "has value": "含值", "instead.": "。", "is empty": "为空", "is false": "为假", "is not empty": "不为空", "is true": "为真", "less than": "小于", "mapped": "已映射", "no": "否", "not empty": "非空", "not equals": "不等于", "number": "数字", "object contains": "对象包含", "perm. failed": "永久失败", "property name (optional)": "属性名称（可选）", "string": "字符串", "stringify": "字符串化", "then select it here.": "然后在此处选择它。", "unknown": "未知", "value": "值", "…": "…", "yes": "是", "%1$swp-config.php%2$s is not writable. Add this line manually before the “That’s all” comment: %3$sdefine( 'DISABLE_WP_CRON', true );%4$s": "%1$swp-config.php%2$s 不可写。请在“That’s all”注释之前手动添加这一行：%3$sdefine( 'DISABLE_WP_CRON', true );%4$s", "A payload object is required for custom source.": "自定义源需要一个数据对象。", "Activity log entry ID.": "活动日志条目 ID。", "Array of log IDs to retry.": "要重试的日志 ID 数组。", "Authentication required. Provide a valid API token via X-FSWA-Token header, Authorization: Bearer token, or api_token query parameter.": "需要身份验证。请通过 X-FSWA-Token 标头、Authorization: Bearer token 或 api_token 查询参数提供有效的 API 令牌。", "Creation date.": "创建日期。", "Current page of results.": "结果的当前页。", "Custom payload JSON (required when payload_source is custom).": "自定义数据 JSON（当 payload_source 为 custom 时必填）。", "Delete entries older than specified days.": "删除早于指定天数的条目。", "Delete logs older than specified days.": "删除早于指定天数的日志。", "Endpoint URL is required.": "端点 URL 为必填项。", "Extra request headers as key-value pairs.": "作为键值对的额外请求标头。", "Field mapping configuration.": "字段映射配置。", "Filter by action prefix (e.g. \"webhook\").": "按操作前缀筛选（例如“webhook”）。", "Filter by event UUID (exact match).": "按事件 UUID 筛选（精确匹配）。", "Filter by exact action string.": "按精确的操作字符串筛选。", "Filter by status.": "按状态筛选。", "Filter by target URL (partial match).": "按目标 URL 筛选（部分匹配）。", "Filter by trigger name.": "按触发器名称筛选。", "Filter by webhook ID.": "按 Webhook ID 筛选。", "Filter by webhook UUID (X-Webhook-Id header value).": "按 Webhook UUID（X-Webhook-Id 标头值）筛选。", "Filter from UTC datetime (Y-m-d H:i:s).": "从 UTC 日期时间筛选（Y-m-d H:i:s）。", "Filter logs from this date.": "从该日期筛选日志。", "Filter logs until this date.": "筛选日志至该日期。", "Filter until UTC datetime (Y-m-d H:i:s).": "筛选至 UTC 日期时间（Y-m-d H:i:s）。", "HTTP method used for delivery.": "用于投递的 HTTP 方法。", "How to run the test: now (synchronous) or queue (async).": "如何运行测试：now（同步）或 queue（异步）。", "ID of a vault credential to use for authorization. Takes precedence over auth_header.": "用于授权的保险库凭据 ID。优先于 auth_header。", "Last update date.": "上次更新日期。", "List of trigger actions.": "触发器操作列表。", "Name of the webhook.": "Webhook 的名称。", "No captured payload found for this trigger. Fire the trigger at least once first.": "未找到该触发器的已捕获数据。请先至少触发一次。", "Number of days to look back.": "回溯的天数。", "Number of results per page.": "每页结果数。", "Only return enabled webhooks.": "仅返回已启用的 Webhook。", "Query parameters appended to the URL.": "附加到 URL 的查询参数。", "This usually means the encryption key changed (e.g. %1$sFSWA_SECRET_KEY%2$s or WordPress salts). Edit each affected credential and re-enter its secret to fix it.": "这通常意味着加密密钥已更改（例如 %1$sFSWA_SECRET_KEY%2$s 或 WordPress 盐值）。请编辑每个受影响的凭据并重新输入其密钥以修复。", "Trigger name to use for the test.": "用于测试的触发器名称。", "Trigger name.": "触发器名称。", "URL to send the webhook to.": "发送 Webhook 的目标 URL。", "Unique identifier for the webhook.": "Webhook 的唯一标识符。", "Webhook ID.": "Webhook ID。", "Where to source the test payload from.": "测试数据的来源。", "Whether the webhook executes synchronously (blocking, bypasses queue).": "Webhook 是否同步执行（阻塞，绕过队列）。", "Whether the webhook is enabled.": "Webhook 是否已启用。", "Whether to include user data.": "是否包含用户数据。", "%d webhook": "%d 个 Webhook", "%d link will be removed": "将移除 %d 个连接", "%d entry": "%d 个条目", "%d day": "%d 天", "Activity entries older than %d day have been deleted.": "已删除早于 %d 天的活动条目。", "%d credential cannot be decrypted with the current key.": "有 %d 个凭据无法用当前密钥解密。", "This webhook participates in a chain:": "该 Webhook 参与了一个链：", "This webhook will become an orphan:": "该 Webhook 将变为孤立：", "This credential is used by %d webhook. Detach it or delete with force.": "该凭据被 %d 个 Webhook 使用。请将其分离或强制删除。", "Deleting with force will detach it from %d webhook; that webhook will send no Authorization header until reconfigured.": "强制删除会将其从 %d 个 Webhook 分离；在重新配置之前，这些 Webhook 将不发送 Authorization 标头。", "%d hour": "%d 小时", "%d minute": "%d 分钟", "%d second": "%d 秒", "%d trigger selected": "已选择 %d 个触发器", "Part of chain:": "属于链：", "Group matches example payload: %1$s (based on %2$d rule)": "组与示例数据匹配：%1$s（基于 %2$d 条规则）", "5 (plugin default)": "5（插件默认）", "Action Scheduler": "Action Scheduler", "Action Scheduler detected — queue processing is managed automatically. You can still configure an external cron URL as a direct trigger.": "检测到 Action Scheduler — 队列处理将自动管理。你仍可配置外部 cron URL 作为直接触发器。", "Add this line to your server's crontab: %1$scrontab -e%2$s": "将此行添加到服务器的 crontab：%1$scrontab -e%2$s", "Admin Menu": "管理菜单", "Admin action history older than this will be automatically deleted.": "早于此期限的管理操作历史将被自动删除。", "All logs have been cleared": "所有日志已清除", "Archive logs before deletion": "删除前归档日志", "Are you sure you want to delete all %d log?": "确定要删除全部 %d 条日志吗？", "Base Delay (seconds)": "基础延迟（秒）", "Cap on the wait between retries. Exponential backoff grows 2ⁿ × base — without a cap delays would grow indefinitely. Any calculated delay above this value is clamped to it.": "重试之间等待时间的上限。指数退避按 2ⁿ × 基础值增长 — 若无上限，延迟将无限增长。任何超过此值的计算延迟都会被限制到此值。", "Clear All Logs": "清除所有日志", "Configure plugin behavior": "配置插件行为", "Cron URL": "Cron URL", "Cron token regenerated. Update your crontab with the new command.": "Cron 令牌已重新生成。请使用新命令更新你的 crontab。", "Crontab Command": "Crontab 命令", "Danger Zone": "危险区域", "Database Version": "数据库版本", "Delay doubles each retry: 2ⁿ × base, capped at max": "每次重试延迟翻倍：2ⁿ × 基础值，上限为最大值", "Delay grows evenly: n × base seconds": "延迟均匀增长：n × 基础秒数", "Delete All Logs": "删除所有日志", "Download Archive (ZIP)": "下载归档（ZIP）", "Exponential — base 30 s, cap 3600 s": "指数 — 基础 30 秒，上限 3600 秒", "Files": "文件", "For reliable webhook delivery, set up a system cron job to process the queue every minute. WP-Cron serves as a fallback when system cron isn't configured.": "为确保 Webhook 可靠投递，请设置系统 cron 任务每分钟处理一次队列。当未配置系统 cron 时，WP-Cron 作为后备方案。", "Keep activity log for": "活动日志保留时长", "Keep webhook logs for": "Webhook 日志保留时长", "Last Cron Run": "上次 Cron 运行", "Loading settings...": "正在加载设置…", "Log Archive": "日志归档", "Log Retention": "日志保留", "Max Delay (seconds)": "最大延迟（秒）", "Move the admin menu item under Tools instead of the top-level sidebar.": "将管理菜单项移动到「工具」下，而非顶级侧边栏。", "Newest": "最新", "No archive files yet": "尚无归档文件", "Oldest": "最早", "Oldest Log": "最早的日志", "Page reload is disabled on WordPress Playground — the menu will update on next WP menu item click.": "在 WordPress Playground 上页面重新加载已禁用 — 菜单将在下次点击 WP 菜单项时更新。", "Plugin Info": "插件信息", "Plugin Version": "插件版本", "Plugin default": "插件默认", "Queue Processor (Cron)": "队列处理器（Cron）", "Regenerate Token": "重新生成令牌", "Regenerating the token will invalidate the current cron URL. You'll need to update your crontab.": "重新生成令牌将使当前的 cron URL 失效。你需要更新 crontab。", "Retry Settings": "重试设置", "Retry settings saved": "重试设置已保存", "Same delay every retry: base seconds": "每次重试延迟相同：基础秒数", "Save Retry Settings": "保存重试设置", "Save Settings": "保存设置", "Scheduler": "调度器", "Settings saved successfully": "设置已成功保存", "Show menu under Tools": "在「工具」下显示菜单", "Size": "大小", "The base number of seconds used to calculate each retry delay. Exact role depends on the strategy: multiplier for exponential, interval for linear, constant for fixed.": "用于计算每次重试延迟的基础秒数。具体作用取决于策略：指数策略为倍数，线性策略为间隔，固定策略为常量。", "This action cannot be undone. All logs will be permanently deleted.": "此操作无法撤销。所有日志将被永久删除。", "This will permanently delete all logs from the database.": "这将从数据库中永久删除所有日志。", "Total Logs": "日志总数", "Total delivery attempts per webhook (including the first try). Leave empty for the plugin default of 5.": "每个 Webhook 的总投递尝试次数（含首次尝试）。留空则使用插件默认值 5。", "Total delivery attempts per webhook, including the first try. Once this number is reached the job is permanently failed.": "每个 Webhook 的总投递尝试次数，含首次尝试。一旦达到此次数，任务将被永久标记为失败。", "WP-Cron Fallback": "WP-Cron 后备", "Wait before each retry": "每次重试前的等待时间", "Webhook delivery logs older than this will be automatically deleted.": "早于此期限的 Webhook 投递日志将被自动删除。", "When enabled, logs are exported to JSON files before being deleted.": "启用后，日志在删除前会导出为 JSON 文件。", "+ New credential": "+ 新建凭据", "A chain with this name already exists.": "已存在同名的链。", "A condition rule is missing \"field\" — a dot-path into the trigger payload (use get_trigger_schema to see the available fields).": "条件规则缺少 \"field\"——指向触发器数据的点路径（使用 get_trigger_schema 查看可用字段）。", "A message is required.": "消息为必填项。", "A provider and model are required.": "必须提供提供商和模型。", "A url or webhook_id is required.": "必须提供 url 或 webhook_id。", "AI Builder": "AI 构建器", "API key": "API 密钥", "API key (header)": "API 密钥（标头）", "Add a chain link": "添加链环节", "Add a source→target edge to a chain. Rejected if it would create a cycle across any chain.": "向链中添加一条 源→目标 边。如果会在任何链中产生循环则被拒绝。", "Add an API key for one or more providers. The active provider is used first; if it is rate-limited or fails, the agent automatically falls back to another connected provider.": "为一个或多个提供商添加 API 密钥。优先使用当前启用的提供商；如果其被限流或失败，代理会自动切换到另一个已连接的提供商。", "Add credential & retry": "添加凭据并重试", "An API key is required to connect this provider.": "连接此提供商需要 API 密钥。", "Assign a vault credential to a webhook": "将保险库凭据分配给 Webhook", "Auto": "自动", "Auto prefers your WordPress connectors when available, otherwise your own keys.": "“自动”优先使用可用的 WordPress 连接器，否则使用您自己的密钥。", "Basic auth": "Basic 认证", "Bearer token": "Bearer 令牌", "Build": "构建", "Build complete.": "构建完成。", "Build progress": "构建进度", "Build with AI": "用 AI 构建", "Change model": "更换模型", "Choose a credential": "选择凭据", "Confirm & run": "确认并运行", "Connect": "连接", "Connect an AI provider": "连接 AI 提供商", "Continue": "继续", "Continue build": "继续构建", "Conversation not found.": "未找到对话。", "Copied": "已复制", "Copy": "复制", "Could not load models for this key — check that the key is valid.": "无法加载此密钥的模型——请检查密钥是否有效。", "Create & assign": "创建并分配", "Create a named chain that wires 2xx completions of one webhook to downstream webhooks.": "创建一个命名链，将一个 Webhook 的 2xx 完成结果接入下游 Webhook。", "Create a new webhook (always created DISABLED until the user enables it). Provide name, endpoint_url, http_method and triggers.": "创建新的 Webhook（始终以“已禁用”状态创建，直到用户启用）。请提供 name、endpoint_url、http_method 和 triggers。", "Create a webhook": "创建 Webhook", "Create a webhook chain": "创建 Webhook 链", "Credential could not be decrypted.": "无法解密凭据。", "Credential name (e.g. n8n auth)": "凭据名称（例如 n8n auth）", "Credentials source": "凭据来源", "Custom header": "自定义标头", "Delete a webhook": "删除 Webhook", "Delete build": "删除构建", "Delete this build": "删除此构建", "Delete this build?": "删除此构建？", "Describe what to build…": "描述要构建的内容…", "Each condition rule must be an object {field, operator, value}.": "每条条件规则必须是 {field, operator, value} 对象。", "Enable (go live) or disable a webhook. Enabling requires confirmation.": "启用（上线）或禁用 Webhook。启用需要确认。", "Enable / disable a webhook": "启用 / 禁用 Webhook", "Enable webhook": "启用 Webhook", "Failed to create chain link.": "创建链环节失败。", "Failed to save conditions.": "保存条件失败。", "Failed to save mapping.": "保存映射失败。", "Failed to start a conversation.": "启动对话失败。", "Failed to store the provider key.": "存储提供商密钥失败。", "Get a single webhook by id, including triggers, mapping, conditions, headers and credential assignment.": "按 id 获取单个 Webhook，包括触发器、映射、条件、标头和凭据分配。", "Get a webhook": "获取 Webhook", "Get captured payload + mapping for a trigger": "获取触发器的已捕获数据 + 映射", "Get delivery logs": "获取投递日志", "Header name (e.g. X-API-Key)": "标头名称（例如 X-API-Key）", "List all configured webhooks with their triggers and status.": "列出所有已配置的 Webhook 及其触发器和状态。", "List available triggers": "列出可用触发器", "List credentials": "列出凭据", "List vault credentials (names, types and masked hints only — secrets are never returned).": "列出保险库凭据（仅名称、类型和掩码提示——绝不返回机密）。", "List webhooks": "列出 Webhook", "Model": "模型", "My own keys": "我自己的密钥", "New build": "新建构建", "No AI provider is configured yet. Set one up to use the AI Builder.": "尚未配置任何 AI 提供商。请先设置一个以使用 AI 构建器。", "No WordPress AI connector is currently configured. Add one under Settings → Connectors, or connect a provider key below.": "当前未配置任何 WordPress AI 连接器。请在“设置 → 连接器”中添加一个，或在下方连接提供商密钥。", "No configured AI provider could complete the request.": "没有任何已配置的 AI 提供商能够完成该请求。", "No credentials in the vault yet — create one and it will be assigned to this webhook.": "保险库中还没有凭据——创建一个后将分配给此 Webhook。", "No matches": "无匹配项", "No payload provided and no captured example exists yet for this trigger.": "未提供数据，且此触发器尚无已捕获的示例。", "Not found.": "未找到。", "Open webhook": "打开 Webhook", "Permanently delete a webhook and its triggers / mapping. Requires confirmation.": "永久删除 Webhook 及其触发器/映射。需要确认。", "Probe a target endpoint": "探测目标端点", "Provider": "提供商", "Read recent delivery logs (optionally for one webhook) to verify what was sent and how the endpoint responded.": "读取最近的投递日志（可选仅针对一个 Webhook），以核实发送了什么以及端点如何响应。", "Reference a stored vault credential from a webhook by id (the secret is injected at dispatch time and never exposed).": "通过 id 从 Webhook 引用保险库中存储的凭据（机密在发送时注入，绝不暴露）。", "Remove": "移除", "Remove this provider and delete its stored key?": "移除此提供商并删除其存储的密钥？", "Reuse an example payload captured for the same trigger on another webhook when this one has none.": "当此 Webhook 没有示例数据时，复用另一 Webhook 上为同一触发器捕获的示例。", "Reuse example from other webhooks": "复用其他 Webhook 的示例", "Reusing an example captured for this trigger on another webhook": "正在复用另一 Webhook 上为此触发器捕获的示例", "Reverted": "已还原", "Review plan before running": "运行前审查计划", "Run plan": "运行计划", "Search credentials…": "搜索凭据…", "Select a model": "选择模型", "Select a provider": "选择提供商", "Set conditions": "设置条件", "Set field mapping": "设置字段映射", "Shared Example": "共享示例", "Show all compatible (%d)": "显示所有兼容项（%d）", "Show recommended": "显示推荐项", "Skip": "跳过", "Start a new build, then describe what you want to integrate.": "开始新的构建，然后描述您想集成的内容。", "Step": "步骤", "Test-dispatch a webhook": "测试发送 Webhook", "That URL is not allowed (private, reserved or invalid host).": "不允许该 URL（私有、保留或无效的主机）。", "That link would create a cycle across an existing chain.": "该环节会在现有链中产生循环。", "The AI Client returned no text.": "AI 客户端未返回文本。", "The AI provider key could not be decrypted.": "无法解密 AI 提供商密钥。", "The AI provider returned an error.": "AI 提供商返回错误。", "The AI provider returned no text.": "AI 提供商未返回文本。", "The WordPress AI Client is not available.": "WordPress AI 客户端不可用。", "The condition rule on \"%1$s\" (%2$s) has an empty value — ask the user for the value before setting this condition.": "\"%1$s\"（%2$s）上的条件规则值为空——请在设置此条件前询问用户该值。", "The configured AI provider key was not found in the vault.": "在保险库中找不到已配置的 AI 提供商密钥。", "The endpoint could not be reached (%s). Check the URL is correct and publicly reachable, then retry.": "无法连接到端点（%s）。请检查 URL 是否正确且可公开访问，然后重试。", "The endpoint could not be reached. Check the URL is correct and publicly reachable, then retry.": "无法连接到端点。请检查 URL 是否正确且可公开访问，然后重试。", "The endpoint responded %d — it needs authentication. Add a credential to the webhook, then retry.": "端点响应 %d——需要身份验证。请为 Webhook 添加凭据后重试。", "The endpoint responded %d — the URL may be wrong or not accept this request. Double-check the endpoint URL on the webhook, then retry.": "端点响应 %d——URL 可能有误或不接受此请求。请仔细核对 Webhook 的端点 URL 后重试。", "The payload shape is the same for a trigger everywhere, so a new webhook can borrow an example already captured elsewhere. Turn off to require this webhook to capture its own.": "同一触发器的数据结构在任何地方都相同，因此新 Webhook 可以借用已在别处捕获的示例。关闭后将要求此 Webhook 捕获自己的示例。", "The webhook has no triggers; provide one.": "该 Webhook 没有触发器；请提供一个。", "There is no plan to run yet.": "还没有可运行的计划。", "There is nothing left to revert.": "没有可再还原的内容。", "There is nothing to revert.": "没有可还原的内容。", "Thinking…": "思考中…", "This removes the conversation and its build history. It does not delete any webhooks it created.": "这将删除该对话及其构建历史。不会删除其创建的任何 Webhook。", "This site no longer includes the WordPress 7.0 AI Client. Connect a provider key below, or restore WordPress 7.0 or later to use your connectors again.": "此站点不再包含 WordPress 7.0 AI 客户端。请在下方连接提供商密钥，或恢复到 WordPress 7.0 及以上版本以继续使用您的连接器。", "This step goes live or changes data. Confirm to run it.": "此步骤将上线或更改数据。请确认后运行。", "Too many probe calls — try again in a minute.": "探测调用过多——请一分钟后重试。", "Undo last change": "撤销上次更改", "Unknown AI provider.": "未知的 AI 提供商。", "Unknown ability: %s": "未知能力：%s", "Unknown condition operator \"%1$s\". Valid operators: %2$s.": "未知的条件运算符 \"%1$s\"。有效的运算符：%2$s。", "Untitled build": "未命名构建", "Update URL & retry": "更新 URL 并重试", "Update a webhook": "更新 Webhook", "Update an existing webhook (endpoint, method, triggers, headers, credential).": "更新现有 Webhook（端点、方法、触发器、标头、凭据）。", "Use": "使用", "Use a provider configured in WordPress, or add your own API keys. Keys are encrypted in your Credentials Vault and never returned over the API.": "使用在 WordPress 中配置的提供商，或添加您自己的 API 密钥。密钥加密存储在您的凭据保险库中，绝不会通过 API 返回。", "Use existing": "使用现有", "Waiting for earlier steps…": "等待前面的步骤…", "Webhook is live.": "Webhook 已上线。", "WordPress connectors": "WordPress 连接器", "Working…": "处理中…", "Your WordPress AI connectors are no longer available.": "您的 WordPress AI 连接器已不再可用。", "Your builds": "您的构建", "chain_id, source_webhook_id and target_webhook_id are required.": "chain_id、source_webhook_id 和 target_webhook_id 为必填项。", "conditions must be an object {enabled, type, rules: [...]}.": "conditions 必须是 {enabled, type, rules: [...]} 对象。", "conditions.rules must be an array of rule objects.": "conditions.rules 必须是规则对象数组。", "https://your-endpoint.example/webhook": "https://your-endpoint.example/webhook", "name and endpoint_url are required.": "name 和 endpoint_url 为必填项。", "of": "/", "webhook_id, trigger and conditions are required.": "webhook_id、trigger 和 conditions 为必填项。", "webhook_id, trigger and field_mapping are required.": "webhook_id、trigger 和 field_mapping 为必填项。", "↩︎ Reverted: %s": "↩︎ 已还原：%s", "WP Webhooks AI (included)": "WP Webhooks AI（已包含）", "WP Webhooks AI is included with your Pro license — no API keys needed. Your own keys and WordPress connectors remain available.": "WP Webhooks AI 已包含在您的 Pro 许可证中 — 无需 API 密钥。您自己的密钥和 WordPress 连接器仍然可用。", "WP Webhooks AI": "WP Webhooks AI", "Included": "已包含", "Credits this month": "本月积分", "Extra credits (never expire)": "额外积分（永不过期）", "Monthly credits reset on %s.": "每月积分将于 %s 重置。", "Buy credits": "购买积分", "Runs through the WP Webhooks AI service — no API keys needed.": "通过 WP Webhooks AI 服务运行 — 无需 API 密钥。", "Build with AI (bring your own API key)": "使用 AI 构建（自备 API 密钥）", "AI credits included — hosted AI, no API keys needed": "AI 积分已包含 — 托管 AI，无需 API 密钥", "%1$s is not supported on %2$s. Supported methods: %3$s.": "%2$s 不支持 %1$s。支持的方法：%3$s。", "Application Passwords are disabled for your user account.": "您的用户账户已禁用应用程序密码。", "Application Passwords are not available on this site. They require HTTPS (or a local development environment).": "此站点不支持应用程序密码。需要 HTTPS（或本地开发环境）。", "Application Passwords require WordPress 5.6 or newer.": "应用程序密码需要 WordPress 5.6 或更高版本。", "Asynchronous delivery": "异步投递", "Asynchronous: queued and delivered in the background on the next cron run, with automatic retries — it doesn’t slow the triggering request, but nothing is sent until a working cron runs. Synchronous: delivered instantly, inline with the triggering request — it works without any cron, at the cost of a little added latency. Toggle to switch.": "异步：进入队列并在下次 cron 运行时在后台投递，自动重试 — 不会拖慢触发请求，但在 cron 正常运行之前不会发送任何内容。同步：立即投递，在触发请求内完成 — 无需 cron 即可工作，代价是略微增加延迟。切换开关即可更换。", "Create & continue": "创建并继续", "Create a WP Application Password for me": "为我创建 WP 应用程序密码", "Create a WordPress Application Password credential": "创建 WordPress 应用程序密码凭据", "Credential name (e.g. WP REST admin)": "凭据名称（例如 WP REST admin）", "Describe a REST API route ON THIS SITE (core or any plugin) from its self-declared schema: every argument with its type, description and whether it is REQUIRED. ALWAYS run this before building an internal automation (a webhook whose endpoint_url points at this site's own wp-json) and satisfy every required argument — e.g. POST /wp/v2/users requires username, email AND password, which mapping alone cannot always supply. Pass the route path relative to /wp-json (e.g. \"/wp/v2/users\") and the HTTP method you plan to use. Internal routes only — it cannot describe external APIs.": "根据站点自身声明的 schema 描述本站点上的一条 REST API 路由（核心或任何插件）：每个参数的类型、描述以及是否为必填。在构建内部自动化（endpoint_url 指向本站点 wp-json 的 Webhook）之前务必先运行此项，并满足每个必填参数 — 例如 POST /wp/v2/users 需要 username、email 和 password，仅靠映射不一定能提供。传入相对于 /wp-json 的路由路径（例如 \"/wp/v2/users\"）以及计划使用的 HTTP 方法。仅限内部路由 — 无法描述外部 API。", "Describe what you want in chat — the built-in AI agent plans, builds, and tests your WordPress webhooks, integrations, and automations.": "在聊天中描述您的需求 — 内置 AI 代理会规划、构建并测试您的 WordPress Webhook、集成和自动化。", "Destructive probe methods (PUT, PATCH, DELETE) require confirmation.": "破坏性探测方法（PUT、PATCH、DELETE）需要确认。", "Get a REST route's argument schema (this site)": "获取 REST 路由的参数 schema（本站点）", "List WordPress do_action hooks discovered on this site (runtime + static scan) that can be used as webhook triggers. The full catalog is LARGE (hundreds of hooks): when hunting for a specific plugin's hooks, always pass search (matches hook name or plugin slug, e.g. {\"search\":\"cf7\"}) instead of listing everything. Results cap at 200 with a total count.": "列出本站点上发现的可用作 Webhook 触发器的 WordPress do_action 钩子（运行时 + 静态扫描）。完整目录很大（数百个钩子）：查找特定插件的钩子时，请始终传入 search（匹配钩子名称或插件 slug，例如 {\"search\":\"cf7\"}），而不是列出全部。结果上限为 200 条，并附总数。", "Make a guarded test HTTP call to validate an endpoint before going live. To probe a webhook you created, pass webhook_id (e.g. {{step_2.id}}) — its URL, credential and method are reused automatically, so never ask the user for the endpoint URL again. Only pass url for an endpoint not tied to a webhook. A probe sends an EMPTY body, so GET, HEAD and POST run without confirmation; only PUT, PATCH and DELETE (which a body-less call can still mutate or delete) require confirmation. Returns status, redacted headers and a truncated, redacted body. The raw secret is never exposed.": "执行受保护的测试 HTTP 调用，在上线前验证端点。要探测您创建的 Webhook，请传入 webhook_id（例如 {{step_2.id}}）— 其 URL、凭据和方法会自动复用，因此切勿再次向用户询问端点 URL。仅在端点未关联任何 Webhook 时才传入 url。探测发送空 body，因此 GET、HEAD 和 POST 无需确认即可运行；只有 PUT、PATCH 和 DELETE（即使没有 body 也可能修改或删除数据）需要确认。返回状态码、脱敏后的响应头和截断且脱敏的 body。原始密钥绝不会被暴露。", "Mint a WordPress Application Password for the CURRENT signed-in admin and store it as a \"basic\" vault credential named \"WP REST API (internal) — \", for authenticating this site's own REST API. Use it for INTERNAL automations (endpoint_url on this site's wp-json), then reference the new credential id from assign_credential as {{step_N.id}}. Requires confirmation; the secret is written straight to the vault and never exposed. The optional name only labels the Application Password in the user's profile.": "为当前登录的管理员生成 WordPress 应用程序密码，并以名为 \"WP REST API (internal) — \" 的 \"basic\" 凭据存入保险库，用于本站点自身 REST API 的身份验证。将其用于内部自动化（endpoint_url 指向本站点的 wp-json），然后在 assign_credential 中以 {{step_N.id}} 引用新凭据 id。需要确认；密钥直接写入保险库，绝不会被暴露。可选的名称仅用于在用户个人资料中标注该应用程序密码。", "Minted the Application Password but failed to store it in the vault.": "已生成应用程序密码，但存入保险库失败。", "No REST route matches \"%s\" on this site. Route paths are relative to /wp-json, e.g. \"/wp/v2/users\". This only describes THIS site's own REST API — not external endpoints.": "本站点上没有与 \"%s\" 匹配的 REST 路由。路由路径相对于 /wp-json，例如 \"/wp/v2/users\"。此功能仅描述本站点自身的 REST API — 不适用于外部端点。", "No credentials in the vault yet — create one and it will be used for this step.": "保险库中还没有凭据 — 创建一个后将用于此步骤。", "No signed-in user to provision an Application Password for — open the AI Builder while logged in as an administrator.": "没有已登录的用户可供创建应用程序密码 — 请以管理员身份登录后再打开 AI Builder。", "Password (or Application Password)": "密码（或应用程序密码）", "Return the last captured example payload, field mapping and conditions for a trigger so the agent can map against the real payload shape. Pass webhook_id to read that webhook's own capture; omit it to get the latest example for the trigger from any webhook. If the result carries a capture_warning, the capture is stale/opaque (no mappable fields): follow the warning — show the user what the capture contains and ask them to re-fire the event — instead of proposing mappings.": "返回触发器最近捕获的示例数据、字段映射和条件，以便代理根据真实的数据结构进行映射。传入 webhook_id 可读取该 Webhook 自己的捕获；省略则获取任意 Webhook 中该触发器的最新示例。如果结果带有 capture_warning，说明捕获已过期/不可解析（没有可映射的字段）：请遵循警告 — 向用户展示捕获内容并请其重新触发事件 — 而不是提出映射建议。", "Some proposed steps were removed because this site cannot run them: %s. The remaining plan may be incomplete. If these are Code Glue abilities, make sure Webhook Actions Pro is installed, up to date and licensed.": "部分建议的步骤已被移除，因为本站点无法执行它们：%s。剩余方案可能不完整。如果这些是 Code Glue 能力，请确保已安装最新版且有有效许可证的 Webhook Actions Pro。", "Synchronous delivery": "同步投递", "The AI provider request failed mid-turn (%s). Progress so far is saved — send the message again to retry from here.": "AI 提供商请求在回合中途失败（%s）。目前的进度已保存 — 重新发送消息即可从此处继续。", "This sends a REAL delivery to the endpoint right now — it is not a dry run. If the webhook targets this site’s own REST API (e.g. wp-json/wp/v2/users) it can actually create or modify data, such as creating a WordPress user. Confirm to send it for real.": "这会立即向端点发送一次真实投递 — 不是演练。如果 Webhook 指向本站点自身的 REST API（例如 wp-json/wp/v2/users），它可能真的创建或修改数据，例如创建 WordPress 用户。确认后将真实发送。", "This step needs a stored auth credential. Pick one from the vault or create a new one — the secret stays in the vault and is injected only at dispatch.": "此步骤需要已存储的身份验证凭据。从保险库中选择一个或新建一个 — 密钥保留在保险库中，仅在投递时注入。", "Use credential & continue": "使用凭据并继续", "Webhook Actions - build automations and integrations with AI help": "Webhook Actions — 借助 AI 构建自动化与集成", "Your selected model %1$s couldn't respond, so this reply came from %2$s instead. (%3$s) Pick a different model with Change model.": "您选择的模型 %1$s 无法响应，因此本条回复来自 %2$s。（%3$s）可通过“更换模型”选择其他模型。", "provider unavailable": "提供商不可用", "reused": "已复用", "route is required, e.g. \"/wp/v2/users\".": "route 为必填项，例如 \"/wp/v2/users\"。", "trigger is required.": "trigger 为必填项。", "%s credits left": "剩余 %s 积分", "%1$d webhook(s) and %2$d chain(s) to import.": "待导入 %1$d 个 Webhook 和 %2$d 条链。", "%1$sOrder:%2$s field mapping runs first, then this snippet — so %3$s$payload%4$s here is the %5$spost-mapping%6$s payload, exactly as at dispatch.": "%1$s顺序：%2$s先执行字段映射，再运行此代码片段——因此这里的 %3$s$payload%4$s 是%5$s映射之后%6$s的数据，与发送时完全一致。", "%d AI credits added to your balance.": "已向你的余额添加 %d 个 AI 额度。", "%d characters left": "还可输入 %d 个字符", "%d duplicate(s) skipped.": "已跳过 %d 个重复项。", "%d webhook(s) already exist here (same UUID).": "此处已存在 %d 个 Webhook（UUID 相同）。", "%d without a description": "%d 项缺少说明", "A chain in this file has no name and was not imported.": "此文件中有一条链没有名称，未被导入。", "A hop of \"%s\" points at a webhook that is not in this file, and was left out.": "“%s”中的一跳指向了不在此文件中的 Webhook，已被略过。", "A hop of \"%s\" was left out because it would have made the chain loop back on itself.": "“%s”中的一跳已被略过，因为它会让链形成循环。", "Adds a diagnostic panel to Build with AI where you can read and export the recorded trace. Independent of logging above.": "在“用 AI 构建”中添加诊断面板，可查看并导出已记录的追踪信息。与上面的日志开关相互独立。", "Adds your prompts and the assistant's replies so the recipient can see how this build was made. Read results are never included and obvious secrets are masked, but the conversation may still mention details about your site — review before sharing publicly.": "附上你的提示词与助手的回复，让接收方了解此配置的构建过程。读取结果从不包含在内，明显的密钥会被遮蔽，但对话仍可能提到你站点的细节——公开分享前请先检查。", "Anonymize my site address": "匿名化我的站点地址", "Automation": "自动化", "Build title": "配置标题", "Captured + Mapping + Pre-dispatch Glue": "捕获数据 + 字段映射 + 发送前 Glue", "Captured + Mapping + Pre-dispatch Glue + Post-dispatch Glue": "捕获数据 + 字段映射 + 发送前 Glue + 发送后 Glue", "Captured example payloads are anonymized automatically: names, addresses, emails, phone numbers and IP addresses are replaced with placeholders, so the field mapping still previews without carrying anyone's data.": "捕获的示例数据会自动匿名化：姓名、地址、邮箱、电话号码和 IP 地址都会替换为占位值，字段映射仍可正常预览，但不会带走任何人的数据。", "Captured example payloads hold whatever a real visitor submitted — names, addresses, emails, phone numbers, IP addresses. They are replaced with placeholders unless you tick this, which you only want for a private backup of your own site.": "捕获的示例数据包含真实访客提交的一切内容——姓名、地址、邮箱、电话号码、IP 地址。除非勾选此项，否则它们会被替换为占位值；只有为自己站点做私人备份时才需要保留原值。", "Chain description (optional)": "链说明（可选）", "Chains (member webhooks included automatically)": "链（自动包含其中的 Webhook）", "Code Glue is custom PHP that runs on your site when these webhooks fire. Only import builds from a source you trust — review each snippet below.": "Code Glue 是这些 Webhook 触发时在你站点上运行的自定义 PHP 代码。只导入你信任来源的配置——请先查看下面的每个代码片段。", "Connects WordPress to a named service — a CRM, a spreadsheet, a chat app.": "把 WordPress 连接到某个具体服务——CRM、电子表格或聊天工具。", "Could not create the Application Password.": "无法创建应用程序密码。", "Could not read this build.": "无法读取此配置。", "Could not read this file. Make sure it is a build JSON exported from Webhook Actions.": "无法读取此文件。请确认它是从 Webhook Actions 导出的配置 JSON。", "Create a HubSpot deal when a WooCommerce order is placed": "WooCommerce 下单时在 HubSpot 中创建交易", "Create a WP Application Password": "创建 WP 应用程序密码", "Create a new vault credential": "在保险库中新建凭据", "Created “%s”": "已创建“%s”", "Credit yourself (optional)": "署名（可选）", "Described": "已填写说明", "Description (optional)": "说明（可选）", "Description must be %d characters or fewer.": "说明不得超过 %d 个字符。", "Descriptions travel with the build and are saved here too — they are what makes a shared build understandable to someone else.": "说明会随配置一同传递，也会保存在这里——正是它让别人能看懂你分享的配置。", "Download JSON": "下载 JSON", "Download a portable JSON build. Secrets are never included — imported auth is re-linked to your vault.": "下载可移植的 JSON 配置。密钥从不包含在内——导入时授权会重新关联到你的保险库。", "Download everything this build created as a portable JSON file. Secrets are never included — whoever imports it re-links auth to their own vault.": "把此配置创建的所有内容下载为可移植的 JSON 文件。密钥从不包含在内——导入者会把授权关联到自己的保险库。", "Drop a build JSON here, or click to browse": "将配置 JSON 拖到此处，或点击浏览", "Drop to import": "松开以导入", "Edit chain": "编辑链", "Edit “%s”": "编辑“%s”", "Export": "导出", "Export chain": "导出链", "Export everything": "导出全部", "Export failed.": "导出失败。", "Export webhooks & chains": "导出 Webhook 与链", "Exporting…": "正在导出…", "Field mapping applied first, then pre-dispatch Code Glue — the dispatch order": "先应用字段映射，再运行发送前 Code Glue——即实际发送顺序", "Flagged: %s": "标记为：%s", "Full pipeline in dispatch order — post-dispatch Code Glue fires after delivery": "按发送顺序的完整流程——发送后 Code Glue 在投递完成后触发", "Hide description": "隐藏说明", "Import": "导入", "Import as new copies": "作为新副本导入", "Import complete": "导入完成", "Import failed.": "导入失败。", "Import webhooks & chains": "导入 Webhook 与链", "Imported %1$d webhook(s) and %2$d chain(s).": "已导入 %1$d 个 Webhook 和 %2$d 条链。", "Importing…": "正在导入…", "Include the AI conversation": "附上 AI 对话", "Integration": "集成", "Invalid import file — %1$s %2$s": "导入文件无效 — %1$s %2$s", "Jump to an imported item": "跳转到已导入的项目", "Keep the real captured values": "保留真实的捕获数据", "LinkedIn": "LinkedIn", "Load a build JSON exported from Webhook Actions.": "载入从 Webhook Actions 导出的配置 JSON。", "Log AI Dev Trace": "记录 AI 开发追踪", "Markdown supported.": "支持 Markdown。", "Missing import document.": "缺少导入文档。", "No authorization": "无需授权", "No authorization needed for this build.": "此配置无需授权。", "No chains match your search.": "没有匹配的链。", "No webhooks match your search.": "没有匹配的 Webhook。", "Nothing to preview yet — switch to Write to add a description.": "暂无可预览的内容——切换到“撰写”添加说明。", "One or two sentences — this is what people read on the listing before they open the build.": "一两句话——别人在打开配置前会在列表中看到它。", "Optional markdown description documenting what this webhook does.": "可选的 Markdown 说明，用于记录此 Webhook 的作用。", "Pick the one that fits best — a build is listed in a single collection.": "选择最合适的一个——每个配置只会出现在一个合集中。", "Preview": "预览", "Publish build": "发布配置", "Publish it on wpwebhooks.org — 50 AI credits, +20 for every like.": "把它发布到 wpwebhooks.org——50 个 AI 额度，每个点赞再加 20。", "Publish this build on wpwebhooks.org so anyone can import it. Secrets are never included, and you keep 50 AI credits for publishing plus 20 every time someone likes it.": "把此配置发布到 wpwebhooks.org，任何人都能导入。密钥从不包含在内；发布可获得 50 个 AI 额度，每次有人点赞再得 20 个。", "Publish your build": "发布你的配置", "Published builds are checked automatically before they go live, and can be taken down later from your account.": "已发布的配置在上线前会自动审核，之后也可以从你的账户中撤下。", "Publishing failed.": "发布失败。", "Publishing…": "正在发布…", "Reading this build…": "正在读取此配置…", "Reading…": "正在读取…", "Records the exact prompts and raw responses exchanged with the AI model to a protected log file, so support can diagnose a build you report. On by default; API keys are always redacted and entries older than 30 days are pruned automatically. Turn this off if you would rather not keep the log.": "把与 AI 模型往来的完整提示词和原始响应记录到受保护的日志文件，便于支持人员诊断你反馈的问题。默认开启；API 密钥始终会被遮蔽，超过 30 天的记录会自动清理。若不希望保留日志，可关闭此项。", "Replaces your site URL with example.com everywhere it appears — the export header, endpoint URLs, Code Glue and the AI conversation. Whoever imports the build re-points those endpoints at their own site.": "把出现过站点网址的地方全部替换为 example.com——包括导出头信息、端点地址、Code Glue 和 AI 对话。导入者会把这些端点改指向自己的站点。", "Runs a process end to end — a chain of steps, a scheduled job, a workflow.": "端到端地跑完一个流程——一串步骤、一个定时任务或一条工作流。", "Search chains…": "搜索链…", "Search webhooks…": "搜索 Webhook…", "Secret / token": "密钥 / 令牌", "Select credential": "选择凭据", "Share this build": "分享此配置", "Short summary": "简短摘要", "Show AI Dev Trace panel": "显示 AI 开发追踪面板", "Show in list": "在列表中显示", "Show “%s” in list": "在列表中显示“%s”", "Skip the duplicates": "跳过重复项", "Some parts were left out": "部分内容已被略过", "The chain \"%s\" could not be created.": "无法创建链“%s”。", "This becomes the page title and headline.": "它将成为页面标题和大标题。", "This build calls this site’s own WP REST API. Reuse or create a WordPress Application Password — there is no secret to paste.": "此配置会调用本站自身的 WP REST API。复用或新建一个 WordPress 应用程序密码即可——无需粘贴任何密钥。", "This build contains %d Code Glue snippet": "此配置包含 %d 个 Code Glue 代码片段", "This build includes a Build-with-AI transcript, shown for reference on the source — it is not imported.": "此配置附有“用 AI 构建”的对话记录，仅在来源处供参考——不会被导入。", "This build needs authorization credentials": "此配置需要授权凭据", "Use an existing vault credential": "使用保险库中已有的凭据", "Website": "网站", "What does this chain automate? Markdown supported.": "这条链自动化了什么？支持 Markdown。", "What does this do, and what does someone need before importing it?": "它的作用是什么？导入前需要准备什么？", "What does this webhook do? Markdown supported.": "这个 Webhook 有什么作用？支持 Markdown。", "What this build contains": "此配置包含的内容", "Where does this belong?": "它属于哪一类？", "Write": "撰写", "Your build is published.": "你的配置已发布。", "Your links appear on the build page. They are published as nofollow.": "你的链接会显示在配置页面上，并以 nofollow 方式发布。", "Your name": "你的名字", "contains no webhooks.": "不包含任何 Webhook。", "exceeds the maximum length of %d bytes.": "超过了 %d 字节的最大长度。", "has unexpected key(s): %s.": "包含意外的键：%s。", "is %1$d; this plugin imports version %2$d builds.": "为 %1$d；此插件可导入版本 %2$d 的配置。", "is missing required key \"%s\".": "缺少必需的键“%s”。", "is required and must be an integer.": "为必填项，且必须是整数。", "is required when mode is \"vault\".": "当模式为“vault”时为必填项。", "may only contain letters, numbers, hyphens and underscores.": "只能包含字母、数字、连字符和下划线。", "must be a boolean.": "必须是布尔值。", "must be a string or null.": "必须是字符串或 null。", "must be a string.": "必须是字符串。", "must be a {key, value} object.": "必须是 {key, value} 对象。", "must be an array of strings.": "必须是字符串数组。", "must be an array of {key, value} pairs.": "必须是 {key, value} 键值对数组。", "must be an array.": "必须是数组。", "must be an http:// or https:// URL.": "必须是 http:// 或 https:// 网址。", "must be an object.": "必须是对象。", "must be one of: %s.": "必须是以下之一：%s。", "must not be empty.": "不能为空。", "must not contain line breaks.": "不能包含换行符。", "references a credential that is not listed in credentials[].": "引用了未列在 credentials[] 中的凭据。", "references a webhook UUID not present in webhooks[].": "引用了 webhooks[] 中不存在的 Webhook UUID。", "resets in %1$dd %2$dh": "%1$d 天 %2$d 小时后重置", "resets in %1$dh %2$dm": "%1$d 小时 %2$d 分钟后重置", "resets soon": "即将重置", "Building your page…": "正在生成你的页面…", "Change what this build contains — add or remove a webhook — to publish it as a separate page.": "更改此配置的内容（添加或移除 webhook），即可将其作为独立页面发布。", "Checking whether the page is live…": "正在检查页面是否已上线…", "It will appear at this address once it has been reviewed.": "通过审核后将出现在此地址。", "Published — your build is live.": "已发布 — 你的配置已上线。", "The page appears at this address once the website finishes rebuilding — it is safe to close this.": "网站重新构建完成后，页面就会出现在此地址 — 你可以放心关闭此窗口。", "Your build was received.": "已收到你的配置。", "wpwebhooks.org rebuilds after every publish — about %d seconds left. The address becomes a link the moment the page is live.": "每次发布后 wpwebhooks.org 都会重新构建 — 大约还需 %d 秒。页面一上线，该地址就会变成链接。", "\"%s\" changes or deletes live data. Re-send the same call with \"confirmed\": true once a human has approved it.": "“%s” 会更改或删除线上数据。请在人工批准后，带上 \"confirmed\": true 重新发送同一调用。", "%d deliveries queued": "已将 %d 次投递加入队列", "%d events replayed": "已重放 %d 个事件", "%d of the selected entries could not be queued: no queue job is left for them.": "所选条目中有 %d 条无法加入队列：它们已没有对应的队列任务。", "%d retries queued": "已将 %d 次重试加入队列", "%s credits left on your free trial.": "你的免费试用还剩 %s 个积分。", "%s free credits": "%s 个免费积分", "(none yet on this site)": "（本站点尚无）", "A token that could would be able to run arbitrary PHP on this site, so it is off by default. Turn on \"Let API tokens write Code Glue\" in Settings to allow it.": "能做到这一点的令牌就能在本站点运行任意 PHP，因此默认关闭。要允许，请在“设置”中开启“允许 API 令牌写入 Code Glue”。", "AI credits included, External Cron, more sites, and priority support. Everything else is free.": "包含 AI 积分、External Cron、更多站点和优先支持。其余一切免费。", "After Mapping Payload Preview": "映射后的载荷预览", "After Pre-dispatch Code Glue Payload": "预发送 Code Glue 之后的载荷", "Ask the agent to fix the payload — it can see this response now — then retry. Skipping leaves the rest of the plan (including going live) to run on a delivery that failed.": "让智能体修复载荷——它现在能看到这个响应——然后重试。跳过会让计划的其余部分（包括上线）在一次失败的投递上继续执行。", "Assign a Code Glue snippet to a webhook": "将 Code Glue 代码片段分配给 Webhook", "Attach a snippet to a webhook+trigger and enable it: stage \"pre\" transforms the payload before dispatch, stage \"post\" runs side effects after the response. Snippet errors never break a delivery (the payload falls back unmodified and the error is logged). Attaching to a LIVE webhook requires confirmation; on a still-disabled webhook being built it runs without one. Pass snippet_id 0 to unassign, or enabled false to keep it assigned but paused.": "将代码片段附加到 Webhook+触发器并启用：\"pre\" 阶段在发送前转换载荷，\"post\" 阶段在收到响应后执行副作用。代码片段出错绝不会中断投递（载荷按原样回退并记录错误）。附加到已上线的 Webhook 需要确认；附加到仍处于禁用、正在构建的 Webhook 则无需确认。传 snippet_id 0 可取消分配，传 enabled false 可保持分配但暂停。", "Base wait in seconds the backoff strategy multiplies. Null inherits the site-wide setting, then 30.": "退避策略所乘的基础等待秒数。Null 继承站点设置，否则为 30。", "Built from a reference payload — the shape is real, the values are ours. The test step checks it against your endpoint.": "基于参考载荷构建——结构是真实的，数值是我们的。测试步骤会用你的端点检查它。", "Capture an example payload for \"%s\" — fire the event once (e.g. publish a test post)": "为“%s”捕获一个示例载荷——触发该事件一次（例如发布一篇测试文章）", "Ceiling in seconds for an exponential backoff. Null inherits the site-wide setting, then 3600.": "指数退避的上限秒数。Null 继承站点设置，否则为 3600。", "Choose whether this is an integration or an automation.": "选择这是一个集成还是一个自动化。", "Choose which payload the conditions read from. Original is the raw payload, before field mapping. Transformed is the payload after mapping AND after the pre-dispatch Code Glue snippet — pick it when you filter on a value the snippet adds. Note: if a field does not exist in the payload you pick, negative operators like 'not equals' still pass, so the event is sent.": "选择条件读取哪个载荷。“原始”是字段映射之前的原始载荷。“转换后”是映射之后且经过预发送 Code Glue 代码片段之后的载荷——当你按代码片段添加的值过滤时选它。注意：如果字段在所选载荷中不存在，“不等于”之类的否定运算符仍会通过，事件就会被发送。", "Code Glue is switched off in wp-config.php.": "Code Glue 已在 wp-config.php 中关闭。", "Code Glue snippets are PHP that runs on this site, so writing one normally requires a signed-in user who is allowed to edit plugin code. Turning this on lets a full-scope API token — including a connected AI tool over MCP — write and assign snippets too. That makes the token as powerful as a plugin editor, so leave it off unless you need it. Reading snippets never required it.": "Code Glue 代码片段是在本站点运行的 PHP，因此写入通常需要一位有权编辑插件代码的已登录用户。开启此项后，具有完整权限范围的 API 令牌——包括通过 MCP 连接的 AI 工具——也可以写入和分配代码片段。这会让该令牌拥有与插件编辑器同等的权力，所以除非确有需要，否则请保持关闭。读取代码片段从不需要此权限。", "Code Glue — PHP snippets before and after dispatch": "Code Glue——发送前后运行的 PHP 代码片段", "Connect your own key": "连接你自己的密钥", "Connect your own provider, or add Pro credits, to keep building.": "连接你自己的服务商，或添加 Pro 积分，以继续构建。", "Could not reach the WP Webhooks publishing service: %s": "无法连接 WP Webhooks 发布服务：%s", "Could not start the free trial.": "无法开始免费试用。", "Could not start the free trial. Please try again.": "无法开始免费试用。请重试。", "Create a Code Glue PHP snippet (inert until assigned to a webhook). Write plain PHP without a \",\"operator\":\"equals|not_equals|contains|not_contains|greater_than|less_than|is_empty|is_not_empty|is_true|is_false|array_contains|object_contains\",\"value\":\"...\"}]}. A rule may add an optional \"cast\":\"number\"|\"string\"|\"boolean\"|\"stringify\" to coerce the payload value before comparing (e.g. numeric compare on a string field). A rules item may also be a nested group {\"type\":\"group\",\"match\":\"and\"|\"or\",\"rules\":[...]}, and there is no limit on how many rules a webhook may carry — use as many as the user's logic actually needs. conditions_evaluate_on decides WHICH payload the field paths address, so set it deliberately: \"original\" (default) = the raw captured payload, so paths look like \"args.0.form_id\" — read them from get_trigger_schema; \"transformed\" = the payload AFTER the field mapping AND after any pre-dispatch Code Glue snippet, so paths are the mapping's target names plus any key the snippet injects — use this, and ONLY this, when filtering on something a snippet computes. Mixing them up silently breaks the filter: a path that does not exist evaluates to null, and the NEGATIVE operators (not_equals, not_contains, is_empty) then PASS, so the event is dispatched rather than filtered out. For a rule that must fail closed when its field is missing, prefer a positive operator (is_internal equals \"false\" rather than is_internal not_equals \"true\").": "为 Webhook+触发器设置条件发送规则，只让匹配的事件离开站点。conditions 必须是一个对象 {\"enabled\":true,\"type\":\"and\"|\"or\",\"rules\":[{\"field\":\"<捕获载荷中的点分路径>\",\"operator\":\"equals|not_equals|contains|not_contains|greater_than|less_than|is_empty|is_not_empty|is_true|is_false|array_contains|object_contains\",\"value\":\"...\"}]}。规则可添加可选的 \"cast\":\"number\"|\"string\"|\"boolean\"|\"stringify\"，在比较前强制转换载荷值（例如对字符串字段做数值比较）。rules 项也可以是嵌套组 {\"type\":\"group\",\"match\":\"and\"|\"or\",\"rules\":[...]}，一个 Webhook 可携带的规则数量没有限制——用户逻辑确实需要多少就用多少。conditions_evaluate_on 决定字段路径指向哪个载荷，因此要有意识地设置：\"original\"（默认）= 原始捕获的载荷，路径形如 \"args.0.form_id\"——从 get_trigger_schema 读取；\"transformed\" = 字段映射之后并经过任何预发送 Code Glue 代码片段之后的载荷，路径是映射的目标名称加上代码片段注入的键——当且仅当按代码片段计算出的内容过滤时使用它。混淆两者会悄悄破坏过滤：不存在的路径求值为 null，否定运算符（not_equals、not_contains、is_empty）随即通过，事件就会被发送而不是被过滤掉。对于字段缺失时必须安全失败的规则，优先用肯定运算符（is_internal equals \"false\" 而不是 is_internal not_equals \"true\"）。", "Set the payload field mapping for a webhook+trigger. field_mapping MUST be an object {\"mappings\":[{\"source\":\"\",\"target\":\"\",\"cast\":\"number|string|boolean|stringify\" (optional)}],\"excluded\":[\"\"],\"includeUnmapped\":true|false}. It can only move/rename/exclude EXISTING payload fields — static or constant values are NOT supported (inject those with a pre-dispatch Code Glue snippet instead). The mapping runs BEFORE any pre-dispatch snippet, so snippet output cannot be mapped — and, in the other direction, the snippet only ever sees what the mapping LEFT BEHIND. With includeUnmapped:false everything unmapped is deleted, including \"args\", so a snippet reading $args[0] gets nothing: whenever a snippet needs a source field, map it through explicitly (e.g. source \"args.0\" → target \"post_id\") and have the snippet unset it before returning if it must not be sent. Run get_trigger_schema first and take source paths from the real captured payload.": "为 Webhook+触发器设置载荷字段映射。field_mapping 必须是一个对象 {\"mappings\":[{\"source\":\"<捕获载荷中的点分路径>\",\"target\":\"<出站请求体中的点分路径>\",\"cast\":\"number|string|boolean|stringify\"（可选）}],\"excluded\":[\"<要丢弃的点分路径>\"],\"includeUnmapped\":true|false}。它只能移动/重命名/排除已存在的载荷字段——不支持静态或常量值（请用预发送 Code Glue 代码片段注入）。映射在任何预发送代码片段之前运行，所以代码片段的输出无法被映射——反过来，代码片段只能看到映射留下的内容。includeUnmapped:false 时所有未映射的内容都会被删除，包括 \"args\"，因此读取 $args[0] 的代码片段什么也拿不到：当代码片段需要某个源字段时，请显式映射它（例如 source \"args.0\" → target \"post_id\"），若不应发送则让代码片段在返回前 unset 它。先运行 get_trigger_schema，并从真实捕获的载荷中获取源路径。", "Snippet not found.": "未找到代码片段。", "Snippet ran but changed nothing": "代码片段已运行但没有任何更改", "Snippets already assigned keep running, but they cannot be edited or previewed here.": "已分配的代码片段继续运行，但无法在此编辑或预览。", "Snippets are PHP that runs on this site, so WordPress gates them the same way it gates editing plugin code. Ask an administrator to make the change, or to grant your role that capability.": "代码片段是在本站点运行的 PHP，因此 WordPress 对它们的限制与编辑插件代码相同。请管理员进行更改，或为你的角色授予该权限。", "Step %1$s (%2$s) did not succeed: %3$s": "步骤 %1$s（%2$s）未成功：%3$s", "Test-run a snippet (by snippet_id, or raw code) against a real captured payload WITHOUT dispatching anything. Pass webhook_id+trigger to use that webhook's captured example WITH ITS STORED FIELD MAPPING APPLIED — the exact array the snippet gets at dispatch — or provide an explicit payload to test a shape yourself. Returns input_payload (what the snippet received; check that the keys your code reads are actually there), the resulting payload, any PHP error and printed output. If result is identical to input_payload, your code matched nothing and no-oped — fix it before assigning. Always preview before assigning.": "在不发送任何内容的前提下，用真实捕获的载荷试运行一个代码片段（通过 snippet_id 或原始代码）。传入 webhook_id+trigger 以使用该 Webhook 已捕获的示例并应用其已保存的字段映射——正是代码片段在发送时得到的数组——或提供一个显式载荷来自行测试某种结构。返回 input_payload（代码片段收到的内容；检查你的代码读取的键确实存在）、结果载荷、任何 PHP 错误和打印输出。如果结果与 input_payload 完全相同，说明你的代码没有匹配到任何内容、什么也没做——请在分配前修复。分配前务必先预览。", "That is not a published build address.": "那不是一个已发布构建的地址。", "That is roughly %s agent runs. A run is one message you send; most integrations take two or three to plan, build and test.": "这大约相当于 %s 次智能体运行。一次运行就是你发送的一条消息；大多数集成需要两到三次来规划、构建和测试。", "The AI answered in prose instead of a runnable plan, so no steps were proposed and nothing has been applied. Ask it to \"send that as a plan\" to try again.": "AI 用文字作答而不是给出可执行的计划，因此没有提出任何步骤，也没有应用任何更改。让它“以计划形式发送”再试一次。", "The AI read this reference on our server — the request shape below comes from the vendor's documentation, not from memory.": "AI 已在我们的服务器上读取了这份参考文档——下方的请求结构来自供应商的文档，而不是凭记忆。", "The AI returned no text.": "AI 没有返回任何文本。", "The AI service returned an error.": "AI 服务返回了错误。", "The API Docs Library tried to read this service's reference but it was not ready in time, so this plan relies on the model's own knowledge of that API. Test before enabling.": "API Docs Library 曾尝试读取该服务的参考文档，但未能及时准备好，因此此计划依赖模型自身对该 API 的了解。请在启用前测试。", "The delivery runs when the queue next drains — on the next cron tick. On a quiet site that can take a while, so you can also run it right now.": "投递将在队列下一次清空时运行——也就是下一次 cron 触发时。在访问量少的站点上这可能要等一会儿，所以你也可以立即运行它。", "The endpoint is reachable but answered %d — expected, because a probe sends an EMPTY body. This does NOT show the integration works. Validate it with a test delivery (test_dispatch), which sends the real mapped payload, before going live.": "端点可达但返回了 %d——这是预期的，因为探测发送的是空请求体。这并不能证明集成可用。请在上线前用测试投递（test_dispatch）验证，它会发送真实的映射后载荷。", "The endpoint rejected the test delivery with %d — it needs authentication. Attach a credential to the webhook, then retry.": "端点以 %d 拒绝了测试投递——它需要身份验证。请为 Webhook 附加一个凭据，然后重试。", "The endpoint rejected the test delivery with %d — nothing was created on the far side. Fix the payload (field mapping or the pre-dispatch snippet) and retry before going live.": "端点以 %d 拒绝了测试投递——对方什么也没创建。请修复载荷（字段映射或预发送代码片段），并在上线前重试。", "The endpoint responded:": "端点的响应：", "The example payload for \"%s\" has now been captured, so the field paths are readable. Read it with get_trigger_schema and finish the build: set the field mapping from the REAL paths, add a pre-dispatch Code Glue snippet if the destination needs a shape mapping alone cannot produce, then test_dispatch before enabling.": "“%s”的示例载荷现已捕获，字段路径可以读取了。用 get_trigger_schema 读取它并完成构建：根据真实路径设置字段映射，如果目标需要仅靠映射无法生成的结构就添加预发送 Code Glue 代码片段，然后在启用前执行 test_dispatch。", "The library already has a build like this one.": "库中已经有一个类似的构建。", "The publishing service had a temporary problem — nothing was published. Please try again.": "发布服务出现了临时问题——没有发布任何内容。请重试。", "The publishing service rejected this build.": "发布服务拒绝了这个构建。", "The publishing service returned an unexpected error (HTTP %d).": "发布服务返回了意外错误（HTTP %d）。", "The test delivery never reached the endpoint. Check the URL is correct and publicly reachable, then retry.": "测试投递从未到达端点。请检查 URL 是否正确且可公开访问，然后重试。", "The trial service is not responding right now. Please try again in a few minutes.": "试用服务目前没有响应。请几分钟后重试。", "The verification challenge could not be completed. Please try again.": "无法完成验证挑战。请重试。", "There is nothing to publish — this build has no webhooks.": "没有可发布的内容——这个构建没有任何 Webhook。", "These containers exist on your site too, but the keys inside them are yours and are not in our copy — do not map a field below one until you have your own capture:": "这些容器在你的站点上也存在，但其中的键是你的，不在我们的副本里——在你拥有自己的捕获之前，不要映射它们下面的任何字段：", "This API token cannot write Code Glue.": "此 API 令牌无法写入 Code Glue。", "This build did not pass our content check.": "这个构建没有通过我们的内容审核。", "This example comes from the WP Webhooks Payload Library, captured on our own test sites — the SHAPE is real, the VALUES are ours. Fire this event once on your site and your own capture replaces it automatically.": "此示例来自 WP Webhooks Payload Library，是在我们自己的测试站点上捕获的——结构是真实的，数值是我们的。在你的站点上触发该事件一次，你自己的捕获就会自动替换它。", "This is a WordPress Playground demo — it disappears when you close the tab, so builds cannot be published from it. Install Webhook Actions on your own site to publish.": "这是一个 WordPress Playground 演示——关闭标签页后它就会消失，因此无法从这里发布构建。请在你自己的站点上安装 Webhook Actions 以发布。", "This is the final payload on the wire — used for Transformed Conditions and URL/param templates.": "这是最终发送到线上的载荷——用于“转换后”条件和 URL/参数模板。", "This is the same rejection for the %d time running — the endpoint returned an identical response, so the last change did not touch what it objects to. Do not reformat that value again. Read the endpoint's own error text and ask what its API contract wants that the request does not carry: a request-level option or flag (many APIs need one before they will coerce or accept a value), a wrapper key the record has to sit inside, a field that must be a different type, or a value that must already exist on the far side. Name the specific API and what you believe it needs; if you are not sure, say so plainly and ask the user to confirm it from that API's documentation instead of guessing a third format.": "这已是连续第 %d 次相同的拒绝——端点返回了完全相同的响应，说明上一次更改没有触及它所反对的内容。不要再次重新格式化那个值。阅读端点自己的错误文本，问问它的 API 契约需要什么而请求中没有携带：请求级别的选项或标志（许多 API 需要它才会转换或接受某个值）、记录必须放入的包装键、必须是另一种类型的字段，或者对方必须已经存在的值。说出具体的 API 以及你认为它需要什么；如果不确定，就直说，并请用户从该 API 的文档中确认，而不是猜测第三种格式。", "This site defines DISALLOW_FILE_EDIT, which turns off editing code from the dashboard. That is a server-level choice and nothing in this plugin can override it — it has to be changed in wp-config.php. Snippets that are already assigned keep running.": "本站点定义了 DISALLOW_FILE_EDIT，它关闭了从仪表盘编辑代码的功能。这是服务器级别的选择，本插件中没有任何东西可以覆盖它——必须在 wp-config.php 中更改。已分配的代码片段继续运行。", "This site's address is not reachable from the internet, so a build published from it could not be verified or visited. Publish from the site that actually runs this integration.": "本站点的地址无法从互联网访问，因此从这里发布的构建无法被验证或访问。请从真正运行此集成的站点发布。", "This step maps a field we cannot see from here. The example payload came from the WP Webhooks Payload Library, and these paths sit inside a container whose contents are specific to your site:": "此步骤映射了一个我们从这里看不到的字段。示例载荷来自 WP Webhooks Payload Library，而这些路径位于一个内容特定于你站点的容器内：", "This test sent our reference payload, captured on %s, not data from this site: a 2xx proves the endpoint accepts the shape the mapping produces, not that the field VALUES are right. Tell the user, and ask them to fire the real event once if those values matter.": "此测试发送的是我们在 %s 捕获的参考载荷，而不是本站点的数据：2xx 证明端点接受映射生成的结构，并不证明字段值正确。请告知用户，如果这些值很重要，请他们触发一次真实事件。", "This test sent our reference payload, not data from this site — it proves the endpoint accepts the shape, not the values.": "此测试发送的是我们的参考载荷，而不是本站点的数据——它证明端点接受该结构，而不是这些值。", "This test sent our reference payload, not data from this site: a 2xx proves the endpoint accepts the shape the mapping produces, not that the field VALUES are right. Tell the user, and ask them to fire the real event once if those values matter.": "此测试发送的是我们的参考载荷，而不是本站点的数据：2xx 证明端点接受映射生成的结构，并不证明字段值正确。请告知用户，如果这些值很重要，请他们触发一次真实事件。", "This webhook is LIVE — the snippet's PHP will run on every real dispatch from now on. A snippet error never breaks the delivery (the payload is sent unmodified and the error is logged). Confirm to attach it.": "此 Webhook 已上线——从现在起代码片段的 PHP 会在每次真实发送时运行。代码片段出错绝不会中断投递（载荷按原样发送并记录错误）。确认以附加它。", "Too many builds published from this license — wait a moment and try again.": "此许可证发布的构建过多——请稍等片刻再试。", "Too many trial requests from this network. Please try again in an hour.": "来自此网络的试用请求过多。请一小时后重试。", "Unlimited conditions and AND / OR groups": "无限条件与 AND / OR 分组", "Update Webhook Actions Pro to %s. Code Glue, dynamic URL templates and retry settings now ship in the free Webhook Actions plugin — until Pro is updated it keeps running its own copies, so nothing breaks, but you are on the old versions of those features.": "请将 Webhook Actions Pro 更新到 %s。Code Glue、动态 URL 模板和重试设置现已随免费的 Webhook Actions 插件提供——在 Pro 更新之前它会继续运行自己的副本，所以不会出问题，但你用的是这些功能的旧版本。", "Update a Code Glue snippet": "更新 Code Glue 代码片段", "Update an existing Code Glue snippet's name, code or tags. If the snippet is already assigned and enabled on a webhook, the new code runs on the next dispatch — re-test with preview_snippet after editing.": "更新现有 Code Glue 代码片段的名称、代码或标签。如果该代码片段已分配并在某个 Webhook 上启用，新代码将在下一次发送时运行——编辑后请用 preview_snippet 重新测试。", "View": "查看", "WP Webhooks API Docs Library": "WP Webhooks API Docs Library", "WP Webhooks Payload Library": "WP Webhooks Payload Library", "Waiting for an example payload. Nothing has fired this trigger yet, so there are no real field names to map against.": "正在等待示例载荷。此触发器尚未被触发过，因此没有真实的字段名可供映射。", "When a Contact Form 7 form is submitted, send it as JSON to my n8n webhook": "当 Contact Form 7 表单提交时，把它作为 JSON 发送到我的 n8n Webhook", "When a new user registers, add them to my CRM and tag them by role": "当新用户注册时，把他们加入我的 CRM 并按角色打标签", "When a post is published, notify my Slack channel with the title and link": "当文章发布时，用标题和链接通知我的 Slack 频道", "Writing Code Glue needs the \"%s\" capability.": "写入 Code Glue 需要“%s”权限。", "You do not have permission.": "你没有权限。", "You have already published this build.": "你已经发布过这个构建。", "Your free trial is used up.": "你的免费试用已用完。", "Your free trial is used up. Connect your own provider below — Google AI Studio gives you a free Gemini key with no credit card — or get Pro credits.": "你的免费试用已用完。在下方连接你自己的服务商——Google AI Studio 提供免费的 Gemini 密钥，无需信用卡——或获取 Pro 积分。", "Your free trial starts with %s credits — nothing to set up, no card, no account.": "你的免费试用从 %s 个积分开始——无需设置，无需银行卡，无需账户。", "Your license does not allow publishing from this site.": "你的许可证不允许从本站点发布。", "Your previous builds, read-only. Connect a provider to continue building.": "你之前的构建，只读。连接一个服务商以继续构建。", "auto-researched": "自动调研", "backoff_base_delay must be between 1 and 86400 seconds.": "backoff_base_delay 必须介于 1 到 86400 秒之间。", "backoff_max_delay must be between 1 and 86400 seconds.": "backoff_max_delay 必须介于 1 到 86400 秒之间。", "backoff_strategy must be exponential, linear, or fixed.": "backoff_strategy 必须是 exponential、linear 或 fixed。", "global_max_attempts must be between 1 and 100.": "global_max_attempts 必须介于 1 到 100 之间。", "library": "库", "name and code are required.": "name 和 code 为必填。", "the step failed.": "该步骤失败。", "verified %s": "已验证 %s", "webhook_id, trigger, stage (pre|post) and snippet_id are required.": "webhook_id、trigger、stage（pre|post）和 snippet_id 为必填。", "💡 Staging and dev copies share their site's slot — %1$sstaging.%2$s, %1$sdev.%2$s, %1$sstage.%2$s, %1$stest.%2$s, %1$sqa.%2$s and similar subdomains of a licensed domain.": "💡 预发布和开发副本共享其站点的名额——%1$sstaging.%2$s、%1$sdev.%2$s、%1$sstage.%2$s、%1$stest.%2$s、%1$sqa.%2$s 以及已授权域名的类似子域名。" }