Duaer

Integrations

WeCom message receive trigger

Use the WeCom message receive trigger in Duaer to start a digital organization when a member messages or events your self-built app. You need a receive credential and a publicly reachable instance.

Set up receive

  1. Create a receive credential (Token, EncodingAESKey) as in WeCom credentials.
  2. Add the WeCom message receive trigger, select the credential, and set Path.
  3. After save, copy the Webhook URL into the app API receive URL in WeCom admin.
  4. When a member sends a message or an event fires, the digital organization starts from this trigger.

For passive replies, use WeCom passive reply trigger.

Questions

Why does WeCom fail URL verification?

Check that Token, EncodingAESKey, and Corp ID match the credential, and that WeCom can reach the Duaer public HTTPS URL.

In this section

Integrations

Built-in integrations in Duaer

Built-in triggers, actions, and credentials in Duaer. Triggers start a digital organization. Actions run a step after it has started.

Integrations

Risks 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.

Integrations

Troubleshoot 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.

Integrations

Make 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.

Integrations

Integrations in Duaer

Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.

Credentials

Built-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 nodes

Create 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.