AI 智能体

做出会替你干活的 AI 智能体。

十八个这周就能在 Lovable 里搭出来的智能体蓝图:客服、销售、调研、运营和语音。每个都附上它做什么、需要哪些零件、要粘的提示词,以及大家怎么靠它收钱。

2026

现在最热

这个月大家真正在搜的八个关于 AI 智能体的问题,每个都给一个直接的答案。点一个,筛下面的蓝图。

什么才算一个 AI 智能体

聊天机器人负责回答。智能体负责决定并行动。差别在三件事:它记着关于用户的上下文,它能调用真正改变点什么的工具,而且当动作不可逆时它会停下来问。下面每个蓝图都具备这三点。

怎么在 Lovable 里搭一个

  1. 01用一句话写清这份活:智能体服务谁、它决定什么、它绝不允许做什么。
  2. 02先把数据放进去。没有一张表可读、一张表可写的智能体,只是一个文本框。
  3. 03给它两三个窄的工具,别给十个。描述清楚的窄工具,胜过一个庞大的目录。
  4. 04凡是会发送、付款或删除的动作,前面都加一道审批。信任是一个功能,不是一个开关。
  5. 05先上最薄的版本,自己用一周,再加上你真正缺的那第四个工具。

AI 智能体

research agent screen with data tables, sources and scraped results,Lovable,盯着任何网站或市场的抓取智能体

一个智能体按计划从好几个服务收集价格、挂牌和招聘信息,把一团乱理成一张表,只有真出现变化时才提醒你。

你把一个来源描述一次:它的 URL、页面怎么分页、你需要哪些字段。智能体抓取页面,让模型把字段抽进一个固定 schema,按一个稳定的键去重,存一份快照,并写下对着上一次运行的差异。

零件
  • 表:sources、runs、items、item_changes
  • 带 fetch 加 HTML 转文本清理的 edge function
  • 用一个严格字段 schema 的结构化抽取
  • 每隔几小时的定时触发
  • 邮件或 webhook 告警,加 CSV 导出
怎么赚钱

把监控做成按来源订阅:二手商付钱看竞品价格,招聘方看职位流,代理公司看线索名单。间隔越短、要 API 访问的,收得越贵。

搭建耗时

一个周末

一步步
  1. 先看规则:读 robots.txt 和服务条款,只抓公开页面,网站有官方 API 时优先用它。
  2. 建 sources 表,带 url、分页模式、css 提示、字段列表、间隔和活跃标记。一行等于一个被监控的服务。
  3. 写一个 edge function fetch_source:它用一个正常的 user agent 加载 HTML,剥掉脚本和样式,把文本裁到装着挂牌的那部分。
  4. 把那段文本连同一个严格的 JSON schema(title、price、currency、url、published_at、raw_key)和温度零传给模型。绝不让模型编字段,缺失值必须是 null。
  5. 按 raw_key 去重:upsert 进 items,当一个被追踪的字段跟存下来的行不同时,往 item_changes 插一条带旧值和新值的记录。
  6. 加上带退避的重试、每个来源的速率限制,以及一个记录状态、条目数和错误文本的 runs 表,好让一个坏掉的选择器立刻可见。
  7. 按每个来源的间隔给这个函数排程,然后发一封摘要邮件或 webhook,只列出上次摘要以来 item_changes 里的行。
  8. 做界面:带健康徽章的来源列表、运行历史、一张可筛选的条目表、一个变更流和一个 CSV 导出按钮。
Build a scraping and monitoring agent.

Data: table "sources" (name, url, pagination_pattern, selector_hint, fields jsonb, interval_minutes, active). Table "runs" (source_id, status, items_found, error, started_at, finished_at). Table "items" (source_id, raw_key unique per source, title, price numeric, currency, url, published_at, payload jsonb, first_seen_at, last_seen_at). Table "item_changes" (item_id, field, old_value, new_value, created_at).

Server: an edge function that takes a source id, fetches the page with a normal user agent, strips scripts, styles and navigation, trims the text to the listing area, then asks the model to extract rows into a strict JSON schema with temperature zero and null for missing values. Upsert rows into items on raw_key and insert item_changes whenever a tracked field differs. Log every attempt into runs, retry twice with backoff on network errors and respect a per source rate limit. Follow pagination up to a configurable page limit.

Automation: a scheduled job that picks active sources whose interval has elapsed, runs them one by one, then sends a digest email or webhook containing only item_changes created since the previous digest.

UI: sources page with add and edit form, health badge from the last run, run history with error text, items table with search and filters, a change feed and a CSV export button.

Rules: only public pages, honour robots.txt, keep all keys and model calls on the server, enable row level security so each user sees only their own sources and items.
#scraping#monitoring#research
support agent workspace with a live chat inbox and ticket queue,Lovable,从你自己文档里作答的客服智能体

多数团队最先需要的那个智能体:它读你的帮助中心,凌晨三点也能回答客户,还不瞎编政策。

