Skip to main content
The n8n-nodes-famulor community package provides 423 native actions, 32 polling events and five signed webhook event choices for the current Famulor workspace API.

Famulor for n8n

Installation instructions, releases and the connector source.

​
Install and connect

  1. In your self-hosted n8n instance, open Settings → Community Nodes as an owner or administrator.
  2. Install n8n-nodes-famulor, or update the existing package. Use version 2.1.1 or later for the setup described here.
  3. In Famulor, select the workspace to automate and create an API key under Settings → API & MCP. Give it only the scopes your workflow needs.
  4. In n8n, create a Famulor API credential and enter the API key. The host is selected automatically; no Base URL input is needed. Previously saved connection hosts remain supported.
  5. Add a Famulor action or Famulor Polling Trigger and select that credential.
The key determines the workspace. API Access, permissions, feature availability and credits are checked by Famulor. Store the key in n8n credentials; it is shown only once when created.
The n8n directory listing may show a different connector release. n8n Cloud supports verified community nodes; npm installation is available on self-hosted instances. If the installed connector does not offer the native operations below, update it where supported or use the HTTP Request example.
See n8n’s installation guide.

​
Credentials

Personal operations such as Account → Get low-credit warning preferences require a user-owned credential. A service-account key has no associated user, even with all scopes enabled. Manage personal warnings in Famulor Settings when using a service-account key. Account → Get current credential shows the credential type and workspace.

​
Native actions

Add Famulor, choose Resource → Operation, and fill the required fields. Operations cover assistants, calls, campaigns, contacts, phone numbers, SMS, conversations, knowledge, bookings, tools, automations, missions, voices, widgets, settings and workspace administration. For a first read-only test, use Account → Get current credential or Calls → List calls, then add Limit under Optional Fields and set it to 10.
  • Searchable references support From List or By ID. Map IDs from previous nodes when needed.
  • Optional fields are omitted until you add them. Explicit false, 0, empty arrays, empty strings and supported null values are preserved.
  • Lists return one n8n item per record. Use the operation’s limit and offset fields to request further pages. Audio previews return binary data.
  • Each input item executes one request. Writes are not retried automatically. Calls → Start an outbound call, SMS, purchases and other write actions perform real operations and may consume credits.

​
Polling triggers

Add Famulor Polling Trigger, select your Famulor API credential, event and polling schedule. Campaign-lead events also require a campaign ID. The 32 choices cover calls, conversations, contacts, campaigns and leads, assistants, phone numbers, knowledge, tools, automations, missions, segments, suppression, bookings and callbacks. For completed calls use Phone Call Completed; for completed messaging conversations use Conversation Completed. The first active poll establishes a baseline without emitting historical records. Manual tests return recent samples and do not advance the active baseline. A call that was already running when the workflow was activated can still emit completion after it ends. Polling checks observed records and statuses. A transition entirely between polls can be missed. Timestamp-based sources re-read a ten-minute window and deduplicate events; records appearing later than that window can be missed. Use event or resource IDs to make downstream writes idempotent. Large snapshot sources require more API reads; failed or incomplete scans do not advance polling state.

​
Signed booking webhooks

Use Famulor Trigger with Famulor Webhook API credentials for signed deliveries. The event choices are booking.created, booking.cancelled, booking.rescheduled, call.completed and conversation.ended. For bookings:
  1. Select the booking event in the n8n trigger and copy its Production URL.
  2. In Famulor, edit the booking event type and open Advanced → Webhook URL.
  3. Paste the URL and save. When first configured, Famulor shows a generated Webhook signing secret. Copy it into the Webhook Secret field of the n8n credential.
  4. Activate the n8n workflow. Use the Test URL only while n8n is listening for a test event; use the Production URL for an active workflow.
The trigger verifies the signature before returning data. Missing or incorrect signatures return HTTP 401. The selected event must match the delivery. The optional assistant filter applies to call and conversation events.
The assistant Automations → Call completed URL and messaging connector conversation-ended URLs send unsigned events. They cannot use this signed trigger. Use the polling events above for calls and conversations unless you already have a signed delivery configured. There is no workspace-wide Settings → Webhooks page.
The signature does not prevent replay by itself. Deduplicate event or resource IDs before performing downstream writes. The connector never changes Famulor webhook destinations automatically. See n8n’s webhook guide.

​
Existing workflows

Saved version-2 action and webhook nodes keep their definitions and parameters. New nodes use version 3. To migrate, choose the native operation, map its fields and test before activating. For signed triggers, move the signing secret into Famulor Webhook API credentials. Keep existing credentials until all dependent workflows have been updated.

​
HTTP Request alternative

Add an HTTP Request node and select Authentication → Generic Credential Type → Header Auth. Store the header value in a credential. Use the response’s data array in the next step. This request reads calls. See the n8n HTTP Request documentation.

​
Troubleshooting

  • 401: check the saved API key, or the signing secret when using the webhook trigger.
  • 403: check scopes, workspace permissions and feature access. Personal operations also require user-owned credentials.
  • 402: check workspace credits and plan access.
  • No polling output: the initial baseline skips old records; check the selected event and campaign.
  • No webhook output: check the URL, listening or active workflow, selected event and assistant filter.

​
API and CLI

The same call list is available through GET /api/v1/calls and the Famulor CLI:
See the API reference for authentication and operations.

​
More integrations