Skip to main content
Job: see what your workflow produced before you hand it to sales, marketing, or ops. The SDK is not only for enrichment. It should help you answer:
  • Which accounts are new this week?
  • Which segments have the strongest signal?
  • Which titles need a different workflow?
  • Which rows failed and need human review?
  • Which accounts should go to Salesforce now?

Start with an output CSV

Most workflows should write an output file:
deepline plays run weekly-new-accounts.play.ts \
  --csv accounts.csv \
  --watch

deepline runs export <run-id> --out output/accounts-enriched.csv
Open the file first. You are looking for boring things:
CheckWhy
row countMake sure no records disappeared
segmentKnow which workflow path each account took
signal columnsSee why the account is interesting
owner or next stepConfirm where the record goes next
error/review columnsSeparate good output from uncertain output

Make a quick chart in Python

Use this when you want a fast view before building anything permanent.
import pandas as pd

df = pd.read_csv("output/accounts-enriched.csv")
print(df["segment"].value_counts())
print(df["next_step"].value_counts())
That is enough to answer: “Did this workflow find the kind of accounts we wanted?”

Common GTM views

ViewUseful when
accounts by segmentYou route enterprise and mid-market differently
titles by seniorityVPs and directors get different plays
signal by sourceYou want to know which signal found the account
output by ownerYou are sending tasks to Salesforce
failed rowsYou need a human review queue

Keep visualization close to the workflow

Recommended folder shape:
workflows/
  weekly-new-accounts.play.ts
  input/accounts.csv
  output/accounts-enriched.csv
  output/accounts-summary.csv
The workflow creates the enriched list. The summary tells your team what changed.