上传文档,把它们切成块,存嵌入,只用检索到的段落加一个来源链接来回答。什么都匹配不上时,智能体转给人工,而不是瞎猜。

零件
  • 带向量列的云数据库
  • 用于检索的 edge function
  • 流式聊天 UI
  • 未回答工单的升级表
怎么赚钱

按坐席卖给小型 SaaS 团队,或者按月收一笔固定费,托管一个客户的知识库。

搭建耗时

一个晚上

Build a documentation support agent.

Data: a table "documents" (title, url, content) and a table "chunks" (document_id, content, embedding vector). A table "escalations" (question, email, created_at, status).

Server: one edge function that embeds the user question, retrieves the six closest chunks, and streams an answer that uses only those chunks. Every answer must end with the source links it used. If similarity is below the threshold, return a short "I do not have this in the docs" answer and insert a row into escalations.

UI: a chat page with streaming responses, message history in the browser, source links rendered as chips under each answer, and an escalation form that appears when the agent cannot answer.

Enable row level security on all tables, keep model calls on the server, and show a clear error state when the request fails.
#rag#support#chat
sales agent dashboard with lead pipeline and outreach sequences,Lovable,给你落地页用的线索筛选智能体

把那个没人填的联系表单换成一个智能体,问四个问题,自己就把会议约好。

智能体做一场简短的结构化访谈,对着你的标准给线索打分,把结果写进数据库,并给销售发一份小结。

零件
  • 用一个小 schema 的结构化输出
  • 带分数和理由的 leads 表
  • 邮件通知
  • 可嵌入的组件
怎么赚钱

代理公司很愿意为这个付钱:每个客户站点一个组件,按月留存,再加一个自定义评分规则的增值项。

搭建耗时

一个周末

Build a lead qualification agent widget.

Behaviour: the agent asks at most five questions, one at a time, to learn company size, budget range, timeline and the problem being solved. It never asks two questions in one message and never asks for data it already has.

After the interview, produce a structured result with fields: score, tier, summary, next_step. Keep the schema flat and unconstrained, state the ranges in the prompt text, and clamp values in code.

Storage: insert into a "leads" table with contact details, transcript, score, tier and created_at. Send a notification email with the summary.

UI: a floating chat bubble on the landing page, mobile friendly, with a typing indicator and a final card showing the booked next step.
#sales#structured-output#widget
research agent screen with data tables, sources and scraped results,Lovable,会用工具、还把过程亮出来的调研智能体

一个多步智能体,会搜索、阅读、比较,交回一份带出处的简报,而不是一段自信的话。

定义三个工具:搜索、抓取页面、保存发现。让智能体循环,直到它有了足够的证据,然后在 UI 里渲染工具时间线,好让用户能审计每一步。

零件
  • 带步数上限的工具调用
  • 带来源 URL 的发现表
  • 工具活动时间线 UI
  • 导出到 markdown
怎么赚钱

按报告收费。市场调研、竞品拆解和尽调简报,都能当作一次性的交付物来卖。

搭建耗时

两个晚上

Build a research agent with tool calling.

Tools: web_search(query), fetch_page(url), save_finding(claim, source_url, confidence). Give each tool a narrow input schema and a short description.

Loop: allow at least fifty steps, stop when the agent has five saved findings or decides the question is answered. Never let the agent answer without at least two independent sources.

Output: a brief with a one paragraph answer, a bullet list of findings, and a sources section. Save the brief to a "reports" table.

UI: stream the answer, render every tool call as a timeline row with its input and a compact result, and add a copy button plus markdown export.
#tools#agent-loop#research
content agent editor with drafts, briefs and publishing calendar,Lovable,把一篇长文再利用的内容智能体

粘一篇文章,拿回邮件通讯、推文串、图文脚本和视频钩子,全用你自己的口吻。

存一个带规则和禁用短语的语气档案,然后在单独的调用里生成每一种格式,好让输出保持锋利、而不是糊成一团。

零件
  • 语气档案表
  • 每种格式并行生成
  • 可编辑的输出卡片
  • 一键复制
怎么赚钱

最容易卖的第一个产品:创作者按月付,代理公司按品牌工作区付。

搭建耗时

一个晚上

Build a content repurposing agent.

Input: a long article plus a saved voice profile (tone rules, favourite words, banned phrases, audience).

Generate four outputs in separate calls so each one is focused: a newsletter intro, a social thread of six posts, a carousel script of seven slides, and three video hooks.

Rules for every output: no em dashes, no emoji, no filler phrases like "in today's fast paced world", short sentences, concrete nouns.

UI: one input panel on the left, four result cards on the right, each editable inline with a copy button and a regenerate button that only regenerates that card.
#content#marketing#voice
operations agent console with automated workflows and status logs,Lovable,会起草回复的收件箱分拣智能体

每个创始人都被同样的四十封邮件淹没。这个智能体把它们分类、起草回复,发出去之前先问你。

