Learn how to use webhooks to get notified when events occur (new jobs, tech changes, etc) in TheirStack and trigger actions in your external systems like N8N, Zapier, Make, Airtable, etc.
Webhooks allow you to send data when specific events occur (new jobs, tech changes, etc) to external systems like N8N, Zapier, Make, Airtable, your own webhook endpoint, etc.
For instance, you can configure a webhook to alert you when a new job is listed in a particular location, company, or technology sector.
Webhooks are dependent on a search, which defines the criteria for triggering the webhook.
There are two types of webhooks:
job.new
: Triggered when a new job is discovered by TheirsStack.company.new
: Triggered when a new company is discovered by TheirsStack.Follow these steps to set up a webhook:
If you are builing your own webhook endpoint, please take into account the following:
Webhooks have the following settings:
Choose where to start
: You can choose whether to start listening from this point forward or from the start of the search. If you choose to start from the start of the search, you will receive all events that have occurred since the search was created.
Trigger once per company
: When enabled, the webhook will fire only once for each company. This is helpful for sales workflows where you want to act on the first job posted (e.g., send an email, add to a CRM) without triggering the workflow for every subsequent job from the same company. Eg: If active, Company A with 5 jobs → 1 event triggered. If deactivated, Company A with 5 jobs → 5 events triggered.
When you run out of API credits, webhook event monitoring is temporarily paused. During this period, no new events will appear in your webhook history. Monitoring automatically resumes once you purchase additional API credits.
Whether you miss events during the pause depends on your search criteria. For example, if your webhook tracks jobs posted within the last 60 days and you lack credits for 2 days, you won't miss anything - when credits are restored, all jobs discovered during the pause will still trigger your webhook as they match your search parameters.
If the webhook event fails, it will be automatically retried every hour for 48 hours.
Webhook events are billed at the same rate as API requests. They consume 1 API credit per event.