SoftTech AI Registry
Zoho · Zoho CRM

Zia Agent CRM action execution

A Zia Agent deployed into Zoho CRM can operate against CRM records using configured tools, with AI-sourced (Model) tool inputs where configured, and can run through CRM activation conditions (Autonomous Trigger conditions) or manual/conversational entry points. Deployment is by connection or as a Digital Employee with its own CRM identity, role and profile.

Recorded characteristics

Function
Boundary (CRM-specific): agents are created in Zia Agents (purpose/instructions, knowledge base, tool groups, connections, guardrails), tested, deployed into Zoho CRM, then set up and activated in Setup > General > Agents. Zoho states AI Agents "execute tasks, make context-aware decisions" and that tools are "the action layer" ("Every time your agent fetches a record, updates a deal stage, or sends an email, it's calling an API that you've allowed it to use"). Tool mechanism: System Tools (pre-built per service, listing tool name, description, method and API path; documented methods GET, POST, PUT, DELETE, e.g. "Change deal stage") and Custom Tools (OpenAPI 3.0 YAML), grouped into tool groups and authenticated through connections. The configured API/tool operation is the execution mechanism, not itself AI reasoning. Tool parameter sources: Model ("The agent figures out the value on its own based on the instructions and conversation context"), On-Trigger (value comes from the triggering CRM record) or Constant (fixed value defined by builder/admin); only Model values are AI-determined. Arbitrary multi-step reasoning, unrestricted tool choice and dynamic planning across all tools are not claimed. Entry points: CRM activation (module; all or conditional records; Autonomous Trigger conditions), manual custom button, and supporting context of Agent Switcher / Ask Zia by profile; platform channels (ChatKit, Cliq, WhatsApp, Agent API) are context only. Architectural context: Zia Agents is cross-Zoho infrastructure deployable into multiple Zoho products; Creator, Flow and Desk evidence is not used.
Data access
Activation can feed the agent fields from the current record, related module information, signals (e.g. email sentiment, missed calls, unopened messages) and user or system metadata. The selected module "determines the data scope the agent can access during execution." Connections carry OAuth scopes and credentials; Zoho advises granting only necessary scopes (e.g. ZohoCRM.modules.ALL for fetching CRM records).
Actions
Can take actions
External actions
Unknown
Human confirmation
Not established
Permission basis
Mixed
Administrative control
Zia Agents roles: Super Admin (unrestricted), Admin (cannot edit/delete the organisation), Collaborator (can create, edit, test and execute agents and workflows but cannot deploy them), Viewer (cannot create, edit or execute). CRM controls: agent portal configuration (Marketplace or Setup > General > Agents), Setup Now/Activate, Manage Agent (triggers, settings, Version id check), Deactivate (moves agent to Draft), disabling the Agent portal (permanently deletes active agents' configurations, triggers and mappings; stops in-progress or scheduled actions; updated records remain). Digital Users section: limited details editable in CRM; deletion or role reassignment managed from Zia Agents. Connections managed under Settings > Connections. Each change creates a new version; rollback available. Builder/admin authority is distinct from runtime execution authority.
Default state
Conditional
Availability
Editions: Zoho CRM paid plans. Prerequisites: access to Zia Agents; Agent API enabled. Requires agent creation, testing, deployment, connections, tool configuration, parameter mapping, CRM activation and permissions; not enabled by default. Overall lifecycle recorded as active. Zoho states "Deploy as a digital employee is being rolled out in a phased manner and may not be available for all services." Region details not publicly established.
Licensing
Zoho CRM paid plans; access to Zia Agents required.
External model or provider
Configurable per agent. Zoho: "Under ZKS (Zoho Key System), you'll find Zoho and OpenAI as built-in options. Under BYOK (Bring Your Own Key), you can use vendors like Claude or ChatGPT if you've configured your own API key." "Model: pick the specific model from your chosen vendor." No single fixed provider; availability of every model in every deployment is not established.
Limitations and uncertainty
ACTION: can_take_actions rests on CRM evidence (Quote Creation Agent "auto-create quotes with mapped fields"; "Records already updated by these agents will remain intact" after portal disable) and platform evidence (record updates/deal-stage changes through tools). No single current CRM walkthrough shows the full chain from agent tool selection to completed CRM mutation. EXTERNAL: unknown - tools/connections can reach other Zoho products and custom APIs, but no CRM-deployed agent making a demonstrated lasting change outside Zoho CRM is established; this does not mean unsupported. CONFIRMATION: not_established - the sample guardrail "Ask for confirmation before performing any action that modifies a record" is a builder-written instruction example, not a platform-enforced runtime mechanism; testing, deployment consent, activation and admin configuration are separate. Autonomous Trigger conditions can result in execution without a person actively present. PERMISSION (mixed = two positively established authority models, not uncertainty): (A) Deploy using Connection - tools use configured connection credentials; connections may use "Credentials of Login User" (on by default) or different credentials, and may be personal, administrator-created or organisation-shared; Zoho says actions are "logged under the identity of the user who deployed it" and the agent has no separate CRM identity. Unresolved: whether the deploying user's ordinary CRM permissions additionally limit execution. (B) Deploy as Digital Employee - registered in Zoho Directory with a unique @ziaagent.ai address, assigned its own role and profile "just like a regular CRM user"; "its access to modules, fields, and data follows the same permission model as your CRM users"; actions logged under this identity in CRM audit logs and activity trails; functions as record owner (record ownership, change owner, mass transfer, import, lead convert, views/reports/dashboards criteria); listed under Digital Users. Limitations: not in Users Lookup fields; cannot be assigned as record owner through workflows, assignment rules or approval processes; deletion/role reassignment managed from Zia Agents. Sharing rules and individual record access unresolved. FIRST-PARTY CONFLICT: CRM setup documentation presents Deploy using Connection and Deploy as Digital Employee as deployment choices, while "Digital Employees: Behavior and Scope" states a digital employee "is automatically created" when a Zia Agent is activated for a CRM module. The relationship between these two current Zoho descriptions is not publicly established. LOGGING: Digital Employee attribution in CRM audit logs/activity trails; Zia Agents Observability (session data, execution metrics, step-by-step breakdowns of individual interactions) and version history. CRM audit logs are not established to contain the tool selected, exact inputs or a reasoning trace. UNRESOLVED: (1) relationship between conflicting Digital Employee descriptions; (2) whether deploying-user CRM permissions constrain connection mode; (3) Digital Employee sharing rules; (4) Digital Employee individual-record access; (5) no single complete CRM tool-selection-to-write walkthrough; (6) CRM selection among several tools / multi-step reasoning; (7) scheduled-trigger availability; (8) exact CRM audit contents for tools and inputs; (9) lifecycle/region availability details; (10) demonstrated persistent external changes.

Evidence