把每条消息分类到一小组意图里,附上一个建议动作,任何离开这个应用的东西都要求明确批准。

零件
  • 用一个紧凑标签集的分类
  • 发送前的批准步骤
  • 回复模板
  • 每日摘要
怎么赚钱

卖给按小时计费的独立顾问和小代理公司,收件箱吃掉的每一小时他们都心疼。

搭建耗时

一个周末

Build an inbox triage agent.

For each incoming message, classify it as one of: sales, support, partnership, invoice, noise. Add urgency low, medium or high, and a one sentence reason.

Draft a reply for every message that is not noise, using saved templates as the base and matching the sender's language.

Any action that sends an email or changes external state must require approval in the UI first. Show the draft, the intent and the reason on an approval card with approve, edit and discard.

UI: a triage queue grouped by intent, keyboard shortcuts for approve and skip, and a daily digest view of what was handled.
#ops#approval#email
voice agent interface with call waveform and live transcript,Lovable,电话接单的语音智能体

诊所、美发店和工作坊到现在还漏掉一半来电。一个语音智能体第一声就接起来,直接把预约写进日历。

进来时语音转文字,中间一段简短的脚本化对话,出去时文字转语音,再加一条来电者能核对的确认消息。

零件
  • 语音转文字
  • 槽位填充对话
  • 对着日历的空档检查
  • 文字转语音和 SMS 确认
怎么赚钱

本地生意老板一句话就懂它的价值:漏一个电话就是丢一个客户。按每个门店按月定价。

搭建耗时

两个周末

Build a voice booking agent.

Flow: transcribe the caller audio, run a slot filling dialogue that collects service, preferred day, preferred time and phone number, confirm the details out loud, then create the booking.

Never invent availability. Check the bookings table first and offer the two closest free slots when the requested time is taken.

Confirm by reading the booking back and sending a text summary. Store the full transcript with the booking for review.

UI: an operator dashboard with today's calls, transcripts, created bookings and a flagged list of calls the agent could not finish.
#voice#booking#local-business
support agent workspace with a live chat inbox and ticket queue,Lovable,应用内的上手副驾
Intermediate

多数流失发生在头十分钟。一个知道用户卡在哪的智能体,比任何气泡引导都更能救激活。

把用户已完成的步骤和当前所在的界面喂给智能体,让它建议唯一的下一个动作,并给它一个真能执行那个动作的工具。

零件
  • 记录用户进度的事件表
  • 感知上下文的系统提示词
  • 带批准的动作工具
  • 激活指标视图
怎么赚钱

这是一个能卖进任何现成 SaaS 的增值项,而且激活提升好衡量、好开票。

搭建耗时

一个周末

Build an in-app onboarding copilot.

Context: pass the current route, the list of completed setup steps and the last three user events into the system prompt on every call.

Behaviour: always propose exactly one next action, explain in one sentence why it matters, and offer to do it. Never list five options.

Tools: create_project, invite_teammate, connect_data_source. Mark every tool as needing approval, and show the approval card inline in the chat.

UI: a slide-over panel available from every page, a progress checklist at the top, and an admin view showing where users get stuck most often.
#activation#saas#copilot
research agent screen with data tables, sources and scraped results,Lovable,对着你自己数据库的数据分析智能体

用大白话问一个问题,拿到一张图和它背后的查询。愿意把查询亮出来,正是让人信它的地方。

把 schema 给智能体,把它限制在只读视图上,让它写查询、在服务器端跑,再把结果渲染成一张图表,SQL 就显示在下面。

零件
  • 只读视图
  • 带 schema 上下文的查询生成
  • 服务器端执行
  • 图表渲染和保存的问题
怎么赚钱

垂直分析好卖:挑一个细分,把它的指标建模建好,收得比通用仪表盘工具更贵。

搭建耗时

两个晚上

Build a data analyst agent over a read-only schema.

Safety: expose only read-only views, reject anything that is not a select, cap rows returned, and run every query server side with a timeout.

Behaviour: the agent writes the query, explains in one sentence what it measures, then picks the chart type that fits the shape of the result.

UI: a question box with example questions, a chart, a collapsible SQL block, and a saved questions list that can be rerun with one click.

Handle empty results and query errors explicitly with a plain language message and a suggested fix.
#analytics#sql#charts
content agent editor with drafts, briefs and publishing calendar,Lovable,给值得排名的页面列大纲的 SEO 简报智能体

不是又一个洗稿工具。这个智能体读当前的搜索结果页,找出所有人都漏掉的,给一个配得上点击的页面写简报。

收集排名靠前的结果,抽出它们的标题,把共享的子话题聚簇,输出一份大纲,带上没人覆盖的角度加内部链接目标。

零件
  • 搜索和抓页面工具
  • 标题抽取
  • 缺口分析提示词
  • 简报导出
怎么赚钱

内容团队买的是简报,不是字数。按每月十份简报打包卖,写作留给客户。

搭建耗时

一个晚上

Build an SEO brief agent.

