SDK examples - Deepline

Human guide: work with your agent →

Choose a maintained source example by the input and caller boundary you need.

Choose the closest outcome. Each linked guide owns its commands, data contract, and production boundaries. This directory does not duplicate them.

Outcome	Start with	What you will decide before scaling
Find verified work emails for a lead file	Batch CSV enrichment	Stable row key, representative pilot rows, and which output states need review
Find people at an account by role	Prebuilt Plays	Whether the published input schema fits the identifiers you have
Route accounts differently by segment	Write Plays	The branch conditions and the durable row key for each account
Enrich an inbound form fill	Webhooks and schedules	Sender authentication, delivery identity, and the destination owner
Refresh an account list every morning	Webhooks and schedules	Cron timezone, manual test input, and the maximum work allowed per run
Start a prebuilt Play from Python or a backend	HTTP and Python	Where the API key lives and how the caller persists the run ID
Publish reviewed Play code from a repository	Git deploys	Which repository, branch, root directory, and workspace own production

Maintained source examples

The repository includes checked examples for a CSV email flow, inbound webhook, scheduled account refresh, TypeScript caller, Python caller, and production callback. The relevant guide points to the source when a checked implementation exists. Treat it as a starting point: inspect its input and output contract before you run it with your data.

Need an exact API surface?

Use SDK reference for Play authoring and runtime methods, or Runtime API reference for generated HTTP and client contracts.

Verify this task

Locate the source file before copying its command. Read its typed input, description, and output before a representative pilot. Ask your agent to explain a failed check before repeating work or expanding the scope.