Integrations
Start a Duaer workflow with Google Drive Trigger
In Duaer, Google Drive Trigger starts a workflow by checking Google Drive on a schedule you set. It can listen for 2 events, such as Changes to a Specific File and Changes Involving a Specific Folder.
Start a Duaer workflow with Google Drive Trigger
- On the Duaer canvas, open the node panel, search for Google Drive Trigger, and add it as the first node.
- Under Authentication, choose OAuth2 (recommended) or Service Account, then pick or create the matching credential (Google Service Account API or Google Drive OAuth2 API) in Credential to connect with.
- Pick the events that should start a run, for example Changes to a Specific File or Changes Involving a Specific Folder.
- Check Poll Times on the node.
- If needed, select Add Option for the optional settings listed below.
- Set Poll Times, select Execute step to fetch a sample, then publish the workflow so Duaer checks Google Drive on that schedule.
Events that start a Duaer workflow with Google Drive Trigger
Changes to a Specific File, Changes Involving a Specific Folder.
Google Drive Trigger parameters in Duaer
- Poll Times: Time at which polling should occur.
Google Drive Trigger options in Duaer
Under Add Option, Google Drive Trigger offers File Type.
Common issues
For errors and fixes, refer to Common issues with Google Drive Trigger in Duaer.
Questions
Which Google Drive Trigger events can start a Duaer workflow?
Duaer's Google Drive Trigger can listen for 2 events, including Changes to a Specific File and Changes Involving a Specific Folder. Pick one or more on the node.
Does Google Drive Trigger run before the Duaer workflow is published?
Only while you test with Execute step. After you publish, Duaer polls Google Drive on the Poll Times schedule.
Which credential does Google Drive Trigger use in Duaer?
Duaer's Google Drive Trigger uses Google Service Account API or Google Drive 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.