Input: a target keyword and the site the page will live on.

Steps: search the keyword, fetch the top eight results, extract their headings and word counts, cluster the shared subtopics, and list the questions none of them answer well.

Output a brief with: search intent in one line, target title and description, an H2 outline, entities to mention, three internal link targets from the given site, and the differentiating angle.

UI: a single input, a progress list of the steps as they run, and the finished brief in a copyable panel with markdown export.
#seo#content#tools
sales agent dashboard with lead pipeline and outreach sequences,Lovable,帮人挑东西的导购智能体

筛选器让人走开。一段关于他们到底需要什么的短对话,能把他们带到商品页、准备下单。

智能体问用途和约束,查实时目录,返回三个选项,配一份对权衡的朴素比较。

零件
  • 商品目录工具
  • 比较卡片 UI
  • 库存和价格感知
  • 交接到结账
怎么赚钱

按辅助成交额的百分比向商店收费,或按每千次对话收固定费。两种都能用数字讲清楚。

搭建耗时

一个周末

Build a shopping assistant agent for an online store.

Tools: search_products(query, filters), get_product(id), check_stock(id).

Behaviour: ask at most three questions about use case, budget and any dealbreaker, then recommend exactly three products. For each one, give the reason it fits and the honest downside. Never recommend an out of stock item.

UI: chat with product cards inline, each card showing image, price, stock status and an add to cart button. Keep the conversation on the product page as a side panel.

Log every conversation with the products shown and whether the visitor added to cart, so the store can measure assisted revenue.
#ecommerce#conversion#chat
operations agent console with automated workflows and status logs,Lovable,筛简历的招聘智能体
Intermediate

两百份申请,每个候选人一张诚实的评分表,还有每个决定到底为什么这么定的记录。

解析简历,对着你写的标准给它打分,通过邮件问两个澄清问题,把短名单连同推理一起交给一个人。

零件
  • 文档解析
  • 标准驱动的打分
  • 跟进邮件序列
  • 人工复核队列
怎么赚钱

招聘预算大,痛点有季节性但很尖锐。按每个在招岗位卖,而不是按坐席。

搭建耗时

一个周末

Build a recruiting screening agent.

Input: a job description with must have and nice to have criteria, plus uploaded resumes.

For each candidate produce: a score per criterion, an overall recommendation, the strongest evidence quoted from the resume, and the biggest open question.

Never infer age, gender, nationality or anything the criteria do not mention, and never reject a candidate automatically. The agent proposes, a human decides.

UI: a candidate table sorted by score with expandable scorecards, a compare view for the top five, and a one click email that asks the open question.
#hiring#documents#scoring
operations agent console with automated workflows and status logs,Lovable,说清钱花到哪去了的记账智能体

上传一张账单,拿到分类、趋势,和一句关于你忘了的那个订阅的、让你不太舒服的话。

解析文件,给交易归类,检测周期性扣费,让用户就自己的数字问跟进问题。

零件
  • CSV 上传和解析
  • 分类规则加模型兜底
  • 周期性扣费检测
  • 在解析好的数据上聊天
怎么赚钱

一个干净的免费增值产品:一张账单免费,历史记录、多账户和导出收费。

搭建耗时

一个晚上

Build a personal spending agent.

Input: a CSV bank statement uploaded by the user.

Processing: normalise dates and amounts, categorise every transaction using rules first and the model only for the leftovers, and detect recurring charges by matching merchant and cadence.

Output: a summary with total by category, month over month change, the three largest changes explained in one sentence each, and a list of subscriptions with their yearly cost.

UI: upload area, a category chart, a transactions table with inline category editing that retrains the rules, and a chat box for follow up questions about the uploaded data only.

Keep all data private to the signed in user with row level security.
#finance#csv#consumer
operations agent console with automated workflows and status logs,Lovable,接进你团队已经在付费的每个工具的 MCP 智能体

一个聊天窗口,读你的 CRM、你的文档和你的账单,然后把那件谁都不想开五个标签页去做的跨工具琐事做掉。

Model Context Protocol 把工具访问变成了一个标准。不用为每个服务写一个单独的集成,智能体拿到一份类型化工具的清单,在运行时挑对的那一个。你维护一个连接的注册表、一份按用户角色的权限映射,以及一份智能体做过的每一次调用的日志。

零件
  • 表:connections、tool_calls、approvals
  • 一个按用户角色列出可用工具的服务器函数
  • 带类型化参数和校验的工具路由器
  • 任何写动作之前的批准卡片
  • 带每次运行成本和延迟的调用日志
怎么赚钱

按坐席卖给同时活在五个工具里的团队,或者作为一次性的按月搭建,卖给一家想要自己内部副驾的公司。

搭建耗时

两个晚上

