How to configure webhook enrichment
Webhook enrichment lets ConnectiveOne add data from an external system before creating a call dialog. For example, it can get the operator email from telephony and assign the dialog automatically, or detect the call topic.
This feature is optional. Without it, calls are saved from the provider webhook fields only.
Prerequisites
- A configured telephony channel and a working webhook
- An action created or available in Scenario Builder -> Action Jail
- Access data for the external system that the action calls
When to use it
- You need to assign operators automatically by email from telephony.
- You need to route calls by topic, for example online or offline calls.
- The provider webhook does not include the operator email or topic, so the data must be requested separately.
Main interface elements
- Webhook enrich action — the field in the telephony channel form where you select an Action Jail action.
- Enrich error action — what to do if the webhook enrich action fails.
- Auto transcription — the channel setting that starts call recording transcription after an operator is assigned.
- Action Jail — where enrichment logic and parameters are stored.
- Action test — a check in Action Jail using sample call data before you connect the action to the channel.
Step 1: Prepare the action in Action Jail
- Go to Scenario Builder -> Action Jail.
- Create or open the action prepared for your telephony integration.
- Fill in the action parameters according to your implementation instructions.
- Run an action test:
- enable the full state mode or pass JSON with the
telephonyblock, as in a real webhook; - make sure the test completes successfully.
- enable the full state mode or pass JSON with the
If the action does not exist yet, contact the ConnectiveOne implementation team. Complex integrations with several systems or non-standard webhook fields are configured together with them.
Step 2: Connect the action to the channel
- Open Settings -> Bots -> [your bot] -> Telephony.
- Create a channel or open an existing one.
- In Webhook enrich action, select the action from the list.
- If Auto transcription is enabled in the channel, select Enrich error action:
- Do not assign or auto-transcribe — use this when a dialog should remain unassigned and transcription should be skipped if enrichment fails.
- Assign administrator and run auto-transcription — use this when a call should be assigned to the default operator and auto-transcribed even if enrichment fails. By default this is the user with ID
1(root admin). If your instance uses a different administrator ID, your implementation team can set the instance settingtelephony_autotranscribe_default_operator_id.
- Save the channel.
If the field is empty, enrichment is disabled. The call is processed only from webhook data.
Step 3: Check a real call
After saving, make a test call or wait for a real completed call:
| What to check | Expected result |
|---|---|
| Dialog created | The call appears in the Operator Panel even if enrichment failed. |
| Operator assigned | The dialog has an operator participant if the action returned an email that matches an active ConnectiveOne user. |
| Enrichment failed without assignment | If Do not assign or auto-transcribe is selected, the dialog is created without an operator and Auto transcription does not start. |
| Enrichment failed with administrator | If Assign administrator and run auto-transcription is selected, the dialog is assigned to the default operator (ID 1 by default), and the transcript can appear after that. |
| Topic | The dialog has a topic if the action returned an existing topic alias. |
| Enrichment error | The dialog exists; a service message about failed enrichment can appear in the feed. The call is not lost. |
Common problems
| Symptom | What to check |
|---|---|
| Operator was not assigned | The email in telephony matches the ConnectiveOne user email, and the user is active. |
| Topic was not set | The topic with the required alias exists, and the alias returned by the action is identical. |
| Action test works, real call does not | The real webhook may use different field names. Update field mapping in Advanced Config. |
| Dialog exists, but enriched fields are missing | Check action logic and external system parameters. An enrichment error does not block dialog creation. |