Filter by tags
No tags available

New Task

Press Enter to add tag

Sample Task
Click a template to insert URL

Format: minute hour day month weekday

Quick templates:

sec

Settings & References

Application settings and system links.

System Links

Scheduler Status Current scheduler status and active jobs
Scheduler Logs View task execution history and logs
API Docs View API documentation
Use these variables in cron expressions, task names or URLs. They will be replaced with real values when executed.
{hour} Hour (0-23) 14
{hour12} Hour (1-12) 2
{minute} Minutes (0-59) 30
{second} Seconds (0-59) 45
{day} Day of month 15
{month} Month 9
{year} Year 2025
{year2} Year (2 digits) 25
{weekday} Weekday (0-6) 2
{weekday_name} Weekday name Wednesday
{weekday_name_ro} Weekday name (Romanian) Miercuri
{weekday_name_es} Weekday name (Spanish) Miércoles
{month_name} Month name September
{month_name_ro} Month name (Romanian) Septembrie
{month_name_es} Month name (Spanish) Septiembre
{timestamp} Unix timestamp 1726574400
{date} Date YYYY-MM-DD 2025-09-17
{time} Time HH:MM:SS 14:30:45
{datetime} Date and time 2025-09-17 14:30:45

Click any variable to copy it to clipboard

Use these URLs to send push notifications via Pushover API.

Personal notifications (you only)

Normal: http://localhost:8650/api/pushover?message=Hello
With title: http://localhost:8650/api/pushover?message=Error&title=Server
High priority: http://localhost:8650/api/pushover?message=Critical&priority=1
Emergency: http://localhost:8650/api/pushover?message=EMERGENCY&priority=2&title=URGENT

Family notifications (you + wife)

Normal: http://localhost:8650/api/pushover?message=Dinner ready&recipient=family
With title: http://localhost:8650/api/pushover?message=School meeting&title=Kids&recipient=family
High priority: http://localhost:8650/api/pushover?message=House problems&priority=1&recipient=family
Emergency: http://localhost:8650/api/pushover?message=COME HOME NOW&priority=2&recipient=family

Pushover priorities

-2 Lowest
-1 Low
0 Normal (default)
1 High
2 Emergency (requires confirmation)

Additional parameters

&title=URGENT - notification title
&priority=1 - notification priority
&sound=siren - notification sound
Popular: pushover, siren, bike, bugle, incoming, spacealarm, persistent, none
&url=http://example.com - link in notification
&url_title=Open - link text
&device=phone - specific device
For priority=2 (emergency) only:
&retry=60 - repeat every 60 seconds
&expire=3600 - stop after 1 hour

Click any URL to copy it to clipboard

Manage your URL templates for quick insertion into tasks.

Your URL Templates

Add URL Template

You can use variables like {timestamp}, {date}, {time} in your URL templates

Manage task categories for Kanban board organization. Drag and drop tasks between categories.

Task Categories

Add Category

Categories help organize your tasks in a Kanban board view. Use arrows to reorder categories.

Documentation for the TTS from JSON API endpoint.

Endpoint: /api/tts-from-json

This endpoint fetches data from a JSON API, checks if the status is "success", and sends the specified field to a TTS (Text-to-Speech) service.

GET http://localhost:8650/api/tts-from-json
↑ This scheduler API (current service)

Parameters

source_url required

URL to fetch JSON data from (e.g., your calendar API)

Example: https://calendar.pelin.top/events/summary/today
tts_url required

URL of your TTS service (without the 'text' parameter)

Example: http://192.168.1.48:8000/tts/google
Example: http://192.168.1.48:8000/tts/openai
↑ TTS server address (external service)
field optional

JSON field to extract (default: "summary")

Default: summary
status_field optional

JSON field name to check for status (default: "status")

Default: status
Empty string = skip status check

Use empty string (status_field=) to skip status validation

status_value optional

Expected value for status field (default: "success")

Default: success
Examples: ok, true, 200, active
Additional params optional

Any additional parameters (speed, volume, lang, etc.) will be passed to the TTS service

Example: speed=0.9&volume=0.3

How It Works

  1. Sends GET request to source_url
  2. Optionally checks status (if status_field is provided):
    • Checks if status_field equals status_value
    • If not - skips TTS request and returns info
  3. Extracts the specified field from JSON
  4. Sends the extracted text to your TTS service with additional parameters

New: You can now use this endpoint with ANY API by customizing status checking or disabling it completely!

Usage Examples

Example 1: Default - Calendar with status check

http://localhost:8650/api/tts-from-json?source_url=https://calendar.pelin.top/events/summary/today&tts_url=http://192.168.1.48:8000/tts/google&field=summary&speed=0.9

✓ Uses default: status_field=status and status_value=success

Example 2: OpenAI TTS with volume control

http://localhost:8650/api/tts-from-json?source_url=https://calendar.pelin.top/events/summary/today&tts_url=http://192.168.1.48:8000/tts/openai&field=summary&speed=1.0&volume=0.3

✓ With additional TTS parameters (volume)

Example 3: Custom status field and value

http://localhost:8650/api/tts-from-json?source_url=https://api.example.com/data&tts_url=http://192.168.1.48:8000/tts/google&field=message&status_field=result&status_value=ok

✓ For APIs that use {"result": "ok"} instead of {"status": "success"}

Example 4: NO status check (always sends to TTS)

http://localhost:8650/api/tts-from-json?source_url=https://api.example.com/quotes&tts_url=http://192.168.1.48:8000/tts/google&field=quote&status_field=&speed=0.9

✓ Use status_field= (empty) to skip status validation completely

Response Examples

Success Response (TTS was called)

{
  "status": "success",
  "message": "TTS request sent successfully",
  "text_sent": "În seara de 7 noiembrie, ai un test event...",
  "tts_status_code": 200
}

Skipped Response (status was not "success")

{
  "status": "skipped",
  "reason": "Source status is 'no_events', not 'success'",
  "message": "Nu există evenimente planificate pentru 7 noiembrie 2025."
}

Server Architecture

localhost:8650
→ This scheduler API (current service)
192.168.1.48:8000
→ TTS Server (external service on another machine)
calendar.pelin.top
→ Calendar API (your event data source)

Data Flow: You call scheduler API → it fetches from Calendar API → if success, it sends to TTS Server

Important Notes

  • Status checking is flexible:
    • Default: checks status == "success"
    • Custom: use status_field and status_value for other APIs
    • Disabled: use status_field= to skip check entirely
  • Use localhost:8650 for scheduler API, 192.168.1.48:8000 for TTS server
  • You can schedule this endpoint in your task scheduler for automated announcements
  • All query parameters (except source_url, tts_url, field, status_field, status_value) are forwarded to the TTS service
  • Works with any JSON API - not just calendar events!

Confirm

Are you sure?

Input

Please enter value:

Execution Logs

Loading logs...