Problems with integrations
n8n, Make or Zapier receive no data, the workflow doesn't start, fields are missing or an outbound call isn't triggered.
Integrations with n8n, Make, Zapier or your own system run through four routes. First find out which route is affected:
| Route | Direction | Where it's set up |
|---|---|---|
| CRM Ticket after the call | bhomy sends to your system | Tools tab › Automation |
| CRM System during the conversation | the agent calls your system during the call | Tools tab › Tools |
| Incoming Webhook when the phone rings | bhomy fetches context from your system | Personality tab |
| Outbound API | your system starts a call at bhomy | API Key and your tool |
The workflow receives no data after the call
| Possible cause | Solution |
|---|---|
| The webhook URL is wrong or not active | n8n distinguishes between a test URL and a production URL. Use the production URL and activate the workflow |
| Your endpoint doesn't respond with 2xx | Check the list of executions of your workflow to see whether the request arrived and what your workflow responded |
| The endpoint requires authentication | Enter the value in the Authorization Header (optional) field, such as Bearer … |
| Your endpoint takes longer than 10,000 milliseconds | Respond with 200 straight away and process the data afterwards in the workflow. bhomy sends the webhook once per conversation and doesn't retry it |
How to test it: In the CRM Ticket tool, click Test URL. bhomy sends sample data to your URL, and your workflow should receive it.
Fields are missing or have different names
The webhook after the call has a fixed structure. You'll find the fields under Webhook after the call. Empty fields come from details that were missing in the conversation. Create variables for them in the Context Extractor and have the agent ask for them specifically.
Make or Zapier don't trigger an outbound call
| API response | Meaning |
|---|---|
| 401 | API key missing, wrong or deactivated, see API keys |
400 with invalid_to_number | Destination number not in E.164 format with a plus sign |
403 with identity_not_verified | Verify your identity once under Billing |
422 with no_assistant_mapped | No agent is assigned to the sender number |
| 429 | Too many requests or all lines busy. Wait for the number of seconds given in Retry-After |
All codes with solutions are listed under API error codes.
The CRM tool fails during the conversation
What the agent sent to your system during the call and what it got back is shown under Main Logs. Causes and solutions are listed under Prompt and tools.
Further help
Send us the time of the call, the affected route and your system's response, see Report a problem.
Was this page helpful?