Cross-platform trend research workflow
Cross-platform trend research workflow. Follow concrete contracts, examples and reviewable steps using Douyin, Weibo, X (Twitter).
Copy the agent prompt manually
Inputs, goal and deliverable
Record platform, region and observation time; compare ranks rather than adding incompatible scores.
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.
Step-by-step plan
| Step | Capability | Input | Output |
|---|---|---|---|
| 1 | douyin.trends.list | board | trend / items |
| 2 | weibo.trends.list | board | trend / items |
| 3 | x.trends.list | board | trend / items |
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.
Goal: Cross-platform trend research workflow Use only DataNavoAPI local demo/simulated mode. Planned capabilities: douyin.trends.list → weibo.trends.list → x.trends.list 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.
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 field | Meaning | Example |
|---|---|---|
| step1_board | 步骤 1 · board | hot_search |
| step2_board | 步骤 2 · board | hot_search |
| step3_board | 步骤 3 · board | trends |
| step3_region | 步骤 3 · region | US |
{
"schemaVersion": 1,
"templateId": "trends",
"runId": "00000000-0000-4000-8000-000000000001",
"inputs": {
"step1_board": "hot_search",
"step2_board": "hot_search",
"step3_board": "trends",
"step3_region": "US"
},
"maxTotalCredits": 6,
"estimatedCredits": 6,
"priceVersion": "test-credit-v1",
"steps": [
{
"id": "step-1",
"title": "抖音热榜",
"capability": "douyin.trends.list",
"params": {
"board": "hot_search"
},
"maxCredits": 2,
"idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-1"
},
{
"id": "step-2",
"title": "微博热搜榜",
"capability": "weibo.trends.list",
"params": {
"board": "hot_search"
},
"maxCredits": 2,
"idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-2"
},
{
"id": "step-3",
"title": "X 趋势榜",
"capability": "x.trends.list",
"params": {
"board": "trends",
"region": "US"
},
"maxCredits": 2,
"idempotencyKey": "wf:00000000-0000-4000-8000-000000000001:step-3"
}
]
}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.
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 ↗