Integrations
Use Perplexity in Duaer
In Duaer, the Perplexity node works with Perplexity from a workflow. It offers 4 operations on Agent, Embedding, and Search.
Add Perplexity to a Duaer workflow
- On the Duaer canvas, open the node panel, search for Perplexity, and connect it after the previous node.
- In Credential to connect with, pick or create a Perplexity API credential. Refer to Perplexity credentials.
- Pick a Resource and an Operation. For example, to get raw, ranked web search results with filtering and content extraction, pick Search and Search.
- Fill the fields that operation shows, such as Query and Simplify Output.
- Select Execute step and check the output.
Perplexity operations in Duaer
The Perplexity node in Duaer offers these operations, grouped by resource:
- Agent › Create Response: Create a response using the Agent API with third-party models, presets, and tools.
- Embedding › Create Embedding: Generate vector embeddings for text input.
- Embedding › Create Contextualized Embedding: Generate context-aware embeddings for document chunks.
- Search › Search: Get raw, ranked web search results with filtering and content extraction.
Use Perplexity as a tool for an AI Agent in Duaer
In the Tool input of an AI Agent, search for Perplexity and add it. The agent decides when to call it. For a field the model should fill, select the sparkle next to it or write $fromAI('name', 'what to put here'); fixed values stay as you set them.
Call a Perplexity endpoint the node does not cover
Add an HTTP Request node, set Authentication to Predefined Credential Type, pick Perplexity API as the credential type, and select the same credential. Duaer signs the request with it, so you only fill in the method and URL. Refer to custom operations.
Questions
Which Perplexity operations does Duaer support?
Duaer's Perplexity node offers 4 operations on Agent, Embedding, and Search. For example, Agent has Create Response.
Which credential does Perplexity use in Duaer?
Duaer's Perplexity uses a Perplexity API credential. The secret stays in the credential, not in node parameters.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.