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

Famulor on n8n

Open the official n8n integration listing and setup instructions.

n8n-nodes-famulor on npm

View the package and releases for self-hosted n8n installations.
The connector source and release notes are available on GitHub. Version 2.5.0 adds the optional replace_payment_id field to Create Platform Custom Payment. Use it to replace an unused payment link in the same customer workspace.

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.3.0 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. With version 2.7.0, Bookings → Permanently delete bookings accepts the IDs of ended or canceled native bookings. Review the IDs before running the action. The result lists deleted and skipped IDs separately. With version 2.9.0, Campaigns → Launch a campaign starts a draft campaign now or at a set start_at. Set compliance_attestation to true to confirm that the campaign follows all laws and consent rules for its contacts, and map sequence_hash unchanged from Get a campaign to stop the launch if the call sequence changed. Pause a campaign, Resume a campaign, Cancel a campaign’s schedule and Get campaign analytics are also available, as well as app action tools, US do-not-call checks and Cal.com accounts and event types. Saved Start a campaign nodes keep sending no body. 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.

Legacy manual receivers

Saved version-2 and version-3 webhook nodes keep their parameters and manual registration mode. New action nodes use version 3; new webhook nodes use version 4 with automatic registration. To migrate a trigger, add a workspace API key and signing secret to the webhook credential, then select Automatic Subscription. Keep existing credentials until dependent workflows have been updated. Legacy manual receivers

Existing workflows

Saved version-2 and version-3 webhook nodes keep their parameters and manual registration mode. New action nodes use version 3; new webhook nodes use version 4 with automatic registration. To migrate a trigger, add a workspace API key and signing secret to the webhook credential, then select Automatic Subscription. Keep existing credentials until 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

Shopify theme widget choices

With connector 2.3.0 or later, choose Shopify → Read Shopify widget choices or Shopify → Synchronize Shopify widget choices and select the linked store. These actions are included in the 485 native actions described above. Public name publication is off by default. Synchronizing explicitly enables it and publishes eligible names as public Shopify storefront data, without an additional Shopify permission request. Subsequent background updates preserve that opt-in. Select the widget and save the theme in Shopify. Synchronization does not activate a theme. To turn publication off, use the capabilities configuration described in the Shopify app guide. Both actions require workspace owner/admin access and Assistants: Read. Reading also needs Integrations: Read; synchronization needs Integrations: Write. If your installed connector lacks these actions, use the HTTP Request node with the same stored Header Auth credential: The POST has no body. The equivalent CLI commands are famulor get-shopify-widget-picker STORE_ID and famulor synchronize-shopify-widget-picker STORE_ID. See the Shopify app guide for the matching MCP tools and SDK methods. The store dropdown also requires Integrations: Read. Use By ID when your synchronization credential has only write access to integrations.

Private AI Avatars

Use Avatars to read the creation price, prepare a photo upload, submit it with explicit consent and check its status. Creation and deletion require a user-owned workspace API key. Upload the photo bytes to the returned signed URL with an HTTP Request node, using no Famulor credentials for that upload. Reuse the same avatar ID after an uncertain response. The one-time creation fee is separate from ongoing usage; a saved Auto-Topup rule may apply. See AI Avatar for the complete API, CLI and SDK workflow.

Signed webhook subscriptions

New Famulor Trigger nodes in package 2.3.0 use automatic registration. Add the workspace API key and your signing secret to Famulor Webhook API credentials, select one event and activate the workflow. Deactivation removes only that node’s subscription. Saved version-2/3 nodes keep manual setup unless you explicitly select Automatic Subscription. Existing assistant, connector and booking destinations remain unchanged. Signed webhook subscriptions

Company senders and RCS

With community package 2.6.0 or later, the SMS resource adds company sender applications, status refresh, brand asset uploads and sending from an SMS connection. Existing Send SMS nodes retain their number field; delivery mode, rich content and fallback text are optional. Send SMS from a connection also supports a company sender without a number. SMS conversation events include RCS activity. Update the package after this release is available; npm distribution and n8n directory approval are separate. In 2.8.0, use List company senders for SMS and RCS to see the available recipient countries, the workspace suggestion and countries pending setup. Enter one or more available country codes in the Countries field when drafting or updating an application. Book company sender setup can also take the reviewed draft’s update time to guard against concurrent edits.