Signalist connects to your own systems in three ways: the API , webhooks that send leads to your endpoint, and the MCP server for AI assistants. All three are under Integrations in the sidebar, in the Developer section.
Open Integrations → API.
A key acts for your whole workspace and has no scopes or expiry date. When a key adds or changes leads, it reaches only your workspace's public lists; private lists cannot be reached with an API key. When you update a lead through the API, fields that are not lead fields are ignored, and a lead's list, prospect and status cannot be changed this way. So:
Webhooks send leads from a list to a URL of yours, for example to start a workflow in another tool.

In a list's settings, under Advanced settings → Send leads to a webhook, choose the webhook and when leads are sent: all found leads, all leads including not found, all found and unsure leads, when a lead is assigned to a campaign, or when a lead replies. You can also select leads in a list and use Add to webhook.
Each lead is sent as its own JSON request, with the same lead fields as a list export. What the request looks like around the lead depends on the webhook's payload format.
Every webhook has a Payload format. You pick it in the Create new webhook dialog and can change it later by opening the webhook for editing.
data. Use it when one endpoint receives several triggers, or when your system needs to skip repeated deliveries.A change of format applies to the next deliveries you send. Deliveries that were already queued before payload formats were introduced are still sent as Version 1, even to a webhook you have switched to Version 2.
Before you switch an existing webhook to Version 2, make sure your endpoint reads an object instead of an array.
{
"id": "2a60142d-c9e6-5f8d-8c93-e0454481e5fa",
"type": "lead.assigned",
"createdAt": "2026-10-13T16:10:00.000Z",
"webhookId": 24,
"list": { "id": 238, "name": "My list" },
"data": { "id": 15136, "firstName": "…", "lastName": "…" }
}
| Field | Meaning |
|---|---|
id | The id of the delivery. A retry of the same delivery carries the same id, so you can use it to skip a delivery you have already handled. A new trigger, or sending the lead again with Add to webhook, is a new delivery with a new id. |
type | What happened. See the event types below. |
createdAt | When the delivery was created, as an ISO 8601 time in UTC. The request itself can follow a few seconds later. |
webhookId | The id of the webhook that sent it. |
list | The id and name of the list the lead belongs to. |
data | The lead, with the same fields as in Version 1 (and as in a list export). In rare cases, when the lead can no longer be exported, data is null. |
Event types:
type | When it is sent |
|---|---|
lead.qualified | The list's trigger is All found leads. |
lead.found | The trigger is All leads (Found & Unsure), or the trigger is All leads including not found and the lead is found or unsure. |
lead.not_found | The trigger is All leads including not found and the lead is not found (any other lead). |
lead.assigned | The trigger is When assigned. |
lead.replied | The trigger is When lead replied. |
lead.manual_send | You sent the lead yourself with Add to webhook. |
The type is read when the delivery is sent. If a lead's status changes while a delivery is being retried, a retry can carry another type under the same id.
A webhook only sends leads for the lists you attach it to. The Lists column of the webhooks table shows every list a webhook is attached to, with the trigger set for that list, for example "When assigned". Click a list name to open that list's settings.
The deliveries of every new webhook are signed with a secret that only you and Signalist know, so your receiver can check that a request came from Signalist. The Signing column of the webhooks table shows Signed, or Secret not yet viewed for a webhook created before signing was introduced (before 14 October 2026). The row menu (More actions) has Send test event, Rotate secret and, for those older webhooks, Reveal secret once.
An older webhook that shows Secret not yet viewed keeps delivering as before: unsigned, without the check for private addresses, and with redirects followed. It switches to signed delivery, with the address check and without redirects, when you choose Reveal secret once or Rotate secret, or change its URL. It never switches back. New webhooks are signed from the start.
How to check a signature, how to rotate the secret and what a test event does: Webhook signatures. Checking the signature is optional; your receiver keeps working without it.
Signalist retries a delivery when your endpoint does not answer or replies with a temporary error (408, 429, or 5xx): after 1 minute, 10 minutes, 1 hour, 6 hours, and 24 hours. Signalist waits up to 180 seconds for an answer; if none has arrived by then, the attempt counts as a failure that is retried, and the Status column shows "No complete answer within 180 seconds". Any other error is final.
Because a delivery can be retried, your endpoint may receive the same lead twice. With Version 2, skip a delivery whose id you have already handled. With Version 1 there is no id, so match on the lead's email or LinkedIn URL.
Signalist never sends a signed delivery (see "Signed deliveries" above) to a private or internal address: a URL on localhost, a loopback address such as 127.0.0.1, a private network such as 10.x or 192.168.x, a link-local address such as 169.254.x, or a name that points to one of them. Such a webhook cannot receive leads. An older webhook that still shows Secret not yet viewed is delivered as before, without this check, until it switches to signed delivery.
To fix it, open the webhook for editing, click Replace URL and paste a public URL that your receiver answers on.
A signed webhook does not follow redirects. If your URL answers with a redirect (301, 302 and so on), the delivery ends as failed with "302 Found: redirects are not followed, use the final URL", and nothing is sent to the address it points to. Use the final URL in the webhook instead. An older webhook that still shows Secret not yet viewed follows redirects as before; if you switch it to signed delivery, replace a redirecting URL with the final URL first.
Every webhook has a Deliveries page. Open Integrations → Webhooks, find your webhook, then click View deliveries in the Status column or Deliveries in its row menu.
You need the same rights as for managing webhooks and access to Integrations. You cannot see or resend deliveries from a colleague's private list.
The page keeps deliveries for 90 days. Deliveries before 15 Oct 2026 were not recorded. Filter with Status, From and To.
| Column | What it shows |
|---|---|
| Time | When the delivery was created. |
| Lead | The lead sent to the webhook. |
| Trigger | What caused the lead to be sent, using the same labels as the list settings. |
| Status | The delivery's current state. |
| Attempts | The number of delivery attempts. |
| Last HTTP status | The receiver's latest HTTP status code. |
| Response excerpt | A short part of the receiver's answer. |
Open a row to see its attempts and the receiver's last answer. The excerpt is the receiver's answer, not a copy of the lead data sent.
Deliveries still Retrying, leads removed from the list or deleted, and deliveries already delivered by a later redelivery are skipped. The dialog shows the counts and reasons.

