SoftTech AI Registry
Zoho · Zoho Flow

Agentic action execution

The Zoho Flow mechanism in which Zia selects from admin-configured application actions and the selected deterministic application action is executed. Current Zoho documentation describes Zia's action selection both during flow execution and during flow construction/configuration; the relationship between these descriptions is not publicly established.

Recorded characteristics

Function
Architecture as documented: workflow/input context → Zia evaluates applicable context → configured application actions form the available action set → Zia participates in selecting the appropriate action → the selected deterministic application action executes. Three layers are kept separate: (A) AI selection/reasoning by Zia; (B) deterministic application-action execution orchestrated by Zoho Flow; (C) application connection authority. An owner/admin adds application actions in Settings → AI Setup → Agentic actions; a "Run agentic action" step with a prompt (which can reference earlier step data) is added to a flow. "This action description will be used by Zia to decide which smart action to use"; Zia chooses "the best option from the list of enabled actions". Product page: "Define possible actions, and let AI decide and perform the right one"; "Replace extensive decision boxes… with a single AI step". SELECTION TIMING CONFLICT (preserved, not resolved): runtime wording — worked example: "When a new ticket is created, the agentic action reads the ticket description, matches it against your configured actions, and executes the most suitable one"; release note: "execute[s] the next step based on your prompt". Build-time wording on the same help page: "Zia will select this action while configuring your workflow"; "Zia intelligently configures the right action"; FAQ "Can I edit Zia's suggested action? … after Zia adds the action block". Current Zoho documentation describes Zia's action selection both during flow execution and during flow construction/configuration. The relationship between these descriptions is not publicly established. Second AI decision layer: for fields set to "Let AI decide", Zia determines values (e.g. Cliq message text, an email address given in the prompt); fields set to "Let me enter the value" are fixed and "remain constant". Not all inputs are AI-generated. The step's "AI Response" output (JSON or plain text) is passed to later steps. Excluded: Text-to-flow/AI flow generation, configuration suggestions, ordinary Zia Utilities, build-time text generation.
Data access
Zia evaluates the step prompt, which can include data from the trigger and earlier steps (e.g. ${trigger.description} of a Zoho Desk ticket), and the descriptions of enabled configured actions. Selected actions read/write data in target applications through Zoho Flow connections, described as "an authorized link between Zoho Flow and an app account. It enables your flows to read and write data on your behalf." Zia itself is not documented as holding target-system credentials.
Actions
Can take actions
External actions
Yes
Human confirmation
Not established
Permission basis
Separate permissions
Administrative control
AI enablement: Settings → AI Setup → Enable AI, owner or admin only; a single switch enables "Flow Generation, ZIA Utilities, and Agentic Actions" together. This global switch is separate from individual workflow state, individual action availability and connection authority. Action configuration: application → action → action description (editable) → per-field input mode (fixed value, "Let AI decide", or empty) → enabled/disabled state. The configured, enabled action set constrains what Zia can select; disabled actions are not available for selection ("the list of enabled actions"). Connections: any member can create them; private by default; can be shared with the organisation "without sharing any credentials"; ownership transferable by the connection owner, organisation owner or admins; users manage only their own connections. Layers: Zia selects/helps determine the action; Zoho Flow orchestrates execution; the application connection provides execution credentials/authority; the target application enforces the permissions of those credentials. Flow owner, builder, triggering user, Zia and organisation owner are not established to share one identity. The agentic pages do not state which connection a selected action uses. Human confirmation: no approval step for agentic actions is documented; "Test with a range of sample ticket descriptions before turning the flow on" is advice, not a control; product-page "set boundaries"/"you stay in control" refer to choosing available actions; Zia routing an approval request "to the right approver" is an action Zia can choose, not confirmation of Zia's choice. Unattended execution (separate from confirmation): once the flow is turned on, each new ticket is handled automatically; product page: "without anyone manually reviewing each response". Triggers: "Run agentic action" is a normal flow step reachable from Flow triggers; the guide uses an app event (Zoho Desk "Ticket created", optional filters); no trigger restrictions documented. Execution History shows "the data exchanged between the trigger and the actions" per run, with input and error tabs; nothing agentic-specific (chosen action, AI-supplied values) is documented. Audit Trail: owners/admins only, logs "who changed what" (human/configuration changes); no evidence it records Zia reasoning or AI decisions.
Default state
Conditional
Availability
Released February 2026 as a new feature (release notes); "available across all Zoho Flow plans, from Free to Professional"; no beta label; no region or account restrictions documented. Default conditional: requires owner/admin AI enablement, configured and enabled candidate actions, application connections, a Run agentic action step with prompt, and the flow turned on.
Licensing
Task consumption: "Every execution consumes certain tasks from your current cycle" (availability/cost limit, not authority); exact task cost per run not established.
External model or provider
"Your content is processed only by Zia, Zoho's own AI, not by third-party models." No specific model is named; not selectable; no bring-your-own-key documented. Model not publicly established beyond Zia. Separate ChatGPT/Claude/Gemini Flow integrations are not the model powering Agentic Actions. Not inherited from #140/#141.
Limitations and uncertainty
Unresolved: (1) timing of Zia action selection — runtime vs construction/configuration wording conflict (not resolved; contributes to partially_verified); (2) which connection a selected action uses and the exact runtime identity relationship; (3) limits of connection authority beyond the target app's own permissions; (4) confirmation behaviour — none documented; (5) whether Execution History shows the chosen action and AI-supplied values; (6) no demonstrated run of the ticket example (documented setup only); (7) no full worked example with a non-Zoho app — Dropbox → Slack prompt and "Zoho CRM or HubSpot" lead scenario are illustrative only, so third-party execution is not established; (8) how "Let AI decide" values are checked; (9) what happens if no action fits; (10) whether more than one action can be chosen per step; (11) model not named; (12) task cost per run. Persistent-action examples from the Zoho Desk "Ticket created" guide (prompt "Check ${trigger.description} and choose the best follow-up action"): Cliq message to a senior agent; acknowledgement email via Zoho Mail; new note in Zoho CRM; move ticket to another Desk department. External action = yes because these target products outside Zoho Flow (boundary is inside vs outside Zoho Flow, not inside vs outside Zoho). The AI is not credited with implementing the downstream action. Product-page scenarios (lead routing, job-application screening, approval routing, outreach replies) are marketing only. The weekly monitor covers the product page only and does not cover every classification field or the timing conflict.

Evidence