aircall-community

Open-source n8n community node for the Aircall Public API (calls, contacts, numbers, messages, teams, tags, and users)

Package Information

Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.2
Author: Artur Litau

Documentation

n8n-nodes-aircall-community

Open-source (unofficial) n8n community node for the Aircall Public API.

It provides declarative-style operations for core Aircall resources like calls, contacts, numbers, messages, teams, tags, and users, plus a Custom API Request mode for advanced endpoints.

Implementation style: declarative-style node (routing-based, no custom execute() request orchestration).

Features

  • Aircall API credential (API ID + API Token via HTTP Basic Auth)
  • Calls resource
    • Get
    • Get Many
    • Search
  • Contacts resource
    • Create
    • Get
    • Get Many
    • Update
    • Delete
  • Messages resource
    • Send
    • Send in Agent Conversation
  • Numbers resource
    • Check Message Configuration
    • Create Message Configuration
    • Get Message Configuration
    • Delete Message Configuration
    • Get
    • Get Many
    • Get Registration Status
  • Tags resource
    • Create
    • Get
    • Get Many
    • Update
    • Delete
  • Teams resource
    • Create
    • Get
    • Get Many
    • Delete
    • Add User
    • Remove User
  • Users resource (v2 endpoints)
    • Get
    • Get Many
  • Custom API Request resource for unsupported endpoints

Installation

npm install n8n-nodes-aircall-community

Development

npm install
npm run dev

Credentials

Create an Aircall API credential in n8n and provide:

  • API ID
  • API Token

The credential test uses GET /v1/ping.

Notes

  • This node currently uses:
    • /v1/calls
    • /v1/contacts
    • /v1/numbers
    • /v1/numbers/:id/messages/*
    • /v1/tags
    • /v1/teams
    • /v2/users
  • Contact updates use POST /v1/contacts/:id per Aircall API reference.
  • Contact create validation enforces Aircall constraints for phone_numbers and email/phone entry shapes.
  • Contact and call search use Aircall-supported structured filters (not generic free-text q) to avoid confusing false matches.
  • For fields not exposed in the UI yet, use Custom API Request.

License

MIT

Discussion