一步步
  1. 先定义工具契约:名称、描述、参数 schema,以及这个工具是读还是写。
  2. 把连接存在一个表里,带上归属用户、服务名和一个令牌引用,绝不在客户端放原始令牌。
  3. 写一个服务器函数,只返回当前角色可以用的那些工具。
  4. 让模型挑一个工具,对着 schema 校验参数,把任何不匹配的都拒掉。
  5. 对写类工具,在执行前渲染一张带确切载荷的批准卡片。
  6. 把每次调用连同时长、tokens 和结果记下来,然后在界面里显示一条运行时间线。
  7. 加一个空跑开关,好让一个新连接能在不碰真实数据的情况下被测试。
Build an internal tool-calling agent with a typed tool registry.

Data: connections (user_id, service, label, status), tools (name, description, args_schema, mode read or write), tool_calls (tool, args, result, duration_ms, cost), approvals (tool_call_id, status).

Server: one function that returns the tools allowed for the current user role, one function that executes a tool after validating arguments against args_schema, and one that records the call.

Agent loop: the model receives the allowed tool list, chooses at most one tool per turn, and must explain in one sentence why it chose it.

Safety: any tool marked write requires an approval card showing the exact arguments before it runs. Never execute a write tool without a recorded approval row.

UI: chat panel, a connections page with a test-run button, and a run timeline showing each tool call with duration and cost.

Protect every table with row level security so a user only ever sees their own connections and calls.
#mcp#tools#integrations#ops
sales agent dashboard with lead pipeline and outreach sequences,Lovable,趁你睡觉时调研、撰写并预约的 AI SDR

今年被搜得最多的智能体。它拿一份公司名单,找到该联系的理由,写一条不像模板的消息,再把回复放上你的日历。

价值不在于发更多邮件,在于那个调研的步骤。对每一家公司,智能体收集几个公开信号,对着你的理想客户画像给契合度打分,把标准线以下的都丢掉,然后才起草。每一份草稿都要等一个人点一下才发出去。

零件
  • 表:accounts、signals、drafts、sequences、replies
  • 带每个信号存下来源链接的调研步骤
  • 从零到一百、带一个可见理由的契合度分
  • 带编辑和一键批准的草稿队列
  • 把回复归为约见、延后或关闭的分类器
怎么赚钱

代理公司按约成的会议收费,软件团队按坐席收费。光是调研这一步就能卖:多数买家已经有了发送工具,缺的是写的理由。

搭建耗时

两个晚上

一步步
  1. 把理想客户画像写成模型真能核实的五个是或否的检查。
  2. 先从一个 CSV 导入客户。在这个循环跑起来之前就买一个数据供应商,是常见的错误。
  3. 对每一家客户,收集三个公开信号,并在每一个旁边存下来源 URL。
  4. 给契合度打分,并把为这个分数辩护的那句话记下来,好让一个人能跟它争辩。
  5. 起草一条恰好引用一个信号的消息。没有信号,就不发。
  6. 把草稿排进队列等批准,然后通过你自己的邮件服务商发,带一个每日上限。
  7. 给每一条回复分类,把正面的约进一个日历链接,两次没回音后把这家客户标为冷。
Build an AI SDR agent focused on research quality, not send volume.

Data: accounts (name, domain, size, notes), signals (account_id, type, text, source_url, found_at), fit_scores (account_id, score, reason), drafts (account_id, subject, body, status), replies (draft_id, category, next_step).

Pipeline: import accounts from CSV, research each account and store at least one signal with a source URL, score fit from 0 to 100 against a stored ideal customer profile, and draft only for accounts above the threshold.

Writing rule: every draft must quote exactly one stored signal and stay under 90 words. If no signal exists, skip the account and say why.

Human control: drafts land in an approval queue with inline editing. Nothing sends without an approved row and a per-day send cap.

Replies: classify each reply as interested, not now, or not a fit, and surface interested ones with a suggested meeting time.

UI: pipeline board, an account page showing signals with source links, and a draft queue with approve, edit and skip.
#sdr#outreach#sales#b2b
operations agent console with automated workflows and status logs,Lovable,一个智能体应用,替掉你那一堆自动化场景

十二个脆弱的场景、三个工具,没人记得哪个才是发发票的那个。把它们收进一个应用,每次运行都看得见,每次失败都有名字。

确定性的步骤保持确定性。模型只用在一个决定需要判断的地方:给这个分类、选收件人、决定它能不能等。别的一切都是排程上的普通代码,那正是让整件事既便宜、又以最好的方式无聊的原因。

零件
  • 表:workflows、steps、runs、run_steps、errors
  • 定时触发加一个手动运行按钮
  • 只用于分类和路由的模型步骤
  • 带退避的重试和一张死信表
  • 带每一步输入和输出的运行时间线
怎么赚钱

收一笔迁移费,再按月收钱把这些运行保持在绿灯。小公司愿意付钱,就为了不用再猜发票为什么没发出去。

搭建耗时

一个周末

