Skip to main content
Use this guide when you need a reviewable reason to contact an account. The result is a research file with evidence and a clear next action—not generic account prose.

​
Choose the research shape

Every research workflow should preserve the input row, source URL or record ID, reason a row passed or needs review, and the next system action. Research that only produces prose is not ready for an automated destination.

​
Prerequisites

  • accounts.csv with a stable account identifier and, preferably, a domain.
  • A definition of the evidence you want, such as a job post, product change, funding event, public record, or company page.
  • A rule for what should be skipped, suppressed, or sent for human review.

​
Define the research contract

Give your coding agent this request. It asks for a local Play and makes the review boundary explicit:

​
Validate it without deploying or spending credits

Once the agent has written the file, validate its source before it runs:
plays check bundles and validates the local Play. It does not publish the Play, create a run, or call a provider.

​
Run a representative pilot

Create accounts-pilot.csv with the header and three representative accounts: one likely match, one typical account, and one sparse or difficult account.
The run can use Deepline credits. Export the completed result for review:

​
Review the pilot before you scale

For each returned row, check:
  • The evidence points to the correct account and supports the stated reason.
  • A missing source is recorded as unresolved, not written as a confident claim.
  • Suppressed or owned accounts did not become outreach candidates.
  • The next action is appropriate for the evidence and has a clear reviewer.
  • The observed Deepline-credit usage is acceptable for the full list.
Do not turn research output into outreach automatically. Review the evidence and the action boundary first.

​
Run the reviewed workflow on the full list

Use the same Play and replace the pilot file with the full input:

​
Next step

Use Warm outbound automation when a visitor event should enter a human-review queue. Use Build a paid ads audience when the approved outcome is an ads audience rather than an outreach action.