AI actions - Typewise Documentation

AI actions let the AI Agent modify data in third-party services through integrations. Unlike read-only lookups, these actions change state (e.g., create a ticket, update a record). Actions are disabled by default. To enable one, add it to a Specialist’s instructions using the @ tool picker. Best for:

Automating routine tasks (ticket creation, status updates)
Direct integration with CRM, ERP, or custom systems

Configure an AI action

AI action configuration form

Field	Description
Integration	The third-party service (Salesforce, Zendesk, your MCP server, etc.)
Action	The specific operation to perform
Name	Readable name for this action instance. Shown in the Actions table and exposed to the AI Agent. Custom names are preserved when you edit; the catalog display name does not overwrite them.
Action description	Tell the AI Agent when and how to use this action. Be specific about triggers.
Customize inputs	Per input, pick a source (Auto, Static, or a context variable). On variable mappings, enable Trusted only to require a verified value at runtime.
Require human approval	When enabled, requires Human Agent confirmation before executing. Default: On

You can add the same catalog action multiple times with different names and static inputs. Identical tool + description + inputs combinations are rejected. See Reuse the same action multiple times.

See also

Manual actions: For tasks requiring human execution
Context Variables: Declare context variables and customize action inputs
Security & verification: The trust model behind input customization
Integrations: Connect third-party services
MCP: Build custom integrations