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

​
Provider-specific requirements

Use kaspr_get_linkedin_profile when you have a LinkedIn profile URL or slug and the person’s full name. Set dataToGet to the smallest set the workflow needs:
  • workEmail for professional email addresses
  • directEmail for personal email addresses
  • phone for phone numbers
Use requiredData only when the workflow should reject a partial match. Every value in requiredData must also appear in dataToGet. Kaspr does not accept Sales Navigator URLs. Convert them to standard LinkedIn profile URLs first. Deepline bills Kaspr profile lookups by the contact fields requested in dataToGet. Phone and direct email are the metered pools. work email is unlimited on the plan and carries only a nominal charge. Request only the fields the workflow needs. Key, rate-limit, and credit reads are free.

​
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.