Skip to main content
Email is the simplest connector VisIQ has: one address, no credential, about a minute of work. It is also the safety net that keeps an approval from going nowhere. Configure it at Connectors → Human-in-the-Loop → Email.

​
What this address is for

Email is your organisation’s catch-all, not your only delivery path. When you connect an agentic framework or tool, you choose that agent’s approval pathway and register its owner. Approvals for an agent with an owner go straight to that person. This address is where an approval lands when the agent has no owner registered — so an admin can see what is running, decide it, and assign someone. The dashboard queue is always active regardless of what you configure here, so an approval is never lost because a channel is unset.

​
Set it up

  1. Open Connectors → Human-in-the-Loop → Email.
  2. Enter the catch-all address — a shared mailbox such as approvals@yourcompany.com works well, because unclaimed-agent approvals are an admin task rather than one person’s.
  3. Save.
There is no API key, no webhook, and no credential of any kind: VisIQ sends these from its own outbound mail infrastructure. The connector is treated as configured as soon as it holds a non-empty address, which is why the card flips to Connected immediately after saving. Once saved, Send test delivers a real approval-shaped email to the address so you can confirm it arrives and is not caught by a spam filter or a mailbox rule.

​
What the email contains

Each approval email renders, in order: a branded header, the rule or policy reason that routed the call to approval, an AI-generated risk summary, an action-details table, and the call-to-action links. For an unclaimed agent the message also names the agent id and the host it reported from, which is the information you need to assign an owner. The links carry signed, single-use, expiring tokens. Clicking one after somebody else has already resolved the item is safe — the decision is not applied twice.

​
The API behind the card

Both endpoints require a session and the connectors:manage permission. Unlike Slack, config is required on an email upsert, and it holds exactly one field:
PUT /api/connectors/hitl-channels/email
The body is validated strictly: address must be a valid email address, and any key VisIQ does not recognise is rejected rather than ignored. display_label is capped at 120 characters.

​
Troubleshooting

Email is marked connected as soon as a valid address is stored — that is a statement about configuration, not about deliverability. Use Send test to prove delivery end to end, then check the mailbox’s spam folder and any routing rules on a shared mailbox.
That is the intended behaviour for an agent that has an owner registered. This address only receives approvals for agents nobody owns yet. To change where a specific agent’s approvals go, set its owner and pathway on the Agents page.
The approval window is capped at 120 seconds and an unanswered request fails closed, so email suits review-after-the-fact and low-volume gates better than time-critical ones. For interactive, in-the-moment approvals use Slack.

Slack approvals

Interactive Approve and Deny buttons in a channel, with owner direct messages.

Human-in-the-Loop

How approvals pause a tool call, owner routing, and the timeout model.