Skip to main content

Hawi help centre

Find an answer. Keep moving.

Search product guidance, common fixes and current service information. No sign-in, tracking cookies or customer data required.

Start here

  1. 01Why an agent did not runCheck that the agent and trigger are enabled, required connectors are connected, credit is available and approvals are not waiting.
  2. 02Connect or reconnect GmailOpen Integrations, select Gmail, review requested access and complete Google's authorization flow.
  3. 03Recover access to your HAWI accountUse the normal sign-in recovery flow; suspected compromise requires the security support queue.
  4. 04Failed payments, invoices and disputesUse Billing for invoice and payment state; create a billing ticket for a dispute or exception.

Browse

Help by topic

The public catalogue is drawn from the same maintained knowledge base used by Hawi's in-product support tools.

Getting started

1

Set up your workspace and first agent.

Agents

2

Create, control and troubleshoot agents.

Integrations

2

Connect and repair external services.

Billing & credits

2

Plans, invoices, limits and balances.

Voice

1

Voice agents, calls and safeguards.

Account & login

1

Access, recovery and teams.

Security & privacy

2

Security, privacy and data rights.

Developers & API

5

Apps, OAuth, API and webhooks.

Marketplace

1

Install and publish HAWI apps.

FAQs

How HAWI credits work

Before chargeable work starts, HAWI sets aside an estimate, then charges only what the work actually used. Your balance and prices on the Billing page are always the current figures. Asking HAWI Help a question does not use your agent credits. Voice has its own balance where the product shows one.

Agent approvals and spending controls

An agent cannot bypass workspace permissions, account approvals, spending limits, voice restrictions or the HAWI credit system. A connected app or developer tool also remains subordinate to those controls. If an action is waiting, an authorised person must use the normal HAWI approval flow.

How HAWI isolates support and customer data

HAWI Help never receives service credentials, provider secrets, OAuth tokens, passwords or arbitrary customer content. Account diagnostics are read-only, authorised server-side and sanitised before use. A workspace or account ID supplied by the browser is not trusted until HAWI proves the signed-in user's membership.

Install or remove a marketplace app

A HAWI app installation records the app version, customer account, workspace, installer and granted scopes. Users cannot grant more authority than their own role allows. Removing an app revokes its access and refresh tokens, stops webhooks and disables app-specific actions. New scopes are never added to an existing installation without fresh consent.

Service status

Checking live service status…