Short answer: Drop the "xAI → Grok Live Search" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Model model | options | Required | Model. Options: Grok 4, Grok 3 |
Question message | string | Required | Question (required) |
Search Mode search_mode | options | Optional | Search Mode. Options: Auto, On (always search), Off |
Max Search Results max_search_results | string | Optional | Max Search Results |
Source Types sources | array | Optional | Array of {type: 'web'|'x'|'news'|'rss'} objects |
{"model": "{{trigger.model}}","message": "{{trigger.message}}","search_mode": "{{trigger.search_mode}}","max_search_results": "{{trigger.max_search_results}}","sources": "{{trigger.sources}}"}
{"id": "chatcmpl_abc","usage": {"total_tokens": 300,"prompt_tokens": 100,"completion_tokens": 200},"choices": [{"message": {"content": "..."},"finish_reason": "stop"}],"citations": ["https://example.com"]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.