Integrations
Start a Duaer workflow with GitLab Trigger
In Duaer, GitLab Trigger starts a workflow when GitLab sends an event. It can listen for 12 events, such as Comment, Confidential Issues, Confidential Comments, and 9 more.
Start a Duaer workflow with GitLab Trigger
- On the Duaer canvas, open the node panel, search for GitLab Trigger, and add it as the first 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.
- Pick the events that should start a run, for example Comment or Confidential Issues.
- Set Repository Owner and Repository Name.
- Select Execute step, then cause a real event in GitLab to capture a sample. Publish the workflow so Duaer registers the webhook and starts a run for every event.
Events that start a Duaer workflow with GitLab Trigger
- Comment: Triggered when a new comment is made on commits, merge requests, issues, and code snippets.
- Confidential Issues: Triggered on confidential issues' events.
- Confidential Comments: Triggered when a confidential comment is made.
- Deployments: Triggered when a deployment starts/succeeds/fails/is cancelled.
- Issue: Triggered when a new issue is created or an existing issue was updated/closed/reopened.
- Job: Triggered on status change of a job.
- Merge Request: Triggered when a new merge request is created, an existing merge request was updated/merged/closed or a commit is added in the source branch.
- Pipeline: Triggered on status change of Pipeline.
- Push: Triggered when you push to the repository except when pushing tags.
- Release: Release events are triggered when a release is created or updated.
- Tag: Triggered when you create (or delete) tags to the repository.
- Wiki Page: Triggered when a wiki page is created, updated or deleted.
GitLab Trigger parameters in Duaer
- Repository Owner: Owner of the repository.
- Repository Name: The name of the repository.
Questions
Which GitLab Trigger events can start a Duaer workflow?
Duaer's GitLab Trigger can listen for 12 events, including Comment, Confidential Issues, Confidential Comments, Deployments, Issue, and 7 more. Pick one or more on the node.
Does GitLab Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the GitLab Trigger webhook for production runs after you publish.
Which credential does GitLab Trigger use in Duaer?
Duaer's GitLab Trigger 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.