> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Datagma Find People: Inputs, Cost & CLI Example
> Find up to 10 matching people by title inside a target company. Includes inputs, outputs, pricing notes, Deepline CLI examples, and GTM automation guidance.
## Run in Enrichment Spreadsheet
Use this function as a column step in `deepline enrich`.
```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=datagma_find_people:{}' --json
```
Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
## Input Schema
| Name | Type | Required | Default | Description |
| -------------------------- | --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `payload.currentJobTitle` | `string` | No | | Current Job Title - You can separate different job titles using 'OR' (e.g., head of OR chief OR CEO). |
| `payload.linkedinId` | `string` | No | | Enter the company's LinkedIn ID if available (e.g., 1441, 2728700…). It is the most accurate input you can use. |
| `payload.domain` | `string` | No | | Enter the domain name if available (e.g., algolia.com, ubisoft.com…). It is less accurate than the LinkedIn ID, but more accurate than the company name |
| `payload.currentCompanies` | `string` | No | | Enter the company name (e.g., Algolia, Ubisoft…). This is less accurate compared to using the domain or LinkedIn ID |
| `payload.countries` | `string` | No | | Country. Please use the country name in minimal letters (e.g., united states, france, germany...) |
| `payload.fuzzy` | `boolean` | No | | When set to true, the endpoint performs a fuzzy search, which broadens the scope of the results by allowing approximate matches. This is useful for finding results that may not exactly match the search criteria. However, enabling this parameter can reduce precision, potentially returning more irrelevant results. Default is false. |
| `payload.debug` | `boolean` | No | | We are working on a feature to filter out non-relevant job titles. Set this parameter to true to disable filtering and retrieve all results |
Show raw input schema
### Input JSON Schema
```json theme={null}
{
"type": "object",
"description": "Allows you to identify individuals working in specific job titles within a given company. The query can return up to 10 people. A successful search costs 10 credits, while an unsuccessful search (no results) costs 1 credit.",
"properties": {
"currentJobTitle": {
"type": "string",
"description": "Current Job Title - You can separate different job titles using 'OR' (e.g., head of OR chief OR CEO)."
},
"linkedinId": {
"type": "string",
"description": "Enter the company's LinkedIn ID if available (e.g., 1441, 2728700…). It is the most accurate input you can use."
},
"domain": {
"type": "string",
"description": "Enter the domain name if available (e.g., algolia.com, ubisoft.com…). It is less accurate than the LinkedIn ID, but more accurate than the company name"
},
"currentCompanies": {
"type": "string",
"description": "Enter the company name (e.g., Algolia, Ubisoft…). This is less accurate compared to using the domain or LinkedIn ID"
},
"countries": {
"type": "string",
"description": "Country. Please use the country name in minimal letters (e.g., united states, france, germany...)"
},
"fuzzy": {
"type": "boolean",
"description": "When set to true, the endpoint performs a fuzzy search, which broadens the scope of the results by allowing approximate matches. This is useful for finding results that may not exactly match the search criteria. However, enabling this parameter can reduce precision, potentially returning more irrelevant results. Default is false."
},
"debug": {
"type": "boolean",
"description": "We are working on a feature to filter out non-relevant job titles. Set this parameter to true to disable filtering and retrieve all results"
}
},
"required": [],
"additionalProperties": false
}
```
## Output Schema
| Name | Type | Required | Default | Description |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `object` | Yes | | Provider response payload. |
| `result.meta` | `object` | No | | Additional response metadata (status, paging). |
Show raw output schema
### Output JSON Schema
```json theme={null}
{
"type": "object",
"description": "Standard tool result payload.",
"properties": {
"data": {
"type": "object",
"description": "Provider response payload.",
"properties": {
"transferData": {
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string"
},
"value": {
"type": "string"
}
},
"additionalProperties": false
}
},
"listOfInvalidDataInput": {
"type": "array",
"items": {
"type": "string"
}
},
"listOfValidLinkedInId": {
"type": "array",
"items": {
"type": "string"
}
},
"employees": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"firstname": {
"type": "string"
},
"lastName": {
"type": "string"
},
"location": {
"type": "string"
},
"jobTitle": {
"type": "string"
},
"company": {
"type": "string"
},
"linkedInUrl": {
"type": "string"
},
"extractedRole": {
"type": "string"
},
"extractedSeniority": {
"type": "string"
},
"extractedGender": {
"type": "string"
},
"person_confidence_score": {
"type": "number",
"format": "float"
},
"employee_jobScore": {
"type": "number",
"format": "float"
},
"employee_companyScore": {
"type": "number",
"format": "float"
},
"email": {
"type": "object",
"properties": {
"email": {
"type": "string"
},
"status": {
"type": "string"
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
}
},
"additionalProperties": false
},
"meta": {
"type": "object",
"description": "Additional response metadata (status, paging).",
"additionalProperties": true
}
},
"required": [
"data"
],
"additionalProperties": false
}
```
## Advanced: Direct CLI
Use direct execution for single payload debugging.
```bash theme={null}
deepline tools execute datagma_find_people --payload '{}' --json
```
### CLI flags
| Flag | Description |
| --------------------------- | --------------------------------------------------- |
| `--json` | Print machine-readable output. |
| `--wait` | Wait for terminal provider status when supported. |
| `--debug` | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS` | Max seconds to wait in wait mode. |
| `--poll-interval SECONDS` | Polling interval in seconds during wait mode. |
| `--timeout SECONDS` | Request timeout in seconds. |
| `--connect-timeout SECONDS` | Connection timeout in seconds. |
## Cost
* Pricing model: `per_result` (per result).
* Estimated Deepline credits: `1.31` per pricing unit.
* Billing mode: `post_deduct`.