Integrations
Use Google Workspace Admin in Duaer
In Duaer, the Google Workspace Admin node works with Google Workspace Admin from a workflow. It offers 16 operations on ChromeOS Device, Group, and User.
Add Google Workspace Admin to a Duaer workflow
- On the Duaer canvas, open the node panel, search for Google Workspace Admin, and connect it after the previous node.
- In Credential to connect with, pick or create a Google Workspace Admin OAuth2 API credential. Refer to Google Workspace Admin credentials.
- Pick a Resource and an Operation. For example, to create a group, pick Group and Create.
- Fill the fields that operation shows, such as Group Email and Group Name.
- Select Execute step and check the output.
Google Workspace Admin operations in Duaer
The Google Workspace Admin node in Duaer offers these operations, grouped by resource:
- ChromeOS Device: Get, Get Many, Update, Change Status
- Group: Create, Delete, Get, Get Many, Update
- User: Add to Group, Create, Delete, Get, Get Many, Remove From Group, Update
Use Google Workspace Admin as a tool for an AI Agent in Duaer
In the Tool input of an AI Agent, search for Google Workspace Admin 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 Google Workspace Admin endpoint the node does not cover
Add an HTTP Request node, set Authentication to Predefined Credential Type, pick Google Workspace Admin OAuth2 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 Google Workspace Admin operations does Duaer support?
Duaer's Google Workspace Admin node offers 16 operations on ChromeOS Device, Group, and User. For example, ChromeOS Device has Get, Get Many, Update, and Change Status.
Which credential does Google Workspace Admin use in Duaer?
Duaer's Google Workspace Admin uses a Google Workspace Admin OAuth2 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.