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:

• APIs are like servers waiting for your request. You ask for something — and the API responds with data.

• Webhooks are the opposite. When something happens, Vector proactively pushes that data out to your system — no need to ask.

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 send that information 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 URL — Where should we send the data?

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

• https://zapier.com/hooks/mycustomendpointforvectordata

• https://clay.com/integration/visitor-data

• https://your-custom-system.com/webhooks/vector

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

2. Event Type — What should we send?

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

• contact.visited — A contact from a segment landed on your website

• contact.intent — A contact showed offsite intent

• company.visited — A company showed anonymous interest on your site

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

3. Event Catalog — What does the data 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:

json

{"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 specific to that action.

🎯 Targeting Specific Segments

By default, Vector will fire a webhook for all enabled segments that have the “Webhook” action.

If you'd like to limit a webhook to only fire for certain segments, you can add them in the Channels section of the webhook settings using the following format:

nginx

segment_12345 segment_67890

You can find a segment's ID in the URL of its page (e.g., https://app.vector.co/segments/12345).
If no segment is specified, the webhook will apply to all active segments with the webhook action.

👻 Why This Matters

With webhooks, you can:

• Trigger a Slack alert when a key contact visits your pricing page

• Send high-intent leads to your CRM or enrichment tool

• Start an email or ad campaign when someone shows intent

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!