Skip to main content

Abilities

Abilities are modular capabilities you attach to workflows or tasks. They extend what your AI agent can do during conversations — from searching the web to booking appointments to using custom tools you've built.

Without abilities, your agent can converse, collect Data Type values, and follow workflow prompts. With abilities, it becomes a fully capable agent.

How Abilities Work​

  1. Add an ability to a workflow or task
  2. The AI gains that capability during conversations in that context
  3. The AI decides when to use the ability based on the conversation

Abilities can also have conditions (CEL expressions) that control when they activate — like only during business hours or only for VIP members.

Variable and function availability depends on the ability's CEL context; see the Developer CEL reference when writing a condition.

An ability with no settings opens on What the Agent can do: the name of each tool it adds, the first sentence of that tool's description, and the Chats it works in when it is limited to some channels. Your workflow prompt can name these tools. The same names show under the ability in the list of abilities.

Adding Abilities​

Workflow-Level Abilities​

Apply to all tasks in the workflow:

  1. Open your workflow
  2. Go to the Abilities tab
  3. Click Add Ability
  4. Configure and save

Task-Level Abilities​

Apply only to a specific task:

  1. Open the task in the workflow editor
  2. Go to the Abilities tab
  3. Click Add Ability

Task abilities override workflow abilities of the same type. Use this when a specific step needs different tool access than the rest of the workflow.

Attaching abilities from the CLI​

The gr CLI can attach an ability to a task without touching the abilities the task already has:

# Discover the ability type slug and its config schema
gr abilities list -w $WID
gr abilities get --name integration:data_access -w $WID

# Attach it to a task (generates the ability's uuid for you)
gr abilities attach --task 9 --type integration:data_access \
--config '{"dataTypeId":2}' -w $WID --allow-write

# See what's attached, then detach by uuid
gr abilities attached --task 9 -w $WID
gr abilities detach --task 9 --uuid <uuid> -w $WID --allow-write

Notes:

  • The ability type is set with --type (the slug, e.g. oversight:escalation), not slug/name — those are for the read-only get command.
  • gr abilities attach reads the task, appends the new ability, and re-saves, so existing task abilities are preserved. Editing the raw abilities array via gr tasks update instead is a full replace — any ability you omit is deleted.
  • --config takes the ability's JSON config; see gr abilities get for each type's schema. Add --cel '<condition>' for conditional activation and --disabled to attach without enabling.

Built-in Abilities​

Let your AI search the internet for current information. No configuration needed — just enable it and the AI decides when to search.

Great for: looking up business hours, verifying facts, checking recent events, answering questions outside your knowledge base.

Web Browser​

Let your AI open public web pages and use them: read a page, find a field, click, and type. No configuration needed. Your workspace must have the Browser feature turned on.

Calendar Booking​

Give your AI access to check availability and book appointments on connected calendars.

  • Select which calendar and event type to use
  • Optionally allow editing existing bookings
  • Requires a connected Google Calendar or native Gravity Rail calendar. Company Google accounts may need an admin allowlist first — see Google Workspace Accounts.

File Access​

Let your AI read, write, and search files and folders in your workspace.

  • Choose specific files or folders to grant access to
  • Fine-grained permissions: read, write, search, and create
  • Finds matching passages and ranks their relevance

Form Access​

Give your AI access to read or create Data Type records beyond the current conversation.

  • Select which Data Type to access
  • Configure read, create, and update permissions independently
  • Add multiple Form Access abilities for different Data Types

Custom Toolkits​

Attach tools you've built (or MCP server integrations) to give your AI entirely new capabilities.

  • Select which toolkits to include
  • Extend AI with your own integrations and business logic
  • See the Toolkits developer guide for building tools

Phone Call Tools​

Give AI control over voice calls.

  • Hang Up: In a workflow, end calls gracefully when Phone Call Tools is enabled (Agents outside a workflow can always hang up)
  • Forward: Transfer calls to other numbers or agents
  • Pair with conditions for business-hours-only forwarding

Contact Opt-Out​

Add the standard spoken opt-out flow to phone calls in a Workflow or Task.

  • Adds record_contact_opt_out: records a request to stop calls and texts, with a fixed spoken confirmation
  • Adds undo_contact_opt_out: lets the caller correct the request on the same call
  • Works in phone call Chats only
  • Optional; never added automatically. Disable or remove it when you use a bespoke contact-preference flow instead
  • Use a condition to choose when the standard flow is available
  • Existing Workflows receive no automatic selection. Without the ability, the AI receives no standard opt-out tools or instructions; author your chosen flow
  • See Notification Preferences for what a recorded request changes

Send SMS​

Let the agent text the current member.

  • Named templates and optional free-form
  • Per-language variants per template, chosen from the language the caller is using
  • Optional during voice calls
  • Anonymous callers: new callers with a usable phone number start with SMS enabled when no recorded refusal blocks them; unavailable checks leave it disabled. The same named-template and free-form settings apply to all callers. Recorded opt-outs remain authoritative. See Send SMS.

Custom Voice (voice:custom_voice)​

Let members choose the voice the assistant speaks with for this workflow. The preference applies to their own sessions only, and reverts to the workflow's default whenever it isn't compatible with the currently selected voice model — changing the model never breaks a call.

  • Voice tools (on by default): the agent can list available voices, play a short fixed-phrase sample, and set the member's preference when asked — in text chat as well as on calls. On the composable voice stack the conversation continues in the new voice immediately.
  • Allowed voices: optionally narrow which voices members may pick. Entries that aren't available for the current voice model show a warning but never block saving the ability.
  • Members can also manage this themselves from their settings.

Supervisor​

Route complex requests to a supervisor AI for review. Creates a two-tier system where the primary AI escalates uncertain or sensitive requests.

  • Optionally include conversation history for full context
  • Useful for quality assurance, compliance review, and complex decision-making

Manage Workspace​

Let a workflow assistant hand a workspace-management goal to the Manager and stay in the conversation as coordinator.

  • Grant only the write permissions the Manager will need
  • The Manager acts as the current member and cannot exceed that member's role
  • Questions and blockers come back to the workflow assistant to relay

Image Generation​

Let the agent create up to 4 images per request from a text description and show them in the Chat. Your workspace must have the AI image generation feature turned on.

Workflow escalation​

Open the Workflow's Escalation tab to set automatic escalation, pause behavior and Member messages. These settings belong to the Workflow revision. They do not need instructions in the Workflow prompt.

  • Escalate on signals chooses which warning signs escalate. Every Member message is checked and its signals are recorded, independently of the chat model, but a signal acts only when it is chosen here. No signal is selected by default, with or without the Escalation ability, so nothing escalates or pauses on signals until you choose one.
  • Recipients shows the same notification rules as Workspace Settings, filtered to all Workflows or this Workflow. Add a Member, choose the scope, and select SMS, email or voice delivery. Existing priority Members and operator groups also appear here.
  • Pause on escalation pauses the Chat; pair it with a clear paused message. A message that promises a person is sent only when notification succeeds.
  • Let the assistant request a human exposes talk_to_human to the Agent. Its optional CEL condition controls tool availability only; it does not gate automatic signal escalation.

Task and custom-tool Escalation abilities still provide manual talk_to_human tools. They do not configure the Workflow's automatic policy.

Publishing or exporting a Workflow includes its escalation policy, but excludes workspace recipient IDs. Importing or installing a custom-routing Workflow reports that routing needs configuration. An installed Workflow's local recipient binding can be edited without changing the published Workflow definition.

Member Field Verification​

Let the agent confirm a caller's identity by matching configured identity fields against the values on file — without ever seeing the stored values. Admins choose which fields to verify through the ability config.

  • The verify_member tool checks the configured identity fields. A complete identity match requires every enabled field in the same call; a partial call remains incomplete.
  • Configurable fields: verifyName (default: true), verifyEmail (default: false), verifyPhone (default: false), verifyDateOfBirth (default: true)
  • Default configuration verifies name and date of birth only
  • Returns an aggregate identity outcome (matched, not_matched, or incomplete) and one ✓ or ✗ line per provided field; stored values are never revealed
  • A ✗ result is indistinguishable between "wrong value" and "no value on file" — the agent cannot probe which fields are populated
  • The prompt component recognizes "verify the patient", "verify the caller", and "verify the member" instructions
  • Independent of SMS-based phone verification (which lives under Member Access) — enable this on chat-only or email-only agents that should verify identity without telephony

Conditional Abilities​

Make abilities activate only in certain situations using CEL expressions:

# Only during business hours
is_business_hours

# Only for VIP members
"vip" in member.labels

# Only on voice calls
chat.channel == "phone-voice"

Add conditions in the ability's Activation condition field (Edit ability → Activation condition). The ability is only available to the AI when the condition evaluates to true; leave the field empty to always offer it.

Ability Order​

Drag to reorder abilities in the list. This controls how their instructions and tools are assembled for the Agent. It does not require the Agent to use those tools in that order.

Tips​

  • Start minimal — Add only the abilities your workflow actually needs. More abilities means more choices for the AI to make.
  • Use conditions — Limit powerful abilities to appropriate contexts. Don't give every workflow access to everything.
  • Test thoroughly — After adding abilities, run test conversations to make sure the AI uses them correctly and doesn't over-rely on them.
  • Combine workflow and task levels — Add common abilities (like web search) at the workflow level, and specialized ones (like a specific calendar) at the task level.

For developers​