Short answer: Drop the "Perplexity → Chat Completion" 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: Sonar (default, with search), Sonar Pro (deeper search), Sonar Reasoning (complex queries) |
Message message | string | Required | Message. Example: What are the latest developments in quantum computing? |
System Prompt system_prompt | string | Optional | System Prompt. Example: Be precise and cite your sources. |
Temperature temperature | string | Optional | Temperature. Example: 0.2 |
{"model": "{{trigger.model}}","message": "e.g. What are the latest developments in quantum computing?","system_prompt": "e.g. Be precise and cite your sources.","temperature": "e.g. 0.2"}
{"id": "abc123","model": "sonar","choices": [{"message": {"role": "assistant","content": "According to recent research..."},"finish_reason": "stop"}],"citations": ["https://example.com/article"]}
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.