Scheduler Pack
★Trusted◇Sandbox optionalv1.0.0MIT✔Verified80by AgentNode · published 3 months ago · toolpack
Schedule tasks, manage calendars, and set reminders.
Calendar integration with iCal support and cron-style scheduling.
Quick Start
agentnode install scheduler-packRuns in a subprocess with filtered environment by default. Declared permissions are policy-checked, not sandboxed.
Usage
From packagefrom scheduler_pack.tool import run
# Schedule a daily data sync at 6:00 AM UTC
result = run(
action="schedule_task",
name="daily-data-sync",
cron="0 6 * * *",
timezone="UTC",
callback={
"type": "webhook",
"url": "https://api.example.com/pipelines/data-sync/trigger",
"method": "POST",
"headers": {"Authorization": "Bearer ${PIPELINE_TOKEN}"}
},
description="Sync warehouse data from upstream sources"
)
print(f"Task scheduled: {result['task_id']}")
print(f"Next run: {result['next_run']}")
print(f"Cron: {result['cron_expression']}")
# List all scheduled tasks
all_tasks = run(action="list_tasks")
for task in all_tasks["tasks"]:
print(f" [{task['status']}] {task['name']} — next: {task['next_run']}")Runs locally on your machine. No execution data is sent to AgentNode. Permissions are checked before execution. Learn how this works
Verification
Package installs and imports correctly. runtime checks passed.
This package was executed and validated by AgentNode before listing. Install, import, and runtime checks passed.
Verified in real_auto mode
Last verified 11h ago· Runner v2.0.0
Use this when you need to...
- ›Schedule recurring data pipeline runs using cron expressions
- ›Create calendar events with reminders from natural language input
- ›Set one-time task reminders that trigger agent actions at a future time
- ›Parse and validate iCal feeds to check for scheduling conflicts
- ›Manage a queue of deferred tasks with priority-based execution order
README
Version History
Capabilities
Permissions
Declared by the publisher. Checked before execution by the policy gate.
Permissions are policy-checked before execution. For trusted and curated packages that run on the host, network and filesystem access are policy-checked but not OS-sandboxed. When runtime isolation is required for untrusted/community code, AgentNode uses sandbox-or-fail-closed if the required container runtime and pinned image are available. Learn more
Privacy
All tool execution happens locally on your machine. AgentNode never receives:
- • Tool inputs or outputs
- • Execution logs
- • Data your agent processes
Only install events and search queries are sent to the registry.
agentnode install scheduler-packFiles (3)
License
MITStats
Compatibility
Frameworks
Runtime
pythonPython Version
>=3.10Trust & Security
Publisher
AgentNode
@agentnode