一步步
  1. 列出你当前的场景,把每一步标成规则还是判断。大多数步骤是规则。
  2. 把工作流建模成行:一个工作流有有序的步骤,一次运行每执行一步就有一行。
  3. 把规则步骤实现成普通函数。抓取、转换、写入、发送。
  4. 在需要判断的地方加唯一一个模型步骤,并强制它从一个固定清单里返回一个值。
  5. 把每一步都裹进 try 和 catch,存下错误文本,用逐渐增长的延迟重试三次。
  6. 在你迁移第二个场景之前,先做出运行时间线界面。可见性就是全部意义。
  7. 一次迁移一个场景,并让旧的那个并行跑一周。
Build a workflow runner app where an AI step is used only for judgement.

Data: workflows (name, schedule, active), steps (workflow_id, position, kind rule or model, config), runs (workflow_id, started_at, status), run_steps (run_id, step_id, input, output, duration_ms, error), dead_letters (run_id, payload, reason).

Execution: run steps in order, store input and output of every step, retry a failed step three times with growing delay, then write it to dead_letters and stop the run.

Model steps: must return exactly one value from a fixed list defined in the step config, with a one sentence reason stored alongside.

UI: workflow list with last run status, a run timeline showing each step with duration and output, a manual run button, and a dead letter screen with a retry action.

Keep secrets in server functions only and protect every table with row level security.
#automation#workflow#ops#internal
voice agent interface with call waveform and live transcript,Lovable,接起你生意漏掉的那些来电的 AI 前台

一家诊所、一家美发店或一家修理铺,会漏掉三分之一的来电。每一个都是一个付费客户,只是刚拨了名单上的下一个号码。

智能体接起来,回答每个人都问的那五个问题,查日历,预约或记下留言,并给老板发一份小结。诀窍在那个兜底:当来电者听着不耐烦、或者问了脚本之外的东西,它就提出转人工、然后停止说话。

零件
  • 表:calls、transcripts、bookings、messages
  • 语音转文字、模型一轮、文字转语音
  • 营业时间和服务清单放在一张可编辑的表里
  • 带确认前占位的日历空档
  • 每通电话后通过邮件或即时通讯给老板的小结
怎么赚钱

本地生意按每个门店按月付,而话术自己就写好了:一周挽回一个预约,通常就够覆盖整笔费用。

搭建耗时

一个周末

一步步
  1. 写出这个生意实际会收到的那五个问题和确切的答案。这就是第一天的整个知识库。
  2. 先做文字版本,靠打字跟它对话。要是它在文字里就失败,语音只会把失败藏起来。
  3. 在进来时加语音转文字,并把语音转文字的置信度当作一道闸:低置信度就再问一遍,别猜。
  4. 把回答保持在两句以内。在电话里,长回答会被打断。
  5. 确认时占住一个日历空档,来电者挂了就释放它。
  6. 检测出沮丧和超出范围的问题,然后提出回电并记下号码。
  7. 给老板发一份带转写链接的通话小结,好让他们当天就能修脚本。
Build an AI receptionist for a local business.

Data: business_profile (hours, services, prices, address, five FAQ pairs), calls (started_at, caller, outcome), transcripts (call_id, role, text, confidence), bookings (service, slot, caller, status hold or confirmed), messages (call_id, text, callback_number).

Behaviour: greet, identify the request, answer only from business_profile, check available slots, place a hold, confirm, then release or confirm the hold.

Limits: answers stay under two sentences. If the model cannot answer from business_profile, or the caller sounds frustrated, offer a callback and store the number instead of guessing.

After the call: generate a summary with outcome, next step and a link to the transcript, and send it to the owner.

UI: a text chat to test the same logic without voice, a call log with transcripts, a bookings calendar, and an editable business profile page.
#voice#local#booking#receptionist
content agent editor with drafts, briefs and publishing calendar,Lovable,把一个想法变成一周短视频脚本的内容智能体

最快搭出来、也最好演示的智能体。粘一个念头,拿到七个钩子、七条脚本和文案,全用你自己的口吻。

语气就是产品。智能体存下十份你实际怎么写的样本,把模式抽取一次,应用到每一个脚本上。没有那一步,你得到的就是别人都在发的同一个通用钩子。

零件
  • 表:voice_samples、ideas、scripts、publish_queue
  • 一次性把风格抽取进一个存下来的语气档案
  • 带一遍打分、留下最好三个的钩子生成器
  • 脚本模板:钩子、张力、回报、行动号召
  • 带拖动重排期的日历视图
怎么赚钱

一次卖给一个创作者细分。一个听起来像买家的工具,胜过一个贵四倍的通用写手。

搭建耗时

一个晚上

Build a short video script agent that writes in the user's own voice.

Setup: the user pastes ten samples of their own writing. Extract a voice profile once with tone, sentence length, favourite structures and banned words, and store it.

Input: one idea in a sentence.

Output: seven hooks scored for curiosity and clarity, the best three expanded into 40 second scripts using hook, tension, payoff and call to action, plus a caption and five tags for each.

Rules: no generic openers, no words from the banned list, and every script must be readable out loud in under 45 seconds.

