Skip to main content
Avina can send signal and contact data to any external system via webhooks. Use webhooks to pipe data into tools like Clay, Zapier, n8n, Make, or your own internal systems.

​
Overview

When an automation’s action is set to Send to webhook, Avina sends an HTTP POST request to your specified URL every time the automation triggers. The payload contains structured signal and contact data.

​
Payload Schema

Each webhook delivery sends a JSON payload with the following structure: 
{
  "event": "automation.triggered",
  "automation_id": "abc123",
  "automation_name": "Pricing Page Visitor → Webhook",
  "triggered_at": "2026-04-06T14:30:00Z",
  "signal": {
    "type": "web_visit",
    "signal_group_id": "sg_456",
    "signal_group_name": "Pricing Page Visitors",
    "score": 85,
    "icp_fit": "A",
    "account_fit_score": 92,
    "triggered_at": "2026-04-06T14:28:00Z"
  },
  "account": {
    "name": "Acme Corp",
    "domain": "acme.com",
    "industry": "SaaS",
    "employee_count": 150,
    "crm_id": "001ABC123",
    "crm_url": "https://your-crm.com/accounts/001ABC123"
  },
  "contacts": [
    {
      "first_name": "Jane",
      "last_name": "Smith",
      "email": "jane@acme.com",
      "title": "VP of Engineering",
      "phone": "+1-555-0100",
      "linkedin_url": "https://linkedin.com/in/janesmith"
    }
  ],
  "context": {
    "summary": "Jane Smith from Acme Corp visited your pricing page and spent 4 minutes reviewing enterprise plan details.",
    "pages_visited": ["/pricing", "/pricing/enterprise"],
    "topics_of_interest": ["enterprise pricing", "SSO", "API access"]
  }
}
The exact fields included vary by signal type. Web visit signals include page and session data; new hire signals include the new role and company; champion movement signals include previous and new company details.

​
Setting Up a Webhook

  1. Create an automation triggered by the signal type you want.
  2. Under Actions, select Send to webhook.
  3. Enter your webhook URL.
  4. Click Test Webhook to send a sample payload and verify your endpoint responds with a 200 status. This catches configuration issues (wrong URL, auth problems, firewall blocks) before the automation goes live.
  5. Save and activate the automation.

​
Authentication

Webhook requests include the following headers that you can use to verify the request originated from Avina:
HeaderDescription
Content-Typeapplication/json
User-AgentAvina-Webhook/1.0
For additional security, you can validate requests by checking the source IP or implementing a shared secret in your webhook URL (e.g., https://your-endpoint.com/webhook?token=YOUR_SECRET).

​
Retry Behavior

If your endpoint returns a non-2xx status code or times out, Avina does not automatically retry webhook deliveries. Ensure your endpoint is reliable and returns a 200 response promptly.

​
Common Use Cases

Use CaseHow
Enrich in ClaySend signal leads to a Clay table for waterfall enrichment
Trigger a Zapier workflowUse a Zapier webhook trigger to route data to any connected app
Log to internal databasePOST signal data to your own API for custom analytics
Notify in Microsoft TeamsSend webhook to a Teams incoming webhook connector
Sync to a data warehouseRoute signal events to Snowflake, BigQuery, or Redshift via a middleware