A webhook tells another system the moment something happens in Alsona. When a prospect accepts an invite or sends a reply, Alsona posts the details to a URL you choose, and whatever sits at that URL can react immediately.
This is how you get Alsona events into a CRM, a Slack channel, a spreadsheet, an automation tool, or your own code, without anyone watching the inbox.
Webhooks or the API
Alsona gives you both, and they solve different problems.
| Webhooks | The API |
Direction | Alsona pushes to you | You pull from Alsona |
Timing | The moment it happens | Whenever you ask |
Good for | Alerts, live CRM updates, anything time-sensitive | Reporting, bulk changes, reading data on a schedule |
Setup | Paste a URL, no code needed on our side | Generate a key and write requests |
Most working setups use both. The webhook tells you something happened, then an API call fetches the detail.
The four events
Alsona can fire on four things.
Event | Fires when | Typically used for |
When LinkedIn invite accepted | A prospect accepts a connection request | Creating or updating a CRM contact the moment the relationship exists |
When LinkedIn profile invited | An invite is sent to a profile | Logging outbound activity, keeping a system of record in step |
When LinkedIn profile replied | A prospect replies on LinkedIn | Alerting a rep so a warm reply does not sit unread |
When email replied | An email receives a reply | The same, for the email channel |
Each event has its own URL field, so you can send them all to one place or split them across four different destinations.
Setting one up
Click your account name at the bottom left and choose Integrations.
Find the Webhooks card and click Manage.
Paste your URL into the field for the event you want.
Switch that event's toggle on.
Click Test to send a sample payload straight away.
Click Save.
Always use Test before you rely on it. It confirms the URL is reachable and gives the receiving system a real sample to work from. Building against a sample you have actually received is far more reliable than building against fields you assumed would be there.
The URL field validates the format, so a typo in the protocol will be rejected before you can save. It will not tell you whether the URL is the right one, only that it looks like a URL.
Webhooks are set per account. If you run several accounts, each one needs its own configuration.
Where to point them
Zapier
In Zapier, create a Zap and choose Webhooks by Zapier as the trigger.
Choose Catch Hook as the event.
Copy the custom URL Zapier gives you.
Paste it into the matching field in Alsona, toggle the event on, and click Test.
Back in Zapier, the test payload will be waiting. Every field it received becomes something you can map into later steps.
From there, add whatever action you want: a Slack message, a row in Google Sheets, a record in your CRM. Webhooks by Zapier is included on paid Zapier plans, so check yours before you start.
There is no Alsona app in Zapier's directory yet. Webhooks by Zapier is how you connect the two today, and it is how a lot of Zapier integrations work.
Make, n8n, and similar tools
The same pattern applies. Create a scenario or workflow with a webhook trigger, copy the URL it generates, paste it into Alsona, and hit Test. The tool captures the sample and shows you the fields.
Your own endpoint
If you are writing the receiver yourself, three things matter.
Accept POST requests and respond quickly, ideally with a 200 before you do any real work. Queue the payload and process it afterwards rather than making Alsona wait.
Log the raw body of the first few requests. That is how you learn the exact shape of each event, and it is faster than guessing.
Handle the same event arriving twice. Design the receiver so processing the same payload again does not create a duplicate record.
Slack without any middleware
Slack incoming webhook URLs expect a specific JSON shape, so pointing Alsona straight at one will usually not render properly. Send it through Zapier, Make, or your own small endpoint and format the message there.
Three setups worth building first
Replies to the person who owns the account
Point "When LinkedIn profile replied" and "When email replied" at the same automation, and have it post to a Slack channel or send an email. A warm reply sitting unread is the most expensive thing that happens in outbound, and this is a fifteen-minute fix.
Accepted invites into your CRM
Point "When LinkedIn invite accepted" at your CRM through an automation tool. If your CRM is HubSpot, check the native integration first, because it may already do what you need without a webhook.
An activity log you control
Point "When LinkedIn profile invited" at a spreadsheet or a database table. It gives you a record of outbound activity that lives outside Alsona, which is useful for reporting and for anyone who wants numbers without a login.
Things to know before you rely on them
One URL per event. There is no way to send a single event to two destinations from Alsona, so if you need that, point it at an automation tool and branch there.
There are no custom headers. If your endpoint needs an authentication header, put something in front of it, or use a URL containing a secret token that only you know.
Treat the URL as a secret. Anyone who learns it can send data to your endpoint, so do not paste webhook URLs into tickets, screenshots, or shared documents.
Validate what arrives. Check the payload looks like what you expect before acting on it, rather than trusting anything that reaches the URL.
If you change the destination, test again. A URL that has moved will fail silently from your side, because Alsona has no way to tell you nobody is listening.
Nothing arrives at all. Check the toggle for that event is actually on and that you clicked Save. Both are easy to miss.
Test works but real events do not. The webhook is fine. The event itself may not be happening, so check the agent is running and look at the workflow canvas to see whether that step is executing.
The receiving tool shows an error. Look at that tool's own log first. It will tell you whether the request arrived, which separates a problem on our side from a problem in your automation.
Data arrives but the fields are wrong. Rebuild the mapping from a fresh Test payload rather than from an older sample.
You need the full record, not just the event. Use the API to fetch it. See "How to use the Alsona API".
See also
"How to use the Alsona API" for pulling data on your own schedule.
Your account menu, then Integrations, for native connectors including HubSpot.