Duaer

Integrations

Use Phantombuster in Duaer

In Duaer, the Phantombuster node works with Phantombuster from a workflow. It offers 6 operations on Agent.

Add Phantombuster to a Duaer workflow

  1. On the Duaer canvas, open the node panel, search for Phantombuster, and connect it after the previous node.
  2. In Credential to connect with, pick or create a Phantombuster API credential. Refer to Phantombuster credentials.
  3. Pick a Resource and an Operation. For example, to get an agent by ID, pick Agent and Get.
  4. Fill the fields that operation shows, such as Agent ID.
  5. Select Execute step and check the output.

Phantombuster operations in Duaer

The Phantombuster node in Duaer offers these operations, grouped by resource:

  • Agent › Delete: Delete an agent by ID.
  • Agent › Get: Get an agent by ID.
  • Agent › Get Many: Get many agents of the current user's organization.
  • Agent › Get Output: Get the output of the most recent container of an agent.
  • Agent › Launch: Add an agent to the launch queue.
  • Agent › Launch Sync: Launch an agent and stream results.

Use Phantombuster as a tool for an AI Agent in Duaer

In the Tool input of an AI Agent, search for Phantombuster 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 Phantombuster endpoint the node does not cover

Add an HTTP Request node, set Authentication to Predefined Credential Type, pick Phantombuster 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 Phantombuster operations does Duaer support?

Duaer's Phantombuster node offers 6 operations on Agent. For example, Agent has Delete, Get, Get Many, Get Output, Launch, and Launch Sync.

Which credential does Phantombuster use in Duaer?

Duaer's Phantombuster uses a Phantombuster API credential. The secret stays in the credential, not in node parameters.

In this section