Skip to main content
Human guide: work with your agent → Inspect one Sumble action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use Sumble only when the workspace has connected its own Sumble API key. Deepline does not provide a managed Sumble key, does not pay Sumble provider spend, and should not recommend Sumble as a default fallback when no Sumble key is configured. Good fits when a Sumble key is present:
  • company discovery and account enrichment
  • people discovery, person enrichment, and related-people lookups
  • job-post search and job-related contacts
  • organization signals and priority signals
  • saved organization/contact list management inside the user’s Sumble account
Prefer the synchronous people endpoints: sumble_find_people, sumble_enrich_person, and sumble_find_related_people. Sumble v8 makes sumble_people and sumble_person_detail asynchronous start/poll endpoints. Deepline keeps those disabled until a Sumble polling runtime is implemented. Avoid Sumble when the caller has not explicitly connected or supplied a Sumble API key. Pick Deepline-managed providers instead.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.