Skip to main content
This guide walks through two real-world scenarios. Every code block is ready to copy, paste, and run — just replace YOUR_API_KEY with your actual key.

Scenario: Monitor when OpenAI posts new jobs

You want to know immediately when OpenAI posts job openings — and automatically get contact details for their engineering leadership.

Create the monitor

What this does:
  • Monitors OpenAI (companies: ["67c4696b-..."]) for new US-based job postings
  • Enriches company data and finds up to 5 Director/VP-level Engineering contacts
  • Delivers up to 5 records per trigger to your webhook
  • All other settings use sensible defaults (real-time frequency, 500 daily cap, etc.)
For company_first mode, you typically only need companies (or domains / linkedin_urls) and signal filters. company_filters is optional — it adds a second filtering layer when you want to combine a watch list with broader company criteria.

Test it immediately

Do not wait for the scheduled scan — trigger a manual run to verify everything works. Include tried_at with a past timestamp to ensure there is data available (using the current time may return 0 results if no new signals have appeared yet):
Manual triggers consume credits just like scheduled triggers. Use tried_at with a recent past date to get a representative sample of results for testing.

Check the results

After a few seconds, check your webhook URL at usewebhook.com to see the payload. You can also verify via the logs:
Each log entry shows the status, signal/company/people counts, credit usage, and processing time.

Retrying a Failed Delivery

If a specific trigger failed (e.g., your webhook was temporarily down), retry it without re-running the entire scan:
Find the monitor_log_id by querying Statistic Logs and filtering for entries with "status": "failed".

Next Steps

Best Practices

Frequency, credits, retries, and scaling.

Webhook Setup

Detailed webhook configuration and signature verification.