UI: idea input, a scored hook list, a script editor, and a weekly calendar where scripts can be dragged between days.
#content#video#creator#shorts
video ad production console with storyboard frames, timeline and voiceover track,Lovable,把产品说明变成一条现成广告片的广告视频智能体

进去一份说明,出来一条成片:脚本、分镜、配音、字幕,还有给不同投放位切的三个版本。大家低估的是分镜清单,不是渲染。

智能体分阶段工作,而不是一个巨大的提示词。它先写出报价和承诺,然后一份逐镜头的分镜表、每个镜头带时长,然后配着那些时长掐点的配音文本,然后它把片段拼起来、把字幕烧进去。每个阶段都被保存,所以你能重写一个场景、而不用重新生成整支广告。

零件
  • 表:briefs、scripts、shots、renders、variants
  • 阶段一:报价、受众痛点和单一承诺
  • 阶段二:带时长、机位备注和屏幕文字的分镜表
  • 给配音的文字转语音,加词级字幕
  • 在一个 edge function 里的渲染队列,带一个状态页
怎么赚钱

代理公司按成片收费。用半天拍摄的价钱卖一条广告的五个版本,对一个小品牌是很容易答应的事。

搭建耗时

一个周末

一步步
  1. 只用五个字段收集简报:产品、买家、痛点、承诺、佐证。字段越多,广告越差。
  2. 为同一个产品生成三个角度,让用户在别的什么跑起来之前先挑一个。
  3. 把分镜表做成行、不是散文:镜号、秒数、屏幕上是什么、说了什么。
  4. 把总长封在投放位的长度上:15、30 或 60 秒,让模型删镜头来凑。
  5. 对着时长写配音,然后按大约每秒 2.5 个词检查朗读速度。
  6. 为每个镜头生成或匹配库存素材,把片段 URL 存在这个镜头的行上。
  7. 拼装、烧字幕,从同一条时间线导出 9:16、1:1 和 16:9。
  8. 保存每一个版本,好让客户能把第一版和第三版对比。
Build an ad video agent that turns a product brief into a finished commercial.

Data: briefs (product, buyer, pain, promise, proof), scripts (brief_id, angle, status), shots (script_id, index, seconds, visual, voice_over, on_screen_text, clip_url), renders (script_id, aspect, url, status).

Flow, one stage at a time and each stage saved before the next:
1. From the brief, propose three angles with a one line promise each. Wait for the user to pick one.
2. Build a shot list as rows with index, seconds, visual, on screen text. Total duration must equal the chosen placement length of 15, 30 or 60 seconds.
3. Write the voice over per shot, sized to that shot's seconds at about 2.5 words per second.
4. Attach a clip to each shot, then queue renders for 9:16, 1:1 and 16:9 with burned in word level subtitles.

Rules: one promise per ad, the hook lands in the first two seconds, no claim that is not backed by the proof field, and never exceed the placement length.

UI: brief form, angle picker, an editable shot table where changing seconds re-times only that shot's voice over, a render queue with status, and a version list to compare cuts side by side.
#content#video#ads#marketing#ugc
creator workspace with phone on a ring light and UGC script variants on screen,Lovable,写达人脚本、测钩子的 UGC 广告智能体

付费社媒不是败在剪辑,是败在头两秒。这个智能体每个产品产出二十个钩子,留下扛过打分的那些,再变成能直接开拍的达人简报。

输出不是一个脚本,是一套拍摄套件:钩子句、创作者在每一拍里拿什么做什么、要念出来的那句话、说明文字和缩略图画面。每个变体都带一个追踪名,好让广告结果能被粘回来,智能体就学会哪个钩子家族赢。

零件
  • 表:products、hooks、variants、results
  • 横跨六个被验证过家族的钩子生成器
  • 对好奇心、清晰度和宣称风险的一遍打分
  • 带节拍和道具的创作者简报模板
  • 通过 CSV 导入结果来给钩子家族排名
怎么赚钱

品牌买的是创意量,不是单条广告。一个月三十条测过的脚本打包,比一个代理公司的一个概念还便宜。

搭建耗时

一个晚上

一步步
  1. 把六个钩子家族定义一次:问题、对比、错误、结果、演示、故事。按家族要钩子,别成批要。
  2. 给每个钩子在好奇心和清晰度上打一到五分,并标出产品证明不了的任何宣称。
  3. 留下最好的八个,其余丢掉,绝不给用户看二十条生的句子。
  4. 把每个活下来的钩子展开成四拍、每拍五秒:钩子、问题、演示、行动号召。
  5. 加上物理层:画面里有什么、手做什么、产品在哪儿出现。
  6. 为每个变体生成一段说明文字和三个标签,加一个像 product-family-number 的追踪名。
  7. 让用户把广告结果作为 CSV 粘回来,带每个追踪名的花费、观看和点击。
  8. 显示对这个产品哪个钩子家族赢,并让下一批偏向它。
