Attention: Get Field Configuration Item

Get Field Configuration Item.

Tool ID: attention_get_field_configuration_item

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'attention_get_field_configuration_item',
  {
    "id": "id_123",
    "itemId": "item_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute attention_get_field_configuration_item --input '{
  "id": "id_123",
  "itemId": "item_123"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "data": {
      "uuid": "uuid_123",
      "fieldConfigurationUUID": "field_configuration_123",
      "title": "VP of Engineering",
      "category": "CRM",
      "contents": "example",
      "promptType": "example",
      "contentType": "example",
      "allowLongResponse": true,
      "extractQuotes": true,
      "availableToAllClients": true,
      "createdAt": "2026-01-15T12:00:00Z",
      "lastModifiedAt": "2026-01-15T12:00:00Z"
    }
  }
}

Use deepline tools get attention_get_field_configuration_item --json for the latest machine-readable contract.

Input reference

Returns a single field-configuration item by UUID. Items belonging to a field configuration in another organization return 404.

Name	Type	Required	Default	Details
`payload.id`	`string`	Yes	—	UUID of the field configuration.
`payload.itemId`	`string`	Yes	—	UUID of the field-configuration item.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Envelope containing a single field-configuration item.
`result.data.data`	`object`	No	—	A single field within a Field Configuration (internally `IntelligenceItem`). Items describe a prompt that Attention evaluates against a conversation and produces a value for. A field-configuration item is cloned as one `IntelligenceItemAssignment` per team the parent configuration is assigned to - see `IntelligenceItemAssignment`.
`result.data.data.uuid`	`string`	Yes	—	Unique identifier of the item.
`result.data.data.fieldConfigurationUUID`	`string`	Yes	—	UUID of the parent field configuration.
`result.data.data.title`	`string`	Yes	—	Short human-readable title of the item. Trimmed; 1-128 characters.
`result.data.data.category`	`"CRM" \| "Indicators" \| "BuiltInInsight" \| "CustomInsight"`	Yes	—	Category of the item. One of the intelligence-category enum values. Allowed: `CRM`, `Indicators`, `BuiltInInsight`, `CustomInsight`.
`result.data.data.contents`	`string`	Yes	—	Prompt text that Attention will evaluate against each conversation.
`result.data.data.description`	`string`	No	—	Optional longer description shown to end users. 0-2000 characters.
`result.data.data.promptType`	`string`	Yes	—	Prompt family used to analyze the conversation.
`result.data.data.contentType`	`string`	Yes	—	Expected shape of the extracted content.
`result.data.data.responseType`	`string`	No	—	Optional response data type hint.
`result.data.data.options`	`array`	No	—	Optional allowed response values when the item is a multiple-choice field.
`result.data.data.dependsOn`	`array`	No	—	UUIDs of other items this item depends on.
`result.data.data.maxValues`	`integer`	No	—	Maximum number of values allowed for multi-select items.
`result.data.data.allowLongResponse`	`boolean`	Yes	—	Whether the analyzer may produce a longer free-text response.
`result.data.data.extractQuotes`	`boolean`	Yes	—	Whether the analyzer should attach supporting quotes to the response.
`result.data.data.availableToAllClients`	`boolean`	Yes	—	Internal flag marking the item as globally available.
`result.data.data.analysisLevel`	`"conversation" \| "deal" \| "lead" \| "contact" \| "account"`	No	—	Level at which the item is evaluated. Allowed: `conversation`, `deal`, `lead`, `contact`, `account`.
`result.data.data.metadata`	`object`	No	—	Numeric scoring metadata for a field-configuration item. Required when the item represents a numeric score - `min_score` must be less than or equal to `max_score`.
`result.data.data.metadata.min_score`	`number`	No	—	Minimum allowed score value. Format: `double`.
`result.data.data.metadata.max_score`	`number`	No	—	Maximum allowed score value. Format: `double`.
`result.data.data.metadata.middle_score`	`number \| null`	No	—	Optional midpoint score value, used by scoring heuristics. Format: `double`.
`result.data.data.metadata.min_criteria`	`string`	No	—	Human-readable description of what the minimum score means.
`result.data.data.metadata.max_criteria`	`string`	No	—	Human-readable description of what the maximum score means.
`result.data.data.metadata.middle_criteria`	`string \| null`	No	—	Human-readable description of what the middle score means.
`result.data.data.createdAt`	`string`	Yes	—	Timestamp when the item was created. Format: `date-time`.
`result.data.data.lastModifiedAt`	`string`	Yes	—	Timestamp when the item was last updated. Format: `date-time`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Attention: Get Field Configuration Item

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation