Attention: Get Field Configuration

Get Field Configuration.

Tool ID: attention_get_field_configuration

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',
  {
    "id": "id_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute attention_get_field_configuration --input '{
  "id": "id_123"
}' --json

Example response

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

{
  "data": {
    "data": {
      "uuid": "uuid_123",
      "name": "Example",
      "organizationUUID": "organization_123",
      "teamsUUID": [
        "teams_123"
      ],
      "allTeams": true,
      "isDefaultTemplate": true,
      "createdAt": "2026-01-15T12:00:00Z"
    }
  }
}

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

Input reference

Returns a single field configuration by UUID. Field configurations belonging to other organizations return 404 - the API never leaks cross-organization existence.

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

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Envelope containing a single field configuration.
`result.data.data`	`object`	No	—	A Field Configuration (internally `IntelligenceItemCollection`) groups a set of intelligence items that are surfaced together for the teams it is assigned to. Field Configurations are scoped to a single organization.
`result.data.data.uuid`	`string`	Yes	—	Unique identifier of the field configuration.
`result.data.data.name`	`string`	Yes	—	Human-readable name of the field configuration.
`result.data.data.organizationUUID`	`string`	Yes	—	UUID of the organization the field configuration belongs to.
`result.data.data.teamsUUID`	`array`	Yes	—	UUIDs of the teams this field configuration is assigned to. Ignored when `allTeams` is true.
`result.data.data.allTeams`	`boolean`	Yes	—	When true, this configuration applies to every team in the organization and `teamsUUID` is ignored.
`result.data.data.isDefaultTemplate`	`boolean`	Yes	—	Whether this configuration is the organization’s default template.
`result.data.data.criteria`	`object`	No	—	Criteria expression that controls when this field configuration applies. Conditions are combined using the specified boolean operator.
`result.data.data.criteria.conditions`	`array`	No	—	Ordered list of conditions to evaluate.
`result.data.data.criteria.conditions[].field`	`string`	No	—	Name of the field the condition applies to.
`result.data.data.criteria.conditions[].value`	`string`	No	—	Value the field must match for this condition.
`result.data.data.criteria.operator`	`"AND" \| "OR"`	No	—	Boolean operator used to combine the conditions. Allowed: `AND`, `OR`.
`result.data.data.createdAt`	`string`	Yes	—	Timestamp when the configuration was created. 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

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