Description
n8n-nodes-aloware
This is an n8n community node for Aloware — an AI-powered contact center platform for SMS, voice calls, power dialing and sales outreach.
It lets you react to Aloware events (calls, SMS, AloAi call summaries, contact changes) and call the Aloware API from n8n workflows to place two-legged calls, send SMS/MMS, manage contacts, enroll contacts into sequences, and manage power dialer lists.
Installation
Trigger
Operations
Example use cases
Credentials
Compatibility
Resources
Installation
Follow the community nodes installation guide in the n8n documentation.
In your n8n instance go to Settings → Community Nodes → Install and enter:
n8n-nodes-aloware
> Community nodes run only on self-hosted n8n. They cannot be installed on n8n Cloud.
Trigger
Aloware Trigger starts a workflow when Aloware sends a webhook event: Call disposed,
Communication disposed, Contact created / updated / disposed, Contact DNC updated,
Appointment saved, Voicemail saved, Recording saved, Transcription saved,
Call summarized (AloAi).
Aloware cannot register webhooks over its API, so the setup is manual:
1. Add the trigger to a workflow and copy its Production URL (use the Test URL while building).
2. In Aloware go to Integrations → Webhook Integration → + Add Webhook, paste the URL,
set Authentication to None and tick the events you want.
3. Optionally narrow the trigger to Call Disposed, SMS Disposed, Call Summarized (AloAi)
or Other Events. Empty means every event.
Each delivery becomes one item. By default the {"body": …, "event": …} envelope is flattened
to { event, id, direction, type, disposition_status, duration, contact: {…}, … }; for
transcription.call.summarized the item carries summary, json_summary, transcription,
contact and communication. Turn off Flatten Payload to keep the raw envelope.
Operations
Call
- Make Two-Legged Call — ring an agent (or a ring group) first, then dial the contact by phone number or contact ID from one of your lines. Aloware answers
202 Two legged call established. - Lookup by Phone — find a contact by phone number
- Create or Update — create a new contact or update an existing one by phone number. Update If Contact Exists is on by default; without it Aloware returns
409 Contact already exists. Supports name, email, company, address, lead source, date of birth, timezone, custom fields, tags, list IDs, assigned user, sequence enrollment, Power Dialer placement, ring-group distribution and DNC. - Send — send an SMS or MMS message (supports sending from a phone number or line ID, user-ownership modes, MMS image, force-random, and up to 3 custom fields)
- Get Many — list all Aloware users (agents) in the account (the endpoint has no pagination and always returns every user)
- Enroll Contact — add a contact to an Aloware sequence (identify contact by phone number or by ID from Aloware, HubSpot, Zoho, Guesty, or Pipedrive; optional force enrollment)
- Disenroll Contact — remove a contact from all sequences
- Remove Contact from Lists — remove a contact from every Power Dialer list
- Clear List — remove every contact from a specific Power Dialer list (use the list ID from Aloware Classic; Aloware Talk list numbers are different)
- Clear User Lists — remove every contact from all Power Dialer lists owned by a given user
Contact
SMS
User
Sequence
Power Dialer
Example use cases
Log every AloAi call summary in your CRM
Aloware Trigger (Call Summarized) → HubSpot: Create Engagement
Aloware Trigger
Events: Call Summarized (AloAi)HubSpot – Create Engagement (Note)
Contact: lookup by {{ $json.contact.phone_number }}
Body: {{ $json.summary }}
Call the lead within a minute while a rep is free
HubSpot Trigger → Aloware: Contact – Create or Update → Aloware: Call – Make Two-Legged Call
Call – Make Two-Legged Call
Call On Behalf Of: User (Agent) → pick the rep from the list
Identify Contact By: Phone Number → {{ $json.properties.phone }}
Identify Line By: Phone Number → +18885551234
The rep’s phone rings first; when they answer, Aloware dials the lead and bridges the call.
Text every new CRM lead within seconds
HubSpot Trigger → Aloware: Contact – Create or Update → Aloware: SMS – Send
Push the new lead into Aloware so your agents see it, then send the first touch
immediately instead of waiting for someone to pick up the phone.
Contact – Create or Update
Phone Number: {{ $json.properties.phone }}
Additional Fields:
First Name: {{ $json.properties.firstname }}
Email: {{ $json.properties.email }}
Tags: webform,hot-leadSMS – Send
Send From: Phone Number (From)
From: +18885551234 ← one of your Aloware line numbers
To: {{ $json.properties.phone }}
Message: Hi {{ $json.properties.firstname }}, thanks for reaching out! An agent will call you shortly.
Start a nurture sequence from a website form
n8n Form Trigger → Aloware: Sequence – Enroll Contact
Sequence – Enroll Contact
Sequence ID: 4821
Source: Phone Number
Phone Number: {{ $json.phone }}
Force Enroll: false
Stop messaging a customer once the deal closes
Salesforce Trigger (Opportunity → Closed Won) → Aloware: Sequence – Disenroll Contact
Removes the contact from every active sequence so a new customer never receives
another prospecting message.
Reduce no-shows with an appointment reminder
Schedule Trigger (hourly) → Google Calendar: Get Many → Aloware: SMS – Send
Look up meetings starting in the next hour and text each attendee a confirmation.
Clean up a Power Dialer list after a campaign
Schedule Trigger (nightly) → Aloware: Power Dialer – Clear List
Power Dialer – Clear List
List ID: 1207
Let an AI agent send messages on your behalf
This node sets usableAsTool: true, so it can be attached directly to n8n’s
AI Agent node. Give the agent the Aloware node as a tool and it can look up a
contact and send an SMS as part of its reasoning — no code, no HTTP Request node.
AI Agent → tool: Aloware: SMS – Send
> Tip: numeric fields such as Sequence ID, List ID and User ID come from
> your Aloware account. Run User – Get Many once to discover user IDs, and read
> sequence and list IDs from their URLs in the Aloware UI.
Credentials
You need an API Token from your Aloware account. Generate it from Aloware UI → Integrations → API Tokens.
All requests are sent to the Aloware production API (https://app.aloware.io).
The token is sent automatically with every request (as a query parameter for GET and in the body for POST, matching Aloware’s webhook API convention).
Compatibility
2.23 (trigger and two-legged call verified against the live Aloware API on 2026-09-08)Resources
Aloware API documentation (per resource used by this node):
n8n:
