Agent Integrations

Connect prospecting capabilities without hiding the runtime

Install Bardeen as an agent skill, scope the tools it can reach, and keep the boundaries between research, enrichment, drafting, and approval visible.

Open the install runbook
Agent runtime integration architecture with permission boundariesAgentToolsApproval
Runtime matrix

Evaluate compatibility as an operating contract

LayerWhat to verifySafe starting posture
Agent environmentPackage execution support, workspace isolation, and tool-call visibilityUse a test workspace with inspectable logs
CredentialsSecret storage, scope, rotation, and revocationGrant the minimum access needed for one task
Data providersField provenance, rate limits, refresh behavior, and permitted useTest a narrow ICP and record unresolved fields
DestinationsSchema mapping, deduplication, and write permissionsPreview structured output before enabling writes
OutreachReview ownership, opt-out handling, and regional requirementsKeep sending outside the autonomous path

No runtime count is claimed here. Confirm support against the installer output and the documentation available in your own environment.

A result should explain how it became usable

A prospect record is more than a name and email. Operators need the original ICP criterion, the matched company evidence, the inferred buying role, enrichment status, and any unresolved conflict. Bardeen's result pattern keeps those states adjacent so a reviewer can accept, reject, or revise a candidate.

  • Qualification notes remain attached to each account.
  • Contact fields distinguish found, verified, unavailable, and unconfirmed states.
  • Draft content remains separate from permission to send.
  • Destination writes can be reviewed before execution.
Auditable prospect result with evidence and approval states

Permission boundaries before connection density

Package behavior

Read the installer output before execution. Understand which files are added, where configuration is stored, and how the skill is updated or removed. Copying the command does not perform an installation.

Secret handling

Store API keys through your agent runtime's secret mechanism. Avoid placing secrets in prompts, repositories, exported prospect lists, screenshots, or shared logs.

Data responsibility

Assess the provenance and permitted use of connected data. GDPR, CCPA/CPRA, CAN-SPAM, and CASL may shape different parts of a workflow, but evaluation language is not a certification claim.

Human control

Research automation can prepare a decision. It should not silently convert enrichment into outreach. Keep targeting, content approval, and send authority explicit.

Install and inspect

Move through four observable states

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

Copy

Copy the exact package command without a shell prompt.

Run

Execute it where package installation and logs are visible.

Configure

Add narrowly scoped credentials for the selected workflow.

First result

Test a small task and audit every returned field.