Integrations
Start a Duaer workflow with Figma Trigger (Beta)
In Duaer, Figma Trigger (Beta) starts a workflow when Figma Trigger (Beta) sends an event. It can listen for 5 events, such as File Commented, File Deleted, File Updated, and 2 more.
Start a Duaer workflow with Figma Trigger (Beta)
- On the Duaer canvas, open the node panel, search for Figma Trigger (Beta), and add it as the first node.
- Under Authentication, choose Access Token or OAuth2, then pick or create the matching credential (Figma API or Figma OAuth2 API) in Credential to connect with.
- Pick the events that should start a run, for example File Commented or File Deleted.
- Set Team ID.
- Select Execute step, then cause a real event in Figma Trigger (Beta) 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 Figma Trigger (Beta)
- File Commented: Triggers when someone comments on a file.
- File Deleted: Triggers whenever a file has been deleted.
- File Updated: Triggers whenever a file saves or is deleted.
- File Version Updated: Triggers whenever a named version is created in the version history of a file.
- Library Publish: Triggers whenever a library file is published.
Figma Trigger (Beta) parameters in Duaer
- Team ID: Trigger will monitor this Figma Team for changes.
Questions
Which Figma Trigger (Beta) events can start a Duaer workflow?
Duaer's Figma Trigger (Beta) can listen for 5 events, including File Commented, File Deleted, File Updated, File Version Updated, and Library Publish. Pick one or more on the node.
Does Figma Trigger (Beta) run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the Figma Trigger (Beta) webhook for production runs after you publish.
Which credential does Figma Trigger (Beta) use in Duaer?
Duaer's Figma Trigger (Beta) uses Figma API or Figma 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.