On this page

Webhooks

ScaliQ can POST JSON to your HTTPS URL when events occur.

Setup

  1. Open app.scaliq.ai/api-mcp → Webhooks
  2. Create a subscription: name, HTTPS URL, events, optional campaign filter
  3. Optionally set a signing secret (you choose the string)

Default max 5 webhooks per workspace. Manage subscriptions in the dashboard (not via REST in v1).

Events

EventWhen
reply.receivedProspect replied
connection.acceptedConnection accepted
lead.taggedLead tagged (manual or auto)
account.disconnectedLinkedIn account disconnected / failed

Events are delivered when ScaliQ records them — typically soon after they happen on LinkedIn. They are not gated on the campaign board’s “why it’s not Done yet” summary, which refreshes on a slower cadence for completion status only.

data.accountId is the LinkedIn account for the lead when known. For lead.tagged, if the lead has no stored account, ScaliQ falls back to the inbox chat’s account (same as the unified inbox). May still be null if there is no chat yet. data.tag is the lead’s current label or null, and may be a built-in tag or a workspace custom tag.

Payload shape

{
  "id": "evt_...",
  "type": "reply.received",
  "createdAt": "2026-07-24T05:00:00.000Z",
  "data": {
    "campaignId": "search_abc",
    "leadId": "lead_xyz",
    "accountId": "acc_...",
    "linkedinUrl": "https://www.linkedin.com/in/jane-doe/",
    "fullName": "Jane Doe",
    "messageText": "Thanks, interested in learning more.",
    "tag": null,
    "messageId": "msg_...",
    "conversationId": "acc_...__ACoAA...",
    "messageTimestamp": "2026-07-24T04:59:58.000Z",
    "direction": "incoming"
  }
}

data fields present depend on the event (messageText / message ids on replies; tag on tag events; etc.). messageText may be truncated (~4000 chars).

On reply.received, use messageId + messageTimestamp for incremental sync and duplicate prevention. conversationId is ScaliQ’s thread id when available. direction is "incoming". Envelope createdAt is webhook delivery time; messageTimestamp is when ScaliQ recorded the inbound message. Other events include the same keys as null.

connection.accepted (example)

{
  "id": "evt_...",
  "type": "connection.accepted",
  "createdAt": "2026-07-24T05:00:00.000Z",
  "data": {
    "campaignId": "search_abc",
    "leadId": "lead_xyz",
    "accountId": "acc_...",
    "linkedinUrl": "https://www.linkedin.com/in/jane-doe/",
    "fullName": "Jane Doe",
    "messageText": null,
    "tag": null,
    "messageId": null,
    "conversationId": null,
    "messageTimestamp": null,
    "direction": null
  }
}

lead.tagged (example)

{
  "id": "evt_...",
  "type": "lead.tagged",
  "createdAt": "2026-07-24T05:00:00.000Z",
  "data": {
    "campaignId": "search_abc",
    "leadId": "lead_xyz",
    "accountId": "acc_...",
    "linkedinUrl": "https://www.linkedin.com/in/jane-doe/",
    "fullName": "Jane Doe",
    "messageText": null,
    "tag": "Interested",
    "messageId": null,
    "conversationId": null,
    "messageTimestamp": null,
    "direction": null
  }
}

account.disconnected (example)

{
  "id": "evt_...",
  "type": "account.disconnected",
  "createdAt": "2026-07-24T05:00:00.000Z",
  "data": {
    "campaignId": null,
    "leadId": null,
    "accountId": "acc_...",
    "linkedinUrl": null,
    "fullName": null,
    "messageText": null,
    "tag": null,
    "messageId": null,
    "conversationId": null,
    "messageTimestamp": null,
    "direction": null
  }
}

Signing (optional)

If you set a signing secret on create, every delivery includes:

X-Webhook-Signature: <your-secret>
X-ScaliQ-Signature: <your-secret>

The value is exactly the string you entered (e.g. password1234) — not an HMAC. In n8n, use Header Auth: header X-Webhook-Signature, value = that secret. (X-ScaliQ-Signature carries the same value and keeps working for existing setups — prefer X-Webhook-Signature for new integrations.)

Delivery

  • Events are persisted and delivered by a durable queue: up to 5 attempts with backoff (one HTTP attempt per try, 10s timeout each)
  • At-least-once per webhook until the attempt budget is exhausted — make your endpoint idempotent on the event id (identical on every attempt, as is createdAt)
  • Invalid URLs and signing problems are not retried
  • Failures never block ScaliQ inbox / tagging flows