Get events in real time and sync them to your tools.
Webhooks let Aloware notify your other systems the moment something happens, so you don't have to poll the API. This page covers setup, authentication, delays, events, filters, saving and testing, with sample payloads at the end.
What a webhook does
An Aloware webhook integration sends event data straight to an outside system such as HubSpot, Zapier, or custom endpoints. Scheduled API checks look for changes on a timer; a webhook fires as soon as the event happens in Aloware.
Example:
A contact is created, and its details are posted to your CRM.
A call gets summarized, and the summary goes to your analytics tool.
You can add authentication, filter what gets sent, and test before you go live.
Why push beats polling
Polling the API over and over to catch new data is slow, wastes resources and can miss updates.
A webhook delivers data when the event occurs instead. Contacts sync right away, call logs stay current and downstream workflows start on their own.
The result: less manual work, more accurate data, and systems that stay in step.
Common uses
Admins typically set up webhooks to automate workflows and keep other platforms current, for example to:
Send every new Aloware contact to HubSpot.
Pass only outbound calls over two minutes to an analytics tool.
Deliver call transcriptions to a documentation system for quality review.
Open webhook settings
Step 1. Sign in to your Aloware admin account.
Step 2. Open the Integrations menu.
Step 3. Choose Webhook Integration.
Step 4. Click + Add Webhook, or open an existing webhook to edit it.
The form that opens holds authentication, delay, event and filter settings.
Authentication
Authentication controls whether your endpoint accepts Aloware's requests. Pick None, Basic, or Bearer Token to match what the endpoint expects:
None : requests go out with no credentials and no authentication mechanism.
Basic : each request includes a username and password, usually base64-encoded in the Authorization header.
Bearer : each request includes a bearer token in the Authorization header.
Delay
Use Delay to wait a set number of seconds before Aloware sends the request to the external service.
Add a delay when you need to:
Let other workflows finish before the webhook fires.
Avoid race conditions or actions that overlap.
Keep data arriving in the right order.
Events
Pick the activities that should send data. In the event list, tick each one you want.
Recommendation: set up a separate webhook for each event type. It's easier to manage and keeps payloads from piling up.
Contact events
Contact created: fires when a contact is added in Aloware and sends its data, so outside systems have it right away.
Contact updated: fires whenever a contact's details change, keeping external records in sync.
Contact disposed: fires when a contact's disposition changes, so you can follow status changes and act fast.
Contact DNC updated: fires as soon as a contact is marked Do Not Contact (DNC) in Aloware.
Communication events
Communication initiated: fires when a communication with a contact starts, so you see new interactions at once.
Communication disposed: fires when a communication's disposition changes, so you can follow outcomes and progress.
Appointment events
Appointment saved: fires once an appointment is saved in Aloware, for calendar updates, follow-ups and planning in other tools.
Call events
Call disposed: fires after a call ends and sends its disposition, useful for analysis and improving strategy.
Voicemail saved: fires when a voicemail is saved, so teams can track it, reply and manage related tasks.
Recording and transcription events
Recording saved: fires when a call recording is saved, giving outside systems the full record for QA, training or compliance.
Transcription saved: fires when a call or communication has been transcribed and the text saved, ready for external processing.
Call summarized: fires when a transcription is summarized and sends the summary content, timestamps and contact details for real-time processing.
Qualified contacts: send only when the conditions are met
Skip lines: ignore events from selected phone lines
Well-chosen filters mean connected platforms get only structured, relevant data, which keeps workflows lean and free of errors.
Saving
There are two ways to save: Save and test webhook or Save without testing.
Save and test webhook
Click Save and test webhook.
Aloware then:
Stores the configuration (URL and selected event type).
Sends a test payload right away to the target system (e.g., HubSpot, Zapier). It holds sample data, never real customer data.
Use the result to check that:
The webhook URL works.
The receiving system accepts the connection.
The integration shows Valid & Active.
Note: some platforms, HubSpot among them, may receive a test payload without the full set of attributes, sometimes only a true/false value. That can break field mapping, which is why Save Without Testing exists.
Save without testing
Click Save Without Testing.
Aloware then:
Stores the configuration (URL and selected event type).
Sends no test payload.
Waits for a real event in Aloware (e.g., a new contact is created, a call transcription is saved) and sends the complete payload to the target system at that point.
Why this helps:
The first real payload has every attribute (IDs, names, contact data, etc.), so you can map fields properly in HubSpot and Zapier.
You avoid the issues that simplified test payloads (like true/false values) cause.
Your workflows run on accurate, real data from the first event.
Note: the webhook reads Untested until its first real event, but it is already active and will trigger workflows.
What users get from it
Admins do the setup, but everyday users feel the benefit. An agent in a contact center no longer updates the CRM by hand after each call, because the details show up on their own. A marketing manager can count on Zapier workflows to send follow-ups without jumping between platforms.
For users, it means information that's always current and in sync.
Checking that a webhook works
Do something ordinary in Aloware, such as editing a contact or saving a call transcription.
Wait for the connected system (HubSpot, Zapier, etc.) to receive the event.
Confirm the workflow or automation there ran as expected.
