CatchAll Create Monitor — schedule recurring jobs

CatchAll Create Monitor sets up automated, recurring CatchAll jobs based on a completed reference job. The monitor reuses the query, validators, and enrichments from the reference job and runs on your specified schedule. Configure a webhook to receive notifications when each scheduled job completes.

This Actor maps to the POST /catchAll/monitors/create endpoint.

When to use this Actor

• Track ongoing events. Monitor funding rounds, executive changes, regulatory approvals, or any recurring topic automatically.
• Build data feeds. Schedule daily or weekly jobs and push results to external services using webhooks.
• Avoid manual reruns. Set up a monitor once and let it run on schedule, deduplicating records across executions at the API level.

Input

Field	Type	Required	Description
apiKey	String	Yes	Your CatchAll API key
referenceJobId	String	Yes	Job ID of a successfully completed job to use as template
schedule	String	Yes	Schedule in plain text (e.g., "every day at 12 PM UTC")
webhookUrl	String	Yes	URL to receive notifications when jobs complete
webhookMethod	String	No	HTTP method for webhook: POST, PUT, or PATCH (default: POST)
webhookAuthHeader	String	No	Authorization header value (e.g., "Bearer YOUR_TOKEN")
webhookHeaders	Object	No	Additional HTTP headers as a JSON object

Input example

{
  "apiKey": "YOUR_CATCHALL_API_KEY",
  "referenceJobId": "5f0c9087-85cb-4917-b3c7-e5a5eff73a0c",
  "schedule": "every day at 12 PM UTC",
  "webhookUrl": "https://your-endpoint.com/webhook",
  "webhookAuthHeader": "Bearer YOUR_TOKEN"
}

The schedule is specified in plain text and converted to a cron expression by the API. Examples: "every day at 9 AM UTC", "every Monday at 8 AM UTC", "every 6 hours".

Output

The Actor returns the monitor_id in the default Dataset. Use this ID with other monitor Actors to manage, update, or retrieve results.

Output example

{
  "monitor_id": "3fec5b07-8786-46d7-9486-d43ff67eccd4",
  "status": "Monitor Created Successfully"
}

Monitor vs. Apify schedules

CatchAll monitors and Apify schedules both run jobs on a recurring basis, but they serve different purposes:

• CatchAll monitors handle job scheduling and record deduplication at the API level. Results from all executions are aggregated and accessible via the CatchAll API.
• Apify schedules run any Actor on a schedule from the Apify Console. Use these when you want platform-level control or need to chain other Actors after each run.

You can use either approach, or combine them.

Other CatchAll Actors

Actor	Description
CatchAll	End-to-end job: submit, poll, and retrieve results
CatchAll Update Monitor	Update a monitor's webhook configuration
CatchAll Start/Stop Monitor	Pause or resume a monitor

For the full list, visit the Newscatcher organization page.

Resources

• CatchAll documentation
• Monitors guide