DataNavoAPI / SKILLS

Brand mention research workflow

Brand mention research workflow. Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote), Weibo, X (Twitter).

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

Inputs, goal and deliverable

Separate ambiguous names, quotations and explicit brand mentions.

Inputs consist of explicit platforms, keywords or object identifiers. Preserve the samples, request IDs, classifications and unresolved questions in the deliverable. The task does not schedule itself or paginate indefinitely.

02

Step-by-step plan

StepCapabilityInputOutput
1xiaohongshu.notes.searchquery, sortpost / items
2weibo.posts.searchquerypost / items
3x.posts.searchquery, sortpost / items
03

Reusable task prompt

Ask the client to present a plan before you confirm each execution. This prompt bounds the sample; it does not call an external service for you.

text
Goal: Brand mention research workflow
Use only DataNavoAPI local demo/simulated mode.
Planned capabilities: xiaohongshu.notes.search → weibo.posts.search → x.posts.search
Describe inputs and output fields and propose a bounded request count first.
Execute explicitly, retaining request IDs. Stop on failures or unknown outcomes.
Return a table, missing fields and sampling limits; never present fictional samples as market facts.
04

Plan, run and export

This bounded example has 3 steps. Successful customer simulation costs 6 TEST; anonymous demo costs zero. Provide each required identifier before generating a fixed plan; search results do not expand the request list automatically.

Use data.items[].id for the matching platform and object detail, account IDs for account content and comment IDs for replies. Check object types before reusing an ID. Fixture IDs do not establish a real relationship. The workbench exports per-step JSON and source-labelled CSV.

Workbench fieldMeaningExample
query研究关键词户外咖啡
json
{
  "schemaVersion": 1,
  "templateId": "mentions",
  "runId": "00000000-0000-4000-8000-000000000001",
  "inputs": {
    "query": "户外咖啡"
  },
  "maxTotalCredits": 6,
  "estimatedCredits": 6,
  "priceVersion": "test-credit-v1",
  "steps": [
    {
      "id": "step-1",
      "title": "搜索小红书笔记",
      "capability": "xiaohongshu.notes.search",
      "params": {
        "query": "户外咖啡",
        "sort": "relevance"
      },
      "maxCredits": 2,
      "idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-1"
    },
    {
      "id": "step-2",
      "title": "微博实时搜索",
      "capability": "weibo.posts.search",
      "params": {
        "query": "户外咖啡"
      },
      "maxCredits": 2,
      "idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-2"
    },
    {
      "id": "step-3",
      "title": "搜索 X 公开帖子",
      "capability": "x.posts.search",
      "params": {
        "query": "户外咖啡",
        "sort": "latest"
      },
      "maxCredits": 2,
      "idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-3"
    }
  ]
}
05

Review and stop conditions

  • Each conclusion links back to a sample and request ID.
  • Pagination stops at the agreed bound.
  • Missing fields remain missing rather than being invented by the model.
  • External writes, scheduled monitoring and automatic top-ups are not enabled by this workflow.
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