Facebook Pixel
Agentic CRM

Webhooks and integrations

How to get data out of the ConnectSafely Agentic CRM and into HubSpot, a spreadsheet or your own tools, including Agentic CRM webhooks and their events.

This page covers moving CRM data to other tools, and bringing outside events into the CRM.

Which one do I need?

I want toUse
Send people to HubSpotSend to another CRM
Open my CRM in a spreadsheetCSV export
Be told when something changes in the CRMAgentic CRM webhooks
React when a LinkedIn message arrivesMessage webhooks
Load or catch up on CRM changesThe CRM API, with updatedSince
Add people from a form or another appThe CRM API, from that app's HTTP step
Let an AI assistant do itMCP

Send people to HubSpot

HubSpot is the CRM you can send people to today. Salesforce, Pipedrive, Zoho CRM and Close are listed in the app as coming soon.

  1. In the CRM, select the people you want to send.
  2. Click Send to another CRM in the bar that appears.
  3. In the panel, click HubSpot. If it says Not connected, click Connect and approve the access in HubSpot first.

What happens:

  • Each person is added to HubSpot as a contact. People are matched by email, or by LinkedIn URL when there is no email.
  • When it finishes, the panel shows how many were synced, skipped and failed. People with no email and no LinkedIn URL are skipped.
  • An email that is still masked in ConnectSafely is not sent.
  • One send handles up to 1,000 people. For a bigger selection, the panel asks you to choose: send everyone in batches of 1,000, or send the first 1,000 now. A batched send shows its progress in the corner, and you need to keep the tab open until it finishes.

Only the workspace owner can disconnect HubSpot. The HubSpot guide covers the HubSpot side.

CSV export

There are two ways to export.

  • Select people, then click Export CSV in the bar. This exports your selection.
  • Open the ⋯ menu and choose Export to CSV. This exports everyone who matches the filters on screen.

The file is named leads-export- followed by the date. It has these columns: linkedinUrl, firstName, lastName, email, company, headline and location.

One export holds up to 50,000 people. Emails that are still masked in ConnectSafely are left blank.

Webhooks

A webhook is a URL on your server that ConnectSafely calls when something happens. Agentic CRM webhooks are included free.

Add a webhook

  1. Open Agentic CRM → Webhooks in the app.
  2. Click Create Webhook.
  3. Fill in Webhook Name and Webhook URL, then choose Agentic CRM events as the Event Type.
  4. Under Agentic CRM Events, tick what this webhook should be told about. Everything is ticked to start with.
  5. Click Create Webhook. The next screen shows the webhook secret once. Copy it and keep it safe.
  6. Back on the list, click Test to check your server receives a call.

One webhook can listen to several events, and you can change which ones later with Edit. Bulk summaries are their own event, so keep A bulk action changes many people ticked if you want them. On the list you can turn a webhook on or off, Edit it, Delete it, and open Logs to see every attempt and how your server answered.

The same page also holds webhooks for LinkedIn messages and connections. Those appear in the Event Type list under LinkedIn and need the API plan. On a free account they are shown but cannot be picked.

The events

EventSent when
prospect.createdA person is added, by hand, through the API, by import or by sync
prospect.stage_changedA person's stage changes
prospect.owner_changedA person is assigned or unassigned
prospect.tags_changedA person's tags change
prospect.deal_changedA deal value or close date changes
prospect.outcome_changedA deal is won, lost or reopened
prospect.deletedA person is deleted
note.createdA note is added
reminder.setA follow-up is set or moved
reminder.dueA follow-up comes due
prospects.bulk_changedA bulk action changed many people at once

What your server receives