Build a UGC ad script agent that produces shot ready creator briefs and learns from results.

Data: products (name, promise, proof, audience), hooks (product_id, family, line, curiosity_score, clarity_score, claim_risk), variants (hook_id, beats json, caption, tags, tracking_name), results (tracking_name, spend, views, clicks, conversions).

Hook families: problem, contrast, mistake, result, demo, story. Generate three hooks per family, score each from one to five on curiosity and clarity, flag any claim not supported by the proof field, keep the top eight and discard the rest.

For each surviving hook produce four beats of five seconds: hook, problem, demo, call to action. Every beat states what is in frame, what the creator does with their hands, and the exact line spoken. Add a caption, three tags and a tracking name of the form product-family-number.

Results loop: accept a CSV of results by tracking name, compute cost per click per hook family, and weight the next generation toward the winning families.

UI: product form, a scored hook table, a beat editor, a print view of the creator brief, and a results dashboard by hook family.
#content#video#ads#ugc#creator#hooks
product demo editor with screen-recording scenes, captions and narration waveform,Lovable,把一段录屏变成精致产品片的演示视频智能体

录一段乱糟糟的五分钟走查,拿回一条 60 秒的演示,配好文字旁白、每个要紧点击都放大、字幕也干净。毁掉演示的是冷场,而这正是智能体去掉的东西。

转写只是入口。智能体把转写映射到录像里的那些时刻,去掉静音和重复的尝试,把啰嗦重写成简短的、以好处为主的旁白,然后在发生点击的时间戳上放置放大和高亮标记。用户编辑的是一条片段的时间线,不是一个视频文件。

零件
  • 表:recordings、segments、narration、exports
  • 带词级时间戳的语音转文字
  • 静音和填充检测,去掉冷场
  • 绑到点击时间戳上的放大和高亮标记
  • 给落地页、应用商店和社交的导出预设
怎么赚钱

每个 SaaS 都需要一个演示,又都讨厌录。按成片收费,或按月卖给每周都上新功能的团队。

搭建耗时

一个周末

一步步
  1. 接受原始录像的上传并把它存下来,绝不在浏览器里处理。
  2. 带词级时间戳转写,把每个词存成一行。
  3. 剪掉任何超过 0.6 秒的静音,以及任何重复的句首。
  4. 把剩下的按任务切成片段,产品做的每一件事一个片段。
  5. 把每个片段重写成一句好处:观众得到什么,而不是按了哪个按钮。
  6. 按重要性给片段排名,只留够凑目标长度的那些。
  7. 在每个点击时间戳上放一个放大标记,在变化的区域上放一个高亮。
  8. 带字幕渲染,然后从同一份剪辑导出给落地页的 16:9 和给社交的 9:16。
Build a product demo video agent that turns a raw screen recording into a short polished demo.

Data: recordings (file_url, duration, target_length), words (recording_id, text, start, end), segments (recording_id, start, end, task, narration, importance), markers (segment_id, timestamp, type zoom or highlight, region), exports (recording_id, aspect, url, status).

Pipeline: transcribe with word level timestamps, remove silences longer than 0.6 seconds and repeated sentence starts, group the rest into segments where one segment equals one task the product performs, rewrite each segment into a single benefit sentence, score segments by importance and keep only enough to fit the target length.

Then place a zoom marker at every click timestamp and a highlight on the region that changed, render with word level subtitles and export 16:9 and 9:16 from the same edit.

Rules: narration describes the outcome, not the interface. Never say click here. Total length must not exceed the target. Keep every cut reversible by storing segments rather than rewriting the source file.

UI: upload page, a segment timeline where segments can be reordered, muted or restored, a narration editor with live duration, a marker overlay on the preview, and an export panel per aspect ratio.
#content#video#demo#saas#onboarding

关于搭建智能体的问题

Lovable 真能搭出一个 AI 智能体,还是只能搭界面?
都能。聊天界面、数据库、调用模型的服务端函数和工具逻辑都在同一个项目里,所以智能体端到端地跑,不用另开一个后端。
我需要一个 AI 服务商的 API 密钥吗?
不需要。模型调用走内建的 AI 网关,所以你能在决定服务商或付费套餐之前,先把智能体搭起来、测起来。
我怎么让智能体别瞎编?
给它接地。回答之前先检索真实的段落,每条说法都要求给出处,也允许智能体说自己不知道。一句带转接的“不知道”,胜过一个自信的编造。
让智能体采取行动,最安全的方式是什么?
审批步骤。任何会发邮件、扣款或删数据的工具,都该先渲染一张审批卡片,上面写清用户即将确认的确切内容。
我该先搭哪个智能体?
那个能把一件事从你自己一周里拿掉的。基于文档的客服和内容再利用是最快的两个起点,各花一个晚上左右。

接着逛

挑一个智能体,今晚就搭出来

免费版每天给五个额度,不用卡。这足够把本页任何一个蓝图的第一版跑起来。

打开 Lovable 搭起来 →