A redelivery keeps the original delivery ID, so your receiver can drop duplicates it has already processed. It rebuilds the payload from the lead's current data and uses the webhook's current signing settings and secret.
A redelivery to a signed webhook is marked as one: it carries the header X-Signalist-Redelivery: true, and a Version 2 delivery also has the field "redelivery": true. A legacy webhook created before 14 Oct 2026 that has not switched to signing resends exactly like its normal deliveries, unsigned and without these marks.
A redelivery counts as one attempt. If it fails, the normal retry rules apply; see "When deliveries fail" above.
Each redelivery can include at most 500 deliveries, sent at most 5 per second. If more than 500 are selected, choose a shorter date range. Only one redelivery can run at a time for each webhook; wait for it to finish before starting another.
A paused webhook resends nothing. The page says: "Nothing was redelivered. The webhook is paused. Resume it to redeliver. No deliveries were changed."
Click Resume on the webhook, then try the redelivery again.

? show as •••, for example https://hooks.example.com/services/••• or https://example.com/hook?token=•••&env=•••. A URL without a secret shows in full.•••) is not saved: you see "This address still contains the hidden part (•••). Paste the full webhook address."The MCP Server lets an AI assistant such as Claude work with your Signalist data. There is no key to paste: the assistant opens a Signalist page, Connect an AI application, where you click Connect. It then acts as you, with your permissions. It can also send messages and LinkedIn invitations and start campaigns on your behalf. It asks for your approval before each send or campaign start, messages and invitations it queues wait in an undo window in which you can cancel them, and the sender's daily sending limits apply; some sends can go over them only with your approval.
The assistant can also answer questions about your results and what needs attention, for example "How did my campaigns do last month?" It reads:
These figures come from the same calculation as the app, so they match the Analytics page for the same filters. As in the app, the Analytics figures need access to Analytics.
The assistant can also hide an issue from your Dashboard when you do not want to be reminded of it, and bring it back later. Ask it to dismiss or restore an issue it has read from your Dashboard, for example "Dismiss the competitors review notice."
Most dismissals apply to you only. Some issues belong to the whole workspace, so dismissing one hides it for everyone in your company, and the assistant says which kind it is: low credits, competitors that need review, a missing owner for HubSpot notes, a missing owner privilege in Dynamics, a CRM that needs to be reconnected, and a Zoho LinkedIn field that cannot be searched. A low-credits notice comes back the next time the Dashboard checks your credits, so dismissing it does not keep it hidden for long. As in the app, you need access to Lists. Nothing is deleted or changed except whether the issue is shown, and you can restore it at any time.
The assistant can also create a list for you, from these sources:
As in the app, you need access to Lists and to the source. Creating the list costs nothing and starts no run: the new list is created paused, and you start its first run in the app, which checks the setup first. A run then costs credits as it does when you create the list in the app.
The assistant can add entries to one of your trackers. As in the app, you need access to Trackers. One request adds one kind of entry, up to 100 at a time:
acme.com). A company Signalist already knows is added at once; any other is added as a pending entry that the tracker's next scheduled run looks up. Values that are not a company URL or domain are reported as invalid.The assistant answers with a report: how many entries were added, how many the tracker already had (skipped), and how many were invalid or could not be added. Repeating a request adds nothing twice. As in the app, a newly tracked company is scored and becomes part of the tracker's recurring signal scan.
To disconnect, go to Personal settings → Connected Accounts → Connected AI applications and click Disconnect. MCP access is enabled per workspace; if you see "MCP access is not enabled for your company", contact your Signalist contact.
| Problem | What to do |
|---|---|
| An API request is rejected | Check that the key is sent in the api-key header and has not been revoked. |
| A webhook shows Failing | Check that the URL is reachable and answers with a 2xx status. |
| A webhook is Paused | Fix or replace the URL, then press Resume. Leads that failed are not resent automatically. Once it runs again, you can resend them from the webhook's Deliveries page (see "See and resend deliveries (Deliveries page)"). If the reason reads "Not sent: the URL points to a private network address", replace the URL with a public one. |
| My receiver was down and missed leads | Open the webhook's Deliveries page and use Redeliver all failed (N)… to resend given-up deliveries. Check the count and skip reasons before confirming. |
| A delivery shows "Not sent: the URL points to a private network address" | The URL is on localhost, a private network or a link-local address, or a name that points to one. Open the webhook for editing, click Replace URL and paste a public URL. |
| "This URL points to a private network address, which cannot receive webhooks. Use a public URL." | Webhooks can only go to public addresses. Use the public URL of your receiver. |
| "302 Found: redirects are not followed, use the final URL" | Your URL answers with a redirect. Use the address the redirect points to as the webhook URL. |
| A webhook shows Not attached to any list | It receives nothing automatically. Attach it in a list's settings under Advanced settings → Send leads to a webhook. |
| "This address still contains the hidden part (•••)" | The table hides the secret in a URL. Click Replace URL and paste the complete URL, or leave the URL unchanged. |
| The same lead arrives twice | A delivery was retried, or the lead was sent again by hand or by another trigger. With Version 2, compare the id: the same id is a retry, a different id is a new delivery. With Version 1, match on the lead's email or LinkedIn URL. |
| My endpoint cannot read the body | Version 1 sends an array that holds the lead; Version 2 sends one object with the lead under data. Open the webhook for editing and pick the Payload format your endpoint expects. |
| I cannot tell new leads from replies on one endpoint | Use Version 2 and read type (for example lead.found or lead.replied). Version 1 has no event type. |
| The deliveries of an older webhook carry no signature | The webhook shows Secret not yet viewed and delivers as before. Choose Reveal secret once or Rotate secret in the row menu, or replace its URL. From then on its deliveries are signed. See Webhook signatures. |
| I lost the signing secret, or the signature does not match | See Webhook signatures: Rotate secret gives a new one, and the signature is computed over the raw request body. |
| A key was shared by mistake | Revoke it now and create a new one. |
| The AI assistant cannot read Analytics figures | Check that your role has access to Analytics in Signalist. |
| The AI assistant cannot dismiss or restore a dashboard issue | Check that your role has access to Lists, and ask the assistant to read your Dashboard issues first so it uses an issue that exists. |
| The AI assistant cannot create a list from a source | Check that your role has access to Lists and to that source, and that a LinkedIn account (with Sales Navigator for Sales Navigator lists) is connected. |
| The AI assistant cannot add the leads of a list to a tracker | Check that the list has at most 100 leads, is not a colleague's private list, and that the tracker has a list behind it. |
Compare the same period, list, sender, channel, and campaign before drawing conclusions from activity and replies.
Your contacts and companies live in two places in the sidebar:
Zoho CRM and Pipedrive are available in every workspace. This article covers the steps and settings that are specific to them. For how syncing, field mapping, and owners work in general, see Plan CRM sync and field mapping.