Dingtalk Log

What This Skill Does

The Dingtalk Log skill is a powerful utility for OpenClaw AI agents to interface directly with the Dingtalk enterprise collaboration platform. By utilizing the topapi/report/list interface, the agent can programmatically retrieve employee work reports and logs, including metadata such as the creator, submission time, and template type. This skill enables seamless data integration between Dingtalk and your internal workflows, allowing for automated report aggregation, trend analysis, and administrative oversight without requiring manual logins or manual report extraction.

Installation

To install this skill, use the following OpenClaw command in your terminal: clawhub install openclaw/skills/skills/3rdsw/dingtalk-log

Use Cases

1. Automated Weekly Review: Generate a summary of team progress by aggregating weekly reports for a specific department or project group.
2. Compliance & Auditing: Maintain a secure, historical archive of employee logs for audit trails or performance evaluation purposes.
3. Attendance & Effort Monitoring: Analyze report submission frequency per employee to understand engagement levels or ensure adherence to reporting policies.
4. Dynamic Data Routing: Automatically send log details into other systems like Slack, Jira, or a centralized dashboard based on report content or keywords.

Example Prompts

1. "Retrieve all log entries created by user_id '8892' between last Monday and today."
2. "Can you pull all the weekly report logs for the engineering team from the last 30 days and summarize the recurring blockers?"
3. "List the most recent 20 logs submitted by the sales department using the 'Daily Plan' template and format them into a table."

Tips & Limitations

• Authentication Requirements: You must have a valid Dingtalk enterprise internal application configured with the 'Query Enterprise Employee Log' permission. Always cache the access_token for 7200 seconds to ensure efficient API usage and prevent rate-limiting.
• Pagination Handling: The skill uses a cursor-based pagination system. If has_more is true in the response, ensure you use the next_cursor value to fetch subsequent batches of data.
• Temporal Constraints: The interface enforces a strict constraint where the interval between start_time and end_time must not exceed 180 days. Ensure your logic handles date calculations precisely using Unix milliseconds.
• Performance: As per API documentation, the page size is capped at 20 entries per request.