Import from Crontab

If you already have schedules in crontab, TrigRun can import them so you do not have to recreate everything by hand.

1. Prepare your crontab

Start with a plain crontab file. Each line should include a schedule and a URL, for example:

*/5 * * * * curl -fsS https://api.example.com/health
0 2 * * * curl -fsS https://api.example.com/backup

If your existing setup uses shell wrappers or extra flags, keep the line as close to your real production command as possible.

2. Import it

Use the import endpoint:

curl -X POST https://api.trigrun.com/v1/jobs/import \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "crontab": "*/5 * * * * curl -fsS https://api.example.com/health\n0 2 * * * curl -fsS https://api.example.com/backup",
    "default_url": "https://api.example.com/health"
  }'

The API returns how many jobs were imported and how many lines were skipped.

3. Review the imported jobs

Open Jobs and check that each imported schedule matches your expectations:

• UTC schedule time
• browser-local preview
• request URL
• HTTP method
• retry policy

4. Clean up unsupported lines

If a crontab line does not map cleanly to a TrigRun job, adjust it manually and import again. That is usually faster than debugging a malformed shell command after the fact.

Helpful references

• Quickstart
• Jobs guide
• Authentication