Integrations
Use GitLab in Duaer
In Duaer, the GitLab node works with GitLab from a workflow. It offers 18 operations on File, Issue, Release, Repository, and User.
Add GitLab to a Duaer workflow
- On the Duaer canvas, open the node panel, search for GitLab, and connect it after the previous node.
- Under Authentication, choose Access Token or OAuth2, then pick or create the matching credential (GitLab API or GitLab OAuth2 API) in Credential to connect with. Refer to GitLab credentials.
- Pick a Resource and an Operation. For example, to create a new issue, pick Issue and Create.
- Fill the fields that operation shows, such as Title, Body, and Due Date.
- Select Execute step and check the output.
GitLab operations in Duaer
The GitLab node in Duaer offers these operations, grouped by resource:
- File: Create, Delete, Edit, Get, List
- Issue: Create, Create Comment, Edit, Get, Lock
- Release: Create, Delete, Get, Get Many, Update
- Repository: Get, Get Issues
- User: Get Repositories
Use GitLab as a tool for an AI Agent in Duaer
In the Tool input of an AI Agent, search for GitLab 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 GitLab endpoint the node does not cover
Add an HTTP Request node, set Authentication to Predefined Credential Type, pick GitLab 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 GitLab operations does Duaer support?
Duaer's GitLab node offers 18 operations on File, Issue, Release, Repository, and User. For example, File has Create, Delete, Edit, Get, and List.
Which credential does GitLab use in Duaer?
Duaer's GitLab uses GitLab API or GitLab OAuth2 API, depending on the method you choose under Authentication.
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.