Tool Calling
Voilo Assistant supports dynamic tool execution via prompt‑based interactions. Tools can be invoked by the assistant during or after a meeting.
Execution Flow
- Send a message to
POST /v1/meetings/{meeting_id}/threads/{id}/messages
with a tool call request - No special format, just a regular message. - The assistant decides to run a tool and sends a
tool_suggestion
type message. - You choose to run the tool or not - you can display the tool suggestion to the user and let them decide or automatically approve the tool call.
- Reply with the
"confirmToolUse": "true" or "false"
in the message. - The Assistant will execute the tool and return message with
tool_response
type.
See Messages API for more details.
Built‑In Tools
Tool | Capabilities |
---|---|
Slack | Post messages, threads, or files to channels or users. |
Jira | Create or update issues, assign participants, add comments. |
Built‑in tools require minimal setup - just provide credentials in your workspace settings.
Custom Tools
Define your own integrations to reach any service or automation platform.
Configuration Fields
Field | Type | Description |
---|---|---|
name | string | Unique function identifier. |
description | string | Human‑readable summary of the tool’s purpose. |
parameters | object | JSON Schema describing inputs (visual editor available). |
server_url | string | Endpoint to call when the tool is invoked. |
headers | object | Custom HTTP headers (e.g., auth). |
secrets | object | Secure values injected at runtime (API keys, tokens). |
async | boolean | true = fire‑and‑forget, false = wait for immediate response. |
Example Definition
{
"name": "sendWebhook",
"description": "Push data to an external workflow",
"parameters": {
"type": "object",
"properties": {
"url": { "type": "string", "format": "uri" },
"payload": { "type": "object" }
},
"required": ["url", "payload"]
},
"server_url": "https://hooks.example.com/incoming",
"headers": {
"Authorization": "Bearer ${WEBHOOK_TOKEN}"
},
"async": true
}
Custom tools unlock limitless automation, including integrations with n8n or Zapier.
MCP Integration
Voilo Assistant can operate as an MCP Client:
- Receives commands from a central Multi‑Channel Platform controller.
- Executes tool calls via secure MCP channels.
- Streams results back to the controller or directly into the meeting.
This enables large‑scale orchestration across multiple Assistants and meetings.
Typical Use Cases
- Post‑Meeting Summary → Slack
#team‑updates
. - Create Action Item → Jira “To Do” board.
- Trigger Workflow → Webhook to n8n for multi‑step automation.
- Notify CRM → Custom tool that POSTs to your sales platform.
For advanced scenarios or troubleshooting, contact our support team at [email protected].