{
  "id": "6737a1c09b1e8a0012ab9f01",
  "event": "prospect.stage_changed",
  "object": "event",
  "data": {
    "workspace_id": "665f19009b1e8a0012ab0000",
    "occurred_at": "2026-11-15T10:00:00.000Z",
    "source": "manual",
    "prospect": {
      "id": "665f1c2e9b1e8a0012ab34cd",
      "name": "Jane Doe",
      "company": "Acme",
      "linkedinUrl": "https://www.linkedin.com/in/jane-doe",
      "stageId": "665f1b7a9b1e8a0012ab3401",
      "stageName": "Interested",
      "ownerUserId": null,
      "tags": ["webinar"],
      "dealValue": 5000,
      "expectedCloseAt": null,
      "outcome": null
    },
    "changes": {
      "stageId": { "from": null, "fromName": "New", "to": "665f1b7a9b1e8a0012ab3401", "toName": "Interested" }
    }
  }
}
FieldNotes
prospectThe person after the change. It has no email. Call GET /prospects/{id} if you need the full record.
changesWhat changed, with the value before and after. Tags list what was added and removed.
sourceOnly on prospect.created and prospect.stage_changed. manual means a person or the API did it. automation means ConnectSafely did it, such as a campaign step or the sync.
noteOn note.created: the note's id, kind, body and authorUserId.
reminderOn reminder.set and reminder.due: dueAt, note and userId.

Bulk actions send one event

Moving, assigning, tagging or deleting many people at once sends one prospects.bulk_changed event, not one call per person. A change that touches 20 people or fewer in one go is still sent person by person.

{
  "id": "6737a1c09b1e8a0012ab9f02",
  "event": "prospects.bulk_changed",
  "object": "event",
  "data": {
    "workspace_id": "665f19009b1e8a0012ab0000",
    "occurred_at": "2026-11-15T10:00:00.000Z",
    "action": "updated",
    "count": 2250,
    "changes": { "stageId": "665f1b7a9b1e8a0012ab3401", "stageName": "Interested" }
  }
}

action is updated or deleted. The same summary is used when more than 100 events of one kind happen close together, such as a large import. In that case action is the event name, for example prospect.created, and count is how many there were. Use the CRM API with updatedSince to fetch the people themselves.

Delivery

  • Events are sent within a few seconds of the change.
  • Your server has 15 seconds to answer with a 2xx status. If it does not, the call is tried up to 3 times in total, with a growing wait between tries.
  • Every call carries X-Webhook-Event, X-Webhook-Timestamp and X-Webhook-Signature. The signature is sha256= followed by an HMAC of the body with the webhook's signing secret. Use the secret you copied when you created the webhook, and check it as shown in Webhook security.
  • The same event can occasionally be sent twice. Every event has an id that stays the same on a repeat, so you can skip one you have already handled.
  • An event that could not be sent within 24 hours is dropped.
  • If your webhook updates the CRM through the API, that update sends another event. Check changes before acting so you do not loop.

Message webhooks are separate

The message webhooks send message.received when a LinkedIn message or InMail arrives. They are set up on the same page and need the API plan. Agentic CRM webhooks do not.

Keep another system in step

Webhooks tell you the moment something changes. To catch up after downtime, or to load everything once, ask the API what changed since you last looked.

  1. Save the time of your last sync.
  2. Call GET /prospects?updatedSince=THAT_TIME.
  3. Follow nextCursor until hasMore is false.
  4. Save the new time.
curl "https://api.connectsafely.ai/crm/prospects?updatedSince=2026-11-14T00:00:00Z&limit=200" \
  -H "Authorization: Bearer YOUR_API_KEY"

Each person in the response carries their current stage, tags, owner, deal value and outcome. The CRM API page lists every field.

Add people from another app

Any tool that can send an HTTP request can add a person to your CRM. That covers automation tools such as n8n, Make and Zapier, form builders with a webhook option, and your own code.

SettingValue
URLhttps://api.connectsafely.ai/crm/prospects
MethodPOST
HeaderAuthorization: Bearer YOUR_API_KEY
HeaderContent-Type: application/json
Body{ "email": "maria@acme.com", "name": "Maria Lopez", "tags": ["form"] }

The body needs an email or a linkedinUrl. Sending the same person twice is safe. The second call returns the existing record and does not make a copy.

ConnectSafely also has guides for n8n, Make and Zapier. Those guides cover LinkedIn actions. For CRM calls, use the tool's HTTP request step with the settings above.

Your API key

The CRM API calls on this page use your API key. Webhooks, HubSpot and CSV export do not. Get it from the API Key page.

Click Regenerate on that page to make a new key. The old key stops working straight away, so update everything that uses it. Members of a workspace share the workspace owner's key, and only the owner can regenerate it.

On this page