Integrations
Start a Duaer workflow with ClickUp Trigger
In Duaer, ClickUp Trigger starts a workflow when ClickUp sends an event. It can listen for 27 events, such as folder.created, folder.deleted, folder.updated, and 24 more.
Start a Duaer workflow with ClickUp Trigger
- On the Duaer canvas, open the node panel, search for ClickUp Trigger, and add it as the first node.
- Under Authentication, choose Access Token or OAuth2, then pick or create the matching credential (ClickUp API or ClickUp OAuth2 API) in Credential to connect with.
- Pick the events that should start a run, for example folder.created or folder.deleted.
- Set Team Name or ID.
- Select Execute step, then cause a real event in ClickUp 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 ClickUp Trigger
folder.created, folder.deleted, folder.updated, goal.created, goal.deleted, goal.updated, keyResult.created, keyResult.deleted, keyResult.updated, list.created, list.deleted, list.updated, space.created, space.deleted, space.updated, task.assignee.updated, task.comment.posted, task.comment.updated, task.created, task.deleted, task.dueDate.updated, task.moved, task.status.updated, task.tag.updated, task.timeEstimate.updated, task.timeTracked.updated, task.updated.
ClickUp Trigger parameters in Duaer
- Team Name or ID: Choose from the list, or specify an ID using an expression.
Questions
Which ClickUp Trigger events can start a Duaer workflow?
Duaer's ClickUp Trigger can listen for 27 events, including folder.created, folder.deleted, folder.updated, goal.created, goal.deleted, and 22 more. Pick one or more on the node.
Does ClickUp Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the ClickUp Trigger webhook for production runs after you publish.
Which credential does ClickUp Trigger use in Duaer?
Duaer's ClickUp Trigger uses ClickUp API or ClickUp 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.