Overview
This node is a trigger that activates workflows when a phone call ends in the Famulor system. It listens for webhook events indicating the end of a call and then passes the call data to subsequent workflow nodes. This is useful for automating post-call processes such as logging call details, updating CRM records, sending follow-up messages, or triggering notifications.
A practical example would be automatically creating a support ticket or sending a summary email after a customer service call finishes.
Important: The webhook URL generated by this node must be manually registered in the Famulor dashboard under the assistant settings. n8n does not register the webhook automatically.
Properties
| Name | Meaning |
|---|---|
| Assistant Name or ID | Select an assistant from the list or specify its ID using an expression. This determines which assistant's call ended events will trigger the workflow. |
Output
The node outputs JSON data representing the payload received from the Famulor webhook when a call ends. This JSON contains all relevant information about the ended call, such as caller details, call duration, timestamps, and any other metadata provided by Famulor.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authentication with the Famulor API.
- The user must manually configure the webhook URL in the Famulor assistant settings to enable event delivery.
- Internet access to reach
https://app.famulor.de/api/user/assistantsfor loading assistants and receiving webhook calls.
Troubleshooting
- Webhook Not Triggering: Ensure the webhook URL is correctly registered in the Famulor dashboard under the correct assistant’s settings. Without this, no events will be sent.
- Failed to Load Assistants: If the node cannot load assistants, verify that the API key credential is valid and has sufficient permissions. Also, check for network connectivity issues.
- Rate Limiting Errors (429): The node implements retry logic with exponential backoff if the API rate limits requests. Persistent 429 errors may require reducing request frequency or contacting Famulor support.
- Invalid Response Format: If the response from the API is not an array as expected, it could indicate an API change or temporary issue. Check the Famulor API status and update the node if necessary.
Links and References
- Famulor Dashboard – For managing assistants and registering webhooks.
- n8n Expressions Documentation – For using expressions to specify dynamic assistant IDs.