Use Knowledge Base and Google Workflow Integrations

Workflow integration nodes let a workflow use organization-owned knowledge files and connected Google services. The result of each node is stored in the workflow variables so that later nodes can use it in templates or Logic conditions. This guide covers:

Knowledge Base search
Google Calendar event creation
Google Calendar availability checks
Google Sheets row appends
Passing results between nodes

Before you begin

Create and save the required Google tool in Tools.
Connect the relevant Google account in Integrations.
For Knowledge Base nodes, upload files from the Files page and wait until they are indexed and ready.
Add the integration node to your workflow and select the saved Google tool in the node configuration.
Test every success and fallback path before publishing.

A workflow Google node references a saved tool with toolUuid. The saved tool contains the Google spreadsheet or calendar configuration and the connected integration. The workflow node supplies the values for the current call.

Workflow variables and output keys

Every Knowledge Base and Google integration node has an Output key (called Output variable for Google nodes in the editor). The runtime stores the node result using that key:

{
  "id": "calendar-check",
  "type": "googleCalendar",
  "data": {
    "output_key": "calendar_availability"
  }
}

If no output key is configured, the node ID is used. In the example above, later nodes can access the result as calendar_availability. If the output key were omitted, they would use calendar-check instead. Use dotted paths in templates:

{{calendar_availability.data.available}}
{{knowledge_result.results.0.content}}
{{sheet_result.data.updatedRange}}

Numeric path segments access list items. The runtime also supports the optional $ prefix:

{{$knowledge_result.results.0.content}}

Use these paths in:

Google Calendar fields
Google Sheets row mappings
Function/API Request URLs, headers, and body templates
Logic edge conditions

Knowledge Base search

A Knowledge Base node searches the selected organization files. It does not search every file automatically; choose one or more indexed files in the node editor.

Configure the node

{
  "id": "search-policy",
  "type": "knowledge",
  "data": {
    "file_ids": ["file-123", "file-456"],
    "query": "What is the refund policy for {{customer_type}}?",
    "top_k": 3,
    "output_key": "knowledge_result"
  }
}

Field	Description
`file_ids`	UUIDs of indexed organization files to search. At least one file is required.
`query`	Search text. Existing workflow variables can be inserted with `{{variable_name}}`.
`top_k`	Number of matching chunks to return. Use a value from 1 to 20; the editor defaults to 3.
`output_key`	Variable that receives the search result. Defaults to the node ID.

The rendered query is sent to the organization-scoped Knowledge Base. A successful result has this shape:

{
  "query": "What is the refund policy for business customers?",
  "count": 2,
  "results": [
    {
      "content": "Business customers may request a refund within 30 days.",
      "score": 0.92,
      "file_name": "refund-policy.pdf",
      "file_id": "file-123"
    },
    {
      "content": "Refund requests must include the original invoice number.",
      "score": 0.84,
      "file_name": "billing-guide.pdf",
      "file_id": "file-456"
    }
  ]
}

Access the first matching chunk in a later node with:

{{knowledge_result.results.0.content}}

Useful paths include:

Path	Value
`knowledge_result.query`	The rendered search query
`knowledge_result.count`	Number of returned chunks
`knowledge_result.results.0.content`	Text from the first chunk
`knowledge_result.results.0.score`	Similarity score of the first chunk
`knowledge_result.results.0.file_name`	Source filename
`knowledge_result.results.0.file_id`	Source file UUID

When a search fails, the result contains error. A search error normally also includes an empty results array and the rendered query:

{
  "error": "Knowledge search failed",
  "results": [],
  "query": "What is the refund policy?"
}

Use a Logic condition such as knowledge_result.count > 0 before using a result in a downstream action.

Google Calendar

The Google Calendar workflow node supports two operations:

Check availability — checks whether a calendar is free during a time range.
Create event — creates an event after the caller has confirmed the details.

Create the matching saved tool in Tools first:

googleCalendarAvailabilityCheck for availability checks
googleCalendarEventCreate for event creation

Then select that tool from the workflow node. The node operation and saved tool type must match. Use ISO 8601 date-time values. Include an offset when possible, for example 2026-06-20T14:00:00+01:00. You can also provide timeZone, such as Africa/Lagos, on the node or in the saved tool configuration.

Check calendar availability

