[PR #1162] [MERGED] feat: Cron v0.1.0 #1425

New Issue

2026-02-22T17:57:21-05:00

yindo commented

2026-02-22 17:57:21 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1162
Author: @yt-koike
Created: 8/31/2025
Status: ✅ Merged
Merged: 9/1/2025
Merged by: @LogicOber

Base: main ← Head: main

📝 Commits (3)

17fa478 Add files via upload
151c0f7 Update dify-cron from 0.2.0 to 0.1.0
1b8d2a5 revise PRIVACY.md and related documents

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 yt-koike/dify-cron/dify-cron-0.1.0.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Plugin Author: yt-koike
Plugin Name: cron
Repository URL: https://github.com/yt-koike/dify-cron

2. Submission Type

New plugin submission
Version update for existing plugin

3. Description

New features:

Cloud support: It can now run on https://cloud.dify.ai/ thanks to https://cron-job.org/
Timezone support: You can now set your own timezone.
More detailed status: You can see the app-id, current UTC time & current time at your timezone, loaded cron string on the status.

4. Checklist

I have read and followed the Publish to Dify Marketplace guidelines
I have read and comply with the Plugin Developer Agreement
I confirm my plugin works properly on both Dify Community Edition and Cloud Version
I confirm my plugin has been thoroughly tested for completeness and functionality
My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

Step-by-step setup instructions
Detailed usage instructions
All required APIs and credentials are clearly listed
Connection requirements and configuration details
Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

For self-hosted servers (i.e., when the "Is this cloud version?" switch is set to False),
Cron does not use any external APIs or collect any personal data.

For cloud.dify.ai (i.e., when the "Is this cloud version?" switch is set to True),
Cron relies on the cron-job.org API to regularly invoke the designated Dify cloud endpoint.

When registering a cron job with cron-job.org, Cron transmits the following information to https://api.cron-job.org/jobs:

The API key issued by cron-job.org
The endpoint URL generated by Dify for the target workflow execution (e.g., https://randomhash1111.ai-plugin.io/cron/runOnce)
Scheduling information (seconds, minutes, hours, days, months, weekdays, and timezone) required to trigger the specified Dify cloud endpoint

After successful registration, cron-job.org returns a cron job identifier, which Cron retains until the user cancels the job.

For details on third-party privacy and data retention policies, please refer to:

Privacy Policy

I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1162 **Author:** [@yt-koike](https://github.com/yt-koike) **Created:** 8/31/2025 **Status:** ✅ Merged **Merged:** 9/1/2025 **Merged by:** [@LogicOber](https://github.com/LogicOber) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (3) - [`17fa478`](https://github.com/langgenius/dify-plugins/commit/17fa4783dc58afc0e6b9631ba9679b16e716d9b3) Add files via upload - [`151c0f7`](https://github.com/langgenius/dify-plugins/commit/151c0f75df511de1fae4973792cb97802ebc0e11) Update dify-cron from 0.2.0 to 0.1.0 - [`1b8d2a5`](https://github.com/langgenius/dify-plugins/commit/1b8d2a53462633e439d9c3257028d835f7d3eb80) revise PRIVACY.md and related documents ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `yt-koike/dify-cron/dify-cron-0.1.0.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata  - **Plugin Author**: yt-koike - **Plugin Name**: cron - **Repository URL**: https://github.com/yt-koike/dify-cron ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description  New features: - Cloud support: It can now run on https://cloud.dify.ai/ thanks to https://cron-job.org/ - Timezone support: You can now set your own timezone. - More detailed status: You can see the app-id, current UTC time & current time at your timezone, loaded cron string on the status. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection For self-hosted servers (i.e., when the "Is this cloud version?" switch is set to False), Cron does not use any external APIs or collect any personal data. For cloud.dify.ai (i.e., when the "Is this cloud version?" switch is set to True), Cron relies on the cron-job.org API to regularly invoke the designated Dify cloud endpoint. When registering a cron job with cron-job.org, Cron transmits the following information to https://api.cron-job.org/jobs: - The API key issued by cron-job.org - The endpoint URL generated by Dify for the target workflow execution (e.g., https://randomhash1111.ai-plugin.io/cron/runOnce) - Scheduling information (seconds, minutes, hours, days, months, weekdays, and timezone) required to trigger the specified Dify cloud endpoint After successful registration, cron-job.org returns a cron job identifier, which Cron retains until the user cancels the job. For details on third-party privacy and data retention policies, please refer to: - [cron-job.org Terms of Service](https://cron-job.org/en/tos/) - [cron-job.org Privacy Policy](https://cron-job.org/en/privacy/) ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-22 17:57:21 -05:00

yindo closed this issue

2026-02-22 17:57:23 -05:00

yindo referenced this issue

2026-02-22 18:02:45 -05:00

[PR #1425] [MERGED] # add pangu-0.0.1.difypkg #1607

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1425