Phone Harness logo

Integrate Phone Harness with your AI CRM

Phone Harness provides cloud Android phone sessions for automated lifecycle management, observation, and ADB access.

Explore Triggers and Actions

Create API Key

Create an account-wide API bearer key that can manage API keys. The raw key is shown only once; store it securely and never log it.

ActionTry it

Create Session

Start a temporary or saved Android emulator session and return its admitted session data plus the internally generated idempotency key. If the initial POST has an ambiguous transport failure, this action recovers or safely replays that same keyed request once. A provisioning result is not ready; poll PHONE_HARNESS_GET_SESSION until state is ready or terminal error.

ActionTry it

Create View-Only Link

Create a short-lived view-only link for an intended person to watch a live session. Return the link for secure handoff; it grants no interactive owner control and must not be logged or published.

ActionTry it

Enable ADB

Enable or re-enable ADB access for a ready Android session and return its current connection endpoint and sensitive unlock code. Repeated calls are idempotent.

ActionTry it

End Session

Request that a Phone Harness session end and billing closure be recorded. A cleanup_pending result is asynchronous and continues to consume capacity; use the durable create receipt to confirm cleanup_complete. Repeating cleanup after the session is gone can return session_not_found; that outcome does not prove release or cleanup, even on a repeated call.

ActionTry it

Get Account

Get the connected account's identity, balance, Android profile choices, active-session capacity, and whether a new session can be started.

ActionTry it

Get ADB

Get the current ADB state for an Android session. Returns exactly a disabled result or the enabled connection endpoint and sensitive unlock credential.

ActionTry it

Get API Health

Check public Phone Harness API-process liveness only. This does not certify phone availability, credits, capacity, video, or successful provisioning.

ActionTry it

Get Owner Viewer

Create a secret, short-lived capability for interactive owner control of a ready session. Embedding is restricted to the configured Phone Harness dashboard origin, not arbitrary third-party origins. Reconnecting does not extend the phone deadline. Return it only for secure handoff to the intended account owner; never log, persist, or publish it.

ActionTry it

Get Recent History

Return up to 100 finished sessions ordered by creation time descending. Use LIST_HISTORY instead when complete cursor-based traversal is needed.

ActionTry it

Get Session

Get one session's current lifecycle state, deadline, screen geometry, and ADB details. Use it to poll provisioning; state=error is a terminal startup failure, not success.

ActionTry it

Get Snapshot

Download the latest still image from a ready Phone Harness session as a file. The image is PNG or JPEG. A no-frame-yet response is retryable after the session is ready and has rendered a frame.

ActionTry it

List API Keys

List metadata for the connected account's API keys, including hashes, labels, hints, creation times, and revocation times. This action never returns raw bearer keys.

ActionTry it

List History

Return one cursor-paginated page of finished-session history in newest-first order, with a next cursor for complete traversal.

ActionTry it

List Sessions

List all active account sessions, including provisioning, terminal-error, closing, and cleanup-pending entries.

ActionTry it

Recover Create Request

Read the durable receipt for an idempotent session create to resolve an ambiguous create result or confirm asynchronous release cleanup.

ActionTry it

Reset ADB Code

Rotate the ADB unlock code for an Android session, invalidate the previous code, and close all existing ADB connections. Returns sensitive replacement connection details that must be used for subsequent connections.

ActionTry it

Reset Device

Irreversibly erase and reprovision an assigned iPhone, deleting its apps, accounts, and data. The reset takes a few minutes; poll PHONE_HARNESS_GET_ACCOUNT until the device state is available before starting it again. Phone Harness refuses the reset while a session holds the device.

ActionTry it

Reset Profile

Irreversibly delete the saved Android profile's apps, logins, and data. The next session using its profile ID starts with a fresh phone. Phone Harness refuses the reset while a live session holds the profile phone.

ActionTry it

Revoke ADB

Revoke ADB access for an Android session. This changes only ADB access: the phone session remains active and session billing continues unaffected.

ActionTry it

Revoke API Key

Idempotently revoke an API key by its hash. Identifier existence is not proven by a successful response, and active phone sessions are unaffected. Do not revoke the key used by the current connection if continued Phone Harness access is needed.

ActionTry it

How the Phone Harness integration works

The Phone Harness integration connects your Dench AI CRM directly to Phone Harness, so agents can read and act on your Phone Harness data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.

21 actions are available for agents to invoke on your behalf. Every call runs through Phone Harness's own authorization, scoped to the account you connect.

Set up Phone Harness in Dench

  1. 1

    Sign in to your Dench workspace and open Integrations.

  2. 2

    Find Phone Harness and click Connect — you'll authorize access through Phone Harness's own sign-in flow. No API keys or code required.

  3. 3

    Ask an agent to use Phone Harness in chat, or call it from an automation.

  4. 4

    Manage or disconnect the connection any time from workspace settings.

Frequently asked questions

How does the Phone Harness integration work with Dench?

The Dench Phone Harness integration connects your AI CRM to Phone Harness, so AI agents can work with your Phone Harness data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.

What actions can AI agents perform with Phone Harness via Dench?

The Phone Harness integration currently exposes 21 actions, including Create API Key, Create Session, Create View-Only Link, Enable ADB, End Session, and Get Account. Agents invoke them on your behalf from chat or from automations.

Do I need to write code to connect Phone Harness to Dench?

No. You connect Phone Harness from your Dench workspace using Phone Harness's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.

Is the Phone Harness integration secure?

Connections are authorized through Phone Harness's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Phone Harness connection from your workspace settings at any time.

Phone Harness | Dench AI CRM