{
  "id": "check-availability",
  "type": "googleCalendar",
  "data": {
    "output_key": "calendar_availability",
    "googleCalendar": {
      "operation": "checkAvailability",
      "toolUuid": "calendar-availability-tool-uuid",
      "startDateTime": "{{appointment_start}}",
      "endDateTime": "{{appointment_end}}",
      "calendarId": "primary",
      "timeZone": "Africa/Lagos"
    }
  }
}

startDateTime and endDateTime are required. calendarId defaults to primary and timeZone defaults to the saved tool’s timezone or UTC. The result is stored under calendar_availability:

{
  "success": true,
  "data": {
    "available": true,
    "busy": [],
    "calendarId": "primary",
    "startDateTime": "2026-06-20T14:00:00+01:00",
    "endDateTime": "2026-06-20T15:00:00+01:00",
    "timeZone": "Africa/Lagos"
  }
}

Use the available value in a Logic edge. condition.value must be a JSON boolean, not the string "true":

{
  "variable": "calendar_availability.data.available",
  "operator": "eq",
  "value": true
}

You can also use the busy periods in a later node:

{{calendar_availability.data.busy.0.start}}
{{calendar_availability.data.busy.0.end}}

An empty busy array means that no busy period was returned for the requested range. Always keep an unconditional fallback edge for the unavailable or error path.

Create a calendar event

Only create an event after the caller has supplied the required details and explicitly confirmed the booking.

{
  "id": "create-appointment",
  "type": "googleCalendar",
  "data": {
    "output_key": "calendar_event",
    "googleCalendar": {
      "operation": "createEvent",
      "toolUuid": "calendar-event-tool-uuid",
      "summary": "{{service}} with {{full_name}}",
      "startDateTime": "{{appointment_start}}",
      "endDateTime": "{{appointment_end}}",
      "attendees": "{{email}}",
      "description": "Booked through Vonative",
      "location": "Google Meet",
      "calendarId": "primary",
      "timeZone": "Africa/Lagos"
    }
  }
}

Required fields are summary, startDateTime, and endDateTime. Optional fields are attendees, description, location, calendarId, and timeZone. Multiple attendees can be provided as a comma-separated string. A successful event result looks like:

{
  "success": true,
  "data": {
    "eventId": "google-event-id",
    "htmlLink": "https://calendar.google.com/calendar/event?eid=...",
    "summary": "Consultation with Ada",
    "start": {
      "dateTime": "2026-06-20T14:00:00+01:00",
      "timeZone": "Africa/Lagos"
    },
    "end": {
      "dateTime": "2026-06-20T15:00:00+01:00",
      "timeZone": "Africa/Lagos"
    },
    "calendarId": "primary"
  }
}

Later nodes can use:

{{calendar_event.data.eventId}}
{{calendar_event.data.htmlLink}}
{{calendar_event.data.summary}}

Google Sheets

The Google Sheets workflow node appends one row to the spreadsheet and range configured in the saved Google Sheets tool. It does not read rows from a spreadsheet. Use a Function/API Request node or a separate integration if your workflow needs to read or query sheet data. Create and configure a saved googleSheets tool with:

Google Sheets integration and connected account
Spreadsheet ID
Sheet range, for example Leads!A:E
Optional field definitions

Then select that saved tool in the workflow node and map the row values.

{
  "id": "log-lead",
  "type": "googleSheets",
  "data": {
    "output_key": "sheet_result",
    "googleSheets": {
      "toolUuid": "google-sheets-tool-uuid",
      "data": {
        "name": "{{full_name}}",
        "email": "{{email}}",
        "appointment": "{{appointment_start}}",
        "knowledge_source": "{{knowledge_result.results.0.file_name}}"
      }
    }
  }
}

The keys in googleSheets.data are mapped to the saved tool’s configured fields. The values can be literal strings or workflow templates. At least one mapped field is required. A successful result is stored under sheet_result:

{
  "success": true,
  "data": {
    "spreadsheetId": "spreadsheet-id",
    "range": "Leads!A:E",
    "updatedRange": "Leads!A42:E42",
    "updatedRows": 1
  }
}

Access the write receipt in later nodes with:

{{sheet_result.data.updatedRange}}
{{sheet_result.data.updatedRows}}
{{sheet_result.data.spreadsheetId}}

The workflow Sheets node is currently an append operation. updatedRange and updatedRows confirm where the row was written; they are not the contents of the entire sheet.

Passing results between nodes

Use an integration result in another integration

{
  "type": "googleSheets",
  "data": {
    "output_key": "booking_log",
    "googleSheets": {
      "toolUuid": "google-sheets-tool-uuid",
      "data": {
        "event_id": "{{calendar_event.data.eventId}}",
        "booking_status": "confirmed"
      }
    }
  }
}

Use a Knowledge Base result in an API request

{
  "type": "function",
  "data": {
    "output_key": "external_result",
    "url": "https://api.example.com/knowledge-events",
    "method": "POST",
    "body_template": "{\"source_file\":\"{{knowledge_result.results.0.file_name}}\",\"answer_context\":\"{{knowledge_result.results.0.content}}\"}"
  }
}

Branch on an integration result

{
  "id": "availability-route",
  "type": "logic",
  "data": {
    "branches": [
      { "id": "available", "label": "Available" },
      { "id": "unavailable", "label": "Unavailable" }
    ]
  }
}

Connect the available branch with:

{
  "variable": "calendar_availability.data.available",
  "operator": "eq",
  "value": true
}

Add an unconditional edge to the unavailable or recovery path. If the integration fails, the runtime emits an error and the workflow should have an error or fallback route.

Example: availability, booking, and logging

A typical appointment workflow is:

A Task collects appointment_start, appointment_end, full_name, email, and service.
A Calendar node with operation: "checkAvailability" writes to calendar_availability.
A Logic node routes on calendar_availability.data.available.
An Agent asks the caller to confirm the available slot.
A Calendar node with operation: "createEvent" writes to calendar_event.
A Sheets node appends the booking and writes to sheet_result.
A confirmation or error path ends the workflow.

This keeps the availability check separate from event creation and prevents an unconfirmed event from being created.

Troubleshooting

Error or symptom	Resolution
No saved Google tool is available	Create the correct Google tool type and select it in the node.
Tool type does not match the node operation	Use `googleCalendarAvailabilityCheck` for `checkAvailability` and `googleCalendarEventCreate` for `createEvent`.
Calendar fields are missing	Availability requires `startDateTime` and `endDateTime`; creation also requires `summary`.
Google integration is not connected	Reconnect the Google account and verify the saved tool references that integration.
Knowledge search returns no results	Confirm the selected files are indexed and ready, then check `knowledge_result.count`.
A template is empty	Check the output key and dotted path. A missing list item, such as `results.0`, renders as an empty value.
Sheets append succeeds but no row is found	Inspect `sheet_result.data.updatedRange` and confirm the saved tool’s spreadsheet ID and range.

Current runtime limitation

Workflow variables are available to deterministic nodes such as Logic, Function, Knowledge Base, Calendar, and Sheets. Static Say text and a later Agent prompt are not currently template-rendered or automatically populated with the full result object. Use the values in supported integration/API fields and Logic conditions, or use a custom runtime step when a later spoken response must include dynamic integration data.

Getting Started

Assistants

WebRTC & Realtime

Workflows

Phone Numbers

Tools

Developer

Billing

Monitoring

Use Knowledge Base and Google Workflow Integrations

Use Knowledge Base and Google Workflow Integrations

Before you begin

Workflow variables and output keys

Knowledge Base search

Configure the node

Google Calendar

Check calendar availability

Create a calendar event

Google Sheets

Passing results between nodes

Use an integration result in another integration

Use a Knowledge Base result in an API request

Branch on an integration result

Example: availability, booking, and logging

Troubleshooting

Current runtime limitation

​Use Knowledge Base and Google Workflow Integrations

​Before you begin

​Workflow variables and output keys

​Knowledge Base search

​Configure the node

​Google Calendar

​Check calendar availability

​Create a calendar event

​Google Sheets

​Passing results between nodes

​Use an integration result in another integration

​Use a Knowledge Base result in an API request

​Branch on an integration result

​Example: availability, booking, and logging

​Troubleshooting

​Current runtime limitation

Use Knowledge Base and Google Workflow Integrations

Before you begin

Workflow variables and output keys

Knowledge Base search

Configure the node

Google Calendar

Check calendar availability

Create a calendar event

Google Sheets

Passing results between nodes

Use an integration result in another integration

Use a Knowledge Base result in an API request

Branch on an integration result

Example: availability, booking, and logging

Troubleshooting

Current runtime limitation