Overview

This node acts as a trigger for DingTalk streaming events, specifically listening for robot and card message topics. It connects to the DingTalk streaming API using provided credentials and emits incoming messages as JSON objects. It is useful for automating workflows based on real-time DingTalk events, such as processing robot messages or card interactions.

Use Case Examples

1. Automatically respond to robot messages in DingTalk by triggering workflows when such messages arrive.
2. Capture and process card message events from DingTalk to update external systems or notify users.

Properties

Name	Meaning
isAutoResponse	Determines whether the node should automatically send a response to DingTalk to prevent server-side retries of the same event.

Output

JSON

• abc - A fixed string indicating the type of message ('baby!' for robot messages, 'heyman!' for card messages).
• msgType - The type of DingTalk message received, either 'TOPIC_ROBOT' or 'TOPIC_CARD'.
• messageId - Unique identifier of the received message from DingTalk headers.
• message - The parsed JSON content of the incoming DingTalk message.

Dependencies

• DingTalk streaming API client (dingtalk-stream)

Troubleshooting

• Ensure valid DingTalk API credentials are provided; missing or incorrect credentials will prevent connection.
• If no events are received, verify network connectivity and that the DingTalk clientId and clientSecret are correct.
• If the node does not emit messages, check if the 'isAutoResponse' property is set correctly to handle server retries.

Links

• DingTalk Real-Time Message Push API - Official documentation for DingTalk streaming message API used by this node.