Agent integrations

Design the installation boundary before you connect the workflow

Agent-native prospecting works best when runtime compatibility, secret ownership, task inputs, and output destinations are explicit from the start.

Agent integration architecture

Compatibility route

Move from local inspection to governed automation

State 01

Inspect package

Review what the npx command executes and where the runtime places skill files.

State 02

Confirm runtime

Use a supported agent environment with a local terminal and visible package output.

State 03

Scope connectors

Grant only the read or write permissions required by the declared task.

State 04

Validate handoff

Test sample output and human approval behavior before production records move.

Architecture

Four interfaces worth making observable

INPUT

Brief contract

ICP rules, exclusions, desired fields, and jurisdictional constraints arrive as an intelligible task definition.

Structured by operator
SECRET

Credential boundary

API keys remain in runtime secret storage and should never be interpolated into prompts or result files.

Least privilege
REVIEW

Decision checkpoint

Account fit, contact confidence, personalization, and any external action remain separately approvable.

Human in the loop
OUTPUT

Destination adapter

Approved records map to a declared schema so exports and CRM updates do not invent unsupported fields.

Config-dependent

Integration classes

Connection types, not an unverified logo wall

Agent runtimes

Local environments capable of invoking npx and exposing package execution output to the operator.

Research sources

Operator-approved providers used according to their contracts, permitted fields, and regional restrictions.

Secret stores

Runtime or operating-system facilities that keep connector credentials outside prompts and repositories.

Record systems

CRMs, tables, or files reached only through a configured adapter and an explicit human-approved handoff.

1exact install command
4distinct install states
0credentials in prompts
Humanapproval before outreach

Install, inspect, then connect

Copy the command without a shell prompt, run it in your chosen agent environment, and review each requested permission.

npx -y @okki-global/okki-go-taroball