Перейти к навигации

Look up social sources in WorkBuddy, Doubao Work or QwenWork

Add BeatAPI as a custom connector in WorkBuddy, Doubao Work or QwenWork with the URL https://beatapi.io/mcp and a Bearer header. The client then gets three tools, capabilities_search, capabilities_inspect and capabilities_run, which look up WeChat articles, Xiaohongshu notes or Douyin videos in a conversation. For a weekly brief, fetch one page of articles from a verified WeChat account and send a teammate the articles worth opening, each with the original title and link.

Add the connector in your client

All three clients use the same three values: server name beatapi, URL https://beatapi.io/mcp, and header Authorization: Bearer <BEATAPI_API_KEY>. Enter the real key in the client’s credentials or custom header form. When starting a task, ask for the connector by name.

ClientAdd and enable the connector
WorkBuddyOpen Experts, Skills and Connectors → Connectors → Custom Connector. Choose Streamable HTTP and enter the URL and header. Use streamableHttp in the MCP JSON editor. If tools are absent, check the Security Center toggle for custom MCP services.
Doubao WorkIn the desktop Skills, Connectors and Partners area, add a custom plugin or connector. Select HTTP, enter the authorization under custom headers, then save and enable it. Start a new task.
QwenWorkOpen Extensions → Connectors → Add → Manual configuration and select Streamable HTTP. Enable the service under Installed, then start a new conversation. For JSON import, use streamable-http as the type.

If your organization manages extensions, check that the client allows custom connections and that the beatapi service is enabled. Then check the tool list for capabilities_search, capabilities_inspect and capabilities_run. Some clients prefix tool names with the server name.

WorkBuddy connectors · WorkBuddy transport types · Doubao Work plugins · QwenWork connectors

Fetch one page before reading articles

Use the beatapi connector to find the WeChat account article-list action. Report the required inputs and price. Once I give you a verified account identifier, fetch only page one. Return titles, original links, scope and request ID. Wait for my selection before reading an article body.

Pass the verified account username to data:wechat_mp.v2.fetch_account_articles with raw:false for the simplified list. Before selecting articles, check that the returned links belong to the target account. For an empty list, record the request ID and the scope. For a tool failure, check the connection or the inputs, and record the failure separately from an empty list.

If the client shows tool arguments, compare the arguments with the example below. Check the reference against the capabilities_inspect result, and replace the account with a confirmed identifier. The example fetches page one only.

{
"reference": "data:wechat_mp.v2.fetch_account_articles",
"operation": "start",
"input": {"username": "<verified_username>", "item_show_type": 0, "raw": false},
"view": "preview"
}

The same client also handles Xiaohongshu topic discovery and Douyin video research. For both, save the platform, the object ID, the source link and the excerpt scope first, then fetch comments, details and extra pages only as needed. See BeatAPI pricing.

What can you hand over in a weekly brief?

For example, a competitor’s article list includes “Autumn product launch,” and your teammate needs the release date.

  1. Share the original title, the source link, the list summary and the request ID as a lead.
  2. Read the selected article to verify the date.
  3. If page one only shows “Event recap” and does not reach the dates you need, write “First page checked. Target dates still pending,” then decide whether to request another page.

With a verified account identifier, one list page plus three selected article bodies takes four data requests. With only the account’s display name, verify the account identifier first, and add every account lookup or extra page you actually request to the count.

Confirm the reply used BeatAPI

Open the task’s tool log and find the BeatAPI lookup, the request ID and the returned records; an enabled connector alone does not show that a lookup ran. For a 401, check the endpoint, the space after Bearer and whether the key is active. If the tools still do not appear in a new task, check the client’s toggle and permissions. A client without a compatible connector can still summarize saved sources, labelled with their retrieval dates.

For example, the assistant says “The product launches next week,” but the tool log only shows a list summary. Ask the assistant which words in the summary support the claim. If the summary says only “launching this autumn,” record “Autumn launch planned. Exact date pending.” If the date matters, fetch the selected article, then leave the article URL and the request ID for the next weekly brief.

WeChat article discovery · Other client setup options