Overview

You can configure an automation in Vidaoo to send data to XCALLY using a Webhook, and then use that data as dynamic variables within your XCALLY routing logic.

This is particularly useful when you want to pass contextual information from Vidaoo—such as metadata about a meeting—to XCALLY and make routing decisions based on it.

• The integration is built using XCALLY’s Open Channel feature and Vidaoo Automations.

• Vidaoo sends a Webhook POST to XCALLY when a specific event occurs (e.g., when a meeting is created, or the first participant joins).

• XCALLY receives this POST request on the Open Channel endpoint and maps the keys in the webhook body to internal XCALLY variables.

• These variables can then be accessed in the XCALLY routing plan using the Noop Application and the syntax {{keyname}}.

Configuration Steps

Step 1: Create a Vidaoo Automation with Webhook

1. In the Vidaoo Admin Panel, navigate to Automations.

2. Create a new automation triggered by an event like:

   • Meeting Created

   • First Participant Joined

3. Add a Webhook as the action.

Open

2. Webhook Configuration:

• Method: POST

• URL: Paste the Receive URL of your XCALLY Open Channel Account.

• Body: Define the data you want to send as JSON key-value pairs. E.g. the value <$data.metadata.long$> corresponds to key cf_20

Open

Step 3: Use Variables in Routing Logic

• XCALLY will automatically create variables using the keys from the webhook body (e.g., cf_20, customer_id).

• In your Routing Plan, add a Noop Application and set a variable using the syntax: {{cf_20}}

Open

Step 4: Verify the Result

Check the XCALLY Logs to verify that the webhook data was received and the variables were correctly assigned.

🔁 Example Use Case

• A customer initiates a Vidaoo video call from your website.

• Vidaoo creates a meeting and sends metadata (e.g., customer ID, call type, or location) to XCALLY via webhook.

• XCALLY uses the received variables to:

  • Route the call to the appropriate queue or agent.

  • Tag the interaction with contextual information.

  • Trigger custom scripts or CRM updates.