Webhooks

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 details page

What are webhooks?

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. Any type of searches (job, company, technology, etc) can be used to trigger a webhook.

Webhooks Applications

  • Initiate a workflow in an automation tool like Zapier, Make, N8N when a new job is posted or a company adopts a new technology (e.g., Snowflake, Hubspot, Python).
  • Send a Slack notification to your team when a new job is found or a company adopts a new technology (e.g., Snowflake, Hubspot, Python).
  • Automatically update a Google Sheet with new job or company data.
  • Trigger an email alert to a specific distribution list when a new job matches certain criteria.
  • Create a table in Airtable to store job listings.
  • Integrate with a CRM system to add new company information as leads.

Webhook types

There are three types of webhooks:

  • job.new: Fires whenever we discover a new job posting that matches your search criteria. The data schema is the same as our Job API response schema.
  • company.new: Fires whenever we discover a new company that matches your search criteria. The data schema is the same as our Company API response schema.
  • tech.new: Triggered when company adopts a new technology (request access to this)

Webhook events statuses

Webhook events have the following statuses:

  • success: The webhook event was processed successfully.
  • in progress: The webhook event is being processed.
  • failed: The webhook event failed to be processed.
  • not_triggered: The webhook event was detected but not triggered because you run out of API credits.

Pricing

Webhooks and API requests share the same pricing. When an event is triggered, it consumes 1 (job.new) or 3 (company.new, tech.new) API credits based on the type of event. Learn more about our credit system here.

How to monitor webhook usage

You can monitor webhook usage in the Usage page.

You can break down the usage by event status or webhook.

Webhook usage

Webhooks API

You can manage programmatically your webhooks by using the Webhooks API. This is specially useful if you want to integrate webhooks with your own application.

FAQs

How is this guide?

Last updated on