Vector’s webhooks are designed to be incredibly flexible — allowing you to push data out of the platform and into the tools where your team already works.


🤝 Webhooks vs. APIs

To understand webhooks, it's helpful to compare them to APIs:

Think of it this way: if Vector has valuable information about a visitor or contact, and you want to take action immediately (in Slack, in your CRM, in Clay, etc.), a webhook lets us spit that information out to you the moment it qualifies.


🔧 How It Works — 3 Simple Parts

To set up a webhook in Vector, you’ll configure three core pieces:

1. Endpoint URLWhere should we spit the data?

This is the destination where you want Vector to send data — such as:

You control this URL — it can be anything that listens for incoming POST requests.


2. Event TypeWhat should we spit?

Choose the types of Vector events you want to receive via webhook. These include:

Only the events you select will be pushed out. You can create different webhooks for different actions or systems.


3. Event CatalogWhat does the spit look like?

Each event type comes with its own payload — a set of data fields sent when the event is triggered.

For example, if you select contact.visited, you might receive:

{
  "event": "contact.visited",
  "timestamp": "2024-04-15T14:32:00Z",
  "contact": {
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane.doe@example.com",
    "title": "Marketing Manager",
    "company": "Acme Corp",
    "linkedin_url": "https://linkedin.com/in/janedoe"
  },
  "segment": {
    "id": "7264",
    "name": "High Intent - ABM Contacts"
  }
}

Other event types will include relevant fields for that action.


👻 Why This Matters

With webhooks, you can:

Vector doesn’t just help you see the signals — it lets you act on them in real time.

Need help setting up your webhook endpoint or choosing the right events to send?
👻 Boo us at support@vector.co — we’re here to help you automate the spooky stuff!