n8n-nodes-mightycall

Community node package for integrating n8n with the MightyCall API.

This repository ships one custom n8n node, one credential type, compiled runtime files under dist/, and documentation for the live workflow compatibility contract.

Install | Credentials | Repository Structure | Build Semantics | Runtime Semantics | Compatibility Contract | Operations | Validation

Install

n8n Community Nodes

In n8n:

1. Go to Settings > Community Nodes.
2. Select Install a community node.
3. Enter n8n-nodes-mightycall.
4. Install and restart n8n.

Manual Install

npm install n8n-nodes-mightycall

For repository development:

npm install
npm run build

Credentials

Credential type: mightyCallApi

Defined in credentials/MightyCallApi.credentials.ts.

| Field | Purpose | | --- | --- | | Account Type | Standard or Contact Center; controls API base URL and route casing | | API Key | MightyCall API key | | Authentication Method | User Key or Extension Number | | User Key | Secret key used as client_secret when selected | | Extension Number | Extension used as client_secret when selected |

Repository Structure

Important tracked files and runtime outputs:

• README.md
• LICENSE
• package.json
• package-lock.json
• tsconfig.json
• gulpfile.js
• credentials/MightyCallApi.credentials.ts
• credentials/mightycall.svg
• nodes/MightyCall.node.ts
• nodes/README.md
• nodes/mightycall.svg
• dist/credentials/MightyCallApi.credentials.js
• dist/credentials/MightyCallApi.credentials.d.ts
• dist/credentials/mightycall.svg
• dist/nodes/MightyCall.node.js
• dist/nodes/MightyCall.node.d.ts
• dist/nodes/mightycall.svg
• docs/BUILD_AND_RELEASE.md
• docs/WORKFLOW_COMPATIBILITY.md

Build Semantics

Build command:

npm run build

Current build script:

node ./node_modules/typescript/bin/tsc && node ./node_modules/gulp/bin/gulp.js build:icons && node ./node_modules/gulp/bin/gulp.js build:node-icons

Development watch script:

node ./node_modules/typescript/bin/tsc --watch

The scripts call package entrypoints directly instead of relying on node_modules/.bin shims where possible. This keeps builds reliable on mounted shares where npm bin symlinks can be materialized as plain files.

Package manifest semantics:

| Field | Current value | | --- | --- | | Package | n8n-nodes-mightycall | | Runtime node entry | dist/nodes/MightyCall.node.js | | Runtime credential entry | dist/credentials/MightyCallApi.credentials.js | | Source node | nodes/MightyCall.node.ts | | Source credential | credentials/MightyCallApi.credentials.ts | | Icon | file:mightycall.svg |

More detail: Build and Release.

Runtime Semantics

The node executes one n8n input item at a time.

1. Reads account type, API key, and selected client secret from mightyCallApi credentials.
2. Uses https://api.mightycall.com/v4 for standard accounts and https://ccapi.mightycall.com/v4 for Contact Center accounts.
3. Requests an OAuth access token from /auth/token using client_credentials.
4. Sends API requests with Authorization: Bearer <token>; some endpoints also require x-api-key.
5. Uses the Swagger-documented route family for each resource. Communication and Interaction are standard-host routes that require a tenant with Contact Center features; Contact Center Contact supports the matching standard-host /contactCenter/... and ccapi /contactcenter/... route casing.

Compatibility Contract

This node is used by saved workflows in the live n8n instance. Backward compatibility includes node identity, declared versions, resource values, operation values, parameter names, icon loading, and editor hydration.

| Field | Value | | --- | --- | | Display name | MightyCall | | Internal node name | mightyCall | | Runtime workflow type | n8n-nodes-mightycall.mightyCall | | Declared versions | [1, 2, 2.1, 3, 10] | | Credential type | mightyCallApi | | Saved workflow usage | 11 saved MightyCall nodes currently use typeVersion 10 in the live n8n database. |

Do not change these values without a saved-workflow migration and browser/editor validation.

More detail: Workflow Compatibility.

Operations

The node currently exposes 14 resources and 77 operation values.

| Resource Display | Resource Value | Operations | | --- | --- | --- | | Call | call | getAll, getActive, getById, make, hangUp | | Contact | contact | getAll, getById, create, update, patch, delete, deleteBulk, getTags, getLimits, addChannel, updateChannel, patchChannel, deleteChannel, addTags | | Contact Center Contact | contactCenterContact | getAll, getById, createBrief, createFull, update, patch, delete, import, exportCsv, searchAuto, deleteByTag, removeCrmInfo, deleteInternal, markMessagesRead, addChannel, updateChannel, patchChannel, deleteChannel | | Journal | journal | getAll, getCount, getById, deleteMessages, addComment, deleteComment, deleteVoicemail, setWorkflowState, setFlags, removeFlags, getBlockListCount, getVipListCount, addToBlockList, removeFromBlockList, restoreMessage, getMessageAttachments | | Voicemail | voicemail | getAll, get | | Business Number | businessNumber | getAll, getWithOptions, get, delete | | User | user | getStatus, setStatus, getInfo | | Message | message | send, sendContactCenter, getAll | | Team | team | get | | Profile | profile | get, getByExtension, getStatus, setStatus | | Ping | ping | ping | | API Request | apiRequest | make | | Communication (Contact Center Only) | communication | getAll, addComment, deleteComment, deleteVoicemails | | Interaction (Contact Center Only) | interaction | getAll |

Service Notes

• Communication and Interaction are Contact Center feature routes in the standard Swagger host; configure the credential as Standard Account for those resources unless MightyCall documents otherwise for your tenant.
• Do not merge standard and Contact Center base URLs; accountType selects the default API host, while route-specific operations preserve the documented path casing.
• API Request is an authenticated escape hatch under /v4/api; the same accountType switch selects the standard or Contact Center host.
• message/getAll is implemented through GET /journal/requests with type=Message and state=Message, because MightyCall does not expose a dedicated GET /messages route in the official Swagger.
• Legacy saved workflow parameters contactData and filters.date_from / filters.date_to are preserved for existing workflows.
• Several write operations mutate calls, contacts, messages, journal flags, and workflow state; validate editor hydration before live execution.

Validation

Minimum local validation:

npm run build

Minimum live validation after deployment:

1. Confirm n8n health is green.
2. Confirm n8n is loading the intended package commit.
3. Confirm the public icon route returns SVG.
4. Query saved workflows for n8n-nodes-mightycall.mightyCall nodes.
5. Validate saved typeVersion values against declared versions.
6. Validate saved resource and operation values against current option lists.
7. Open representative workflows in the n8n editor and verify icon, subtitle, resource, operation, and required fields.

Do not skip browser/editor validation after large node builds.

Related Docs

• Build and Release
• Workflow Compatibility
• Node-local notes
• GitHub repository
• n8n community nodes documentation

License

See the repository license file.