Integrations
Start a Duaer workflow with Github Trigger
In Duaer, Github Trigger starts a workflow when Github sends an event. It can listen for 42 events, such as Check Run, Check Suite, Commit Comment, and 39 more.
Start a Duaer workflow with Github Trigger
- On the Duaer canvas, open the node panel, search for Github Trigger, and add it as the first node.
- Under Authentication, choose Access Token, OAuth2, or GitHub App, then pick or create the matching credential (GitHub API, GitHub OAuth2 API, or GitHub App API) in Credential to connect with.
- Pick the events that should start a run, for example Check Run or Check Suite.
- Set Repository Owner and Repository Name.
- If needed, select Add Option for the optional settings listed below.
- Select Execute step, then cause a real event in Github 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 Github Trigger
Check Run, Check Suite, Commit Comment, Create, Delete, Deploy Key, Deployment, Deployment Status, Fork, Github App Authorization, Gollum, Installation, Installation Repositories, Issue Comment, Issues, Label, Marketplace Purchase, Member, Membership, Meta, Milestone, Org Block, Organization, Page Build, Project, Project Card, Project Column, Public, Pull Request, Pull Request Review, Pull Request Review Comment, Push, Release, Repository, Repository Import, Repository Vulnerability Alert, Security Advisory, Star, Status, Team, Team Add, Watch.
Github Trigger parameters in Duaer
- Repository Owner
- Repository Name
Github Trigger options in Duaer
Under Add Option, Github Trigger offers Insecure SSL.
Questions
Which Github Trigger events can start a Duaer workflow?
Duaer's Github Trigger can listen for 42 events, including Check Run, Check Suite, Commit Comment, Create, Delete, and 37 more. Pick one or more on the node.
Does Github Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the Github Trigger webhook for production runs after you publish.
Which credential does Github Trigger use in Duaer?
Duaer's Github Trigger uses GitHub API, GitHub OAuth2 API, or GitHub App 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.