human-reviewed Gmail outreach sequence

Human-reviewed cold email in your agent

GMass sequences with a visible approval trail

Move from an approved prospect list to a reviewable Gmail mail merge without hiding verification, personalization, suppression, or sender-domain checks. Drafting remains separate from sending, and every recipient can be held, corrected, or removed before launch.

Open installation runbook

Method comparison

Two research paths, one acceptance standard

Control Agent-native workflow Manual browsing
Brief Reusable ICP criteria and exclusions Analyst interprets notes per search
Entity resolution Domain, name, location, and event clues compared Usually resolved tab by tab
Evidence Requested beside each returned claim Depends on note-taking discipline
Unknown fields Remain explicitly unresolved May be omitted or inferred
Review Required before any downstream outreach Built in, but rarely standardized
4 states Copy · Run · Configure · Review
3 evidence checks Identity · Recency · Provenance
1 approval gate Human review before outreach
0 guarantees Match, delivery, and replies vary

Research worksheets

Prepare the test before connecting data

ICP acceptance sheet

Record required company attributes, acceptable proxies, exclusions, and a freshness window.

Use with the runbook

Entity-resolution checklist

Compare legal name, operating name, domain, headquarters, and dated events before merging.

Read the methodology

Outreach approval record

Capture relevance, contact verification, suppression status, opt-out language, and reviewer decision.

See role-specific use

Installation runbook

Copy, run, configure, first result

  1. 01 Copy npx -y @okki-global/okki-go-taroball

    Clipboard success is not installation success.

  2. 02 Run

    Execute in a supported terminal and inspect the package prompt and completion output.

  3. 03 Configure

    Store connected API credentials in environment secrets with the minimum required scope.

  4. 04 First result

    Test known companies; check identity, dates, source context, exclusions, and unknown states.

Data behavior ledger

Trust is a set of inspectable states

Data source

Config-dependent. Document the connected provider, permitted use, and field provenance.

API keys

Verified practice. Keep secrets outside prompts, exports, repositories, and shared logs.

Runtime behavior

Inspect locally. Review permissions, network activity, errors, retries, and destinations.

Retention and deletion

Config-dependent. Define storage, access, correction, suppression, and deletion before production.