Actions

Actions are team-scoped workflow capabilities that agents can be assigned to use. They let an agent do work beyond answering from knowledge without duplicating the same setup for every agent in the team.

Supported action patterns

• Collect a lead and create or update a contact when built-in lead tools are enabled on your deployment.
• Create a native Nexvio ticket when built-in ticket tools are enabled, or call a connected help desk through a configured HTTP action.
• Call a custom HTTP endpoint.
• Run an MCP-backed action against a connected MCP server.
• Send a WhatsApp text message through a connected WhatsApp account.
• Book a meeting or check availability through Cal.com or Google Calendar.
• Check Calendly availability or generate a single-use scheduling link for a connected event type. Share the link with the visitor, who completes the booking on Calendly.
• Run Shopify-connected commerce actions.
• Hand a conversation off to a human.

Catalog availability

The action catalog includes templates whose agent execution is still pending. Generic Slack, Discord, Telegram, Instagram, and Messenger sends and Stripe payment-link templates do not currently become callable agent tools when attached to an agent. Their presence in the catalog or an existing channel connection does not enable these actions.

The standalone send-email action can run through a configured workflow, but attaching it to an agent does not currently expose an email tool. For an agent-driven email flow, use an executable custom HTTP or MCP action.

Lead collection and native ticket forms also require built-in tools to be enabled on your deployment. Confirm availability before relying on them in a conversation.

Custom actions

Use custom actions for business-specific APIs. Define the input fields carefully, validate on the server, and keep destructive or sensitive operations behind explicit confirmation steps in your own systems.