Skip to main content
Siggnal webhooks let you connect signal events to any external system or automation tool — Zapier, Make (Integromat), n8n, custom applications, or any platform that accepts HTTP POST requests.
Webhooks are available on the Масштабирование plan. Upgrade your plan to enable this feature.

​
How Webhooks Work

Each time Siggnal detects a new signal matching your project configuration, it sends an HTTP POST request to your registered endpoint with a JSON payload describing the signal.
  • Siggnal expects a 200 OK response from your endpoint within 10 seconds.
  • If no valid response is received, Siggnal retries up to 3 times using exponential backoff.
  • After 3 failed attempts, the delivery is marked as failed and visible in your webhook delivery log under Settings → Integrations → Webhooks.

​
Setup

1

Open Webhook Settings

In Siggnal, go to Settings → Integrations → Webhooks.
2

Add an Endpoint

Click “Add webhook endpoint” to open the configuration form.
3

Enter Your Endpoint URL

Paste your endpoint URL. It must be a publicly accessible HTTPS address — Siggnal does not deliver to HTTP or localhost URLs.
4

Select Projects and Priorities

Choose which projects should trigger this webhook and which signal priority levels to include (High, Medium, Low, or any combination).
5

Add a Secret Token (Recommended)

Optionally enter a secret token. Siggnal will use it to sign every request so your endpoint can verify the payload came from Siggnal. See Verifying Webhook Signatures below.
6

Send a Test Request

Click “Send test” to dispatch a sample payload to your endpoint. Confirm your system receives it correctly before saving.
7

Save

Click Save. The webhook is now active and will fire on every new qualifying signal.

​
Webhook Payload Structure

Siggnal delivers the following JSON payload with every webhook request: 
{
  "signal_id": "sig_abc123",
  "project_id": "proj_xyz",
  "company": {
    "name": "Romashka LLC",
    "inn": "7707083893",
    "industry": "Software"
  },
  "event": {
    "type": "job_posting",
    "description": "Opened 3 vacancies for Sales Manager",
    "detected_at": "2025-01-15T09:30:00Z"
  },
  "priority": "high",
  "relevance_explanation": "This company is growing its sales team, which typically signals a need for CRM tools.",
  "recommended_action": "Call the commercial director",
  "contacts": [
    {
      "name": "Ivan Petrov",
      "role": "Commercial Director",
      "email": "i.petrov@romashka.ru",
      "phone": "+7 (495) 123-4567"
    }
  ]
}
FieldTypeDescription
signal_idstringUnique identifier for the signal
project_idstringThe Siggnal project that generated the signal
companyobjectCompany name, tax ID (INN), and industry
eventobjectSignal type, description, and detection timestamp
prioritystringhigh, medium, or low
relevance_explanationstringWhy this signal is relevant to your project
recommended_actionstringSuggested first outreach step
contactsarrayDecision-maker contacts with name, role, email, and phone

​
Verifying Webhook Signatures

When you configure a secret token, Siggnal includes an X-Siggnal-Signature header with every request. The value is the HMAC-SHA256 of the raw request body, keyed with your secret token. Always verify this header in production environments to confirm that incoming requests genuinely originate from Siggnal and have not been tampered with. Verification example (Node.js): 
const crypto = require("crypto");

function verifySignature(rawBody, secret, signatureHeader) {
  const expected = crypto
    .createHmac("sha256", secret)
    .update(rawBody)
    .digest("hex");
  return crypto.timingSafeEqual(
    Buffer.from(expected),
    Buffer.from(signatureHeader)
  );
}
Compute the HMAC over the raw bytes of the request body before any JSON parsing, and use a constant-time comparison to prevent timing attacks.

​
Use Cases

Zapier / Make

Connect Siggnal to 5 000+ apps without writing code. Trigger email sequences, Slack messages, CRM updates, or calendar events automatically when a new signal fires.

Custom Application

Build your own processing logic: score signals by fit, route them by territory, auto-enrich company data, or feed them into a custom dashboard or data warehouse.

Slack Notifications

Route signals to the right sales team Slack channel based on industry or priority level — so every rep only sees the signals that are relevant to them.

Spreadsheet Logging

Log every signal to Google Sheets for pipeline tracking, reporting, and historical analysis. Pairs well with a Make or Zapier scenario.
Start with Telegram notifications for simplicity — zero configuration, instant alerts. Once you’re ready to automate follow-up workflows like CRM entry or email sequences, layer webhooks on top.