Webhooks
Receive real-time notifications for LinkedIn outreach events
Overview
Kakiyo webhooks allow you to receive real-time notifications when specific events occur within your LinkedIn outreach campaigns. This enables you to integrate Kakiyo with your existing tools and workflows, such as CRM systems, email platforms, or custom applications.
How Webhooks Work
- You create a webhook endpoint (URL) on your server that can receive POST requests
- You register this endpoint with Kakiyo, specifying which events you want to receive
- When a matching event occurs, Kakiyo sends a POST request to your endpoint with event data
- Your server processes the webhook payload and takes appropriate actions
Available Events
Kakiyo supports the following webhook events:
Event ID | Description |
---|---|
linkedin.message.sent | Triggered when an agent sends a message to a prospect |
linkedin.message.received | Triggered when a prospect responds to an agent |
linkedin.invitation.sent | Triggered when an agent sends a connection invitation |
linkedin.invitation.accepted | Triggered when a prospect accepts a connection invitation |
prospect.qualification.manual | Triggered when a prospect requires manual qualification review |
prospect.unqualified | Triggered when a prospect is automatically marked as unqualified |
You can also use the wildcard event *
to subscribe to all available events.
Webhook Payload
When an event occurs, Kakiyo sends a JSON payload to your webhook endpoint. Here’s an example payload for a linkedin.message.received
event:
Securing Webhooks
To ensure that webhook requests are coming from Kakiyo, we include a signature in the X-Kakiyo-Signature
header. This signature is an HMAC SHA-256 hash of the request payload, using your webhook secret as the key.
Here’s how to verify the signature:
Testing Webhooks
You can test your webhook integration without waiting for real events to occur. Kakiyo provides a test endpoint that allows you to send a test webhook to your registered endpoints:
You can also get example payloads for each event type to help you build your integration: