Short answer: Drop the "Perplexity → Async Chat (Deep Research)" 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 Deep Research, Sonar Reasoning Pro |
Question message | string | Required | Provide a comprehensive analysis of recent advances in quantum computing for cryptography |
System Prompt system_prompt | string | Optional | System Prompt |
{"model": "{{trigger.model}}","message": "Provide a comprehensive analysis of recent advances in quantum computing for cryptography","system_prompt": "{{trigger.system_prompt}}"}
{"id": "req_abc","model": "sonar-deep-research","status": "CREATED","created_at": 1700000000}
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.