This guide walks you through configuring a computation method on a field and triggering computations on your entities. For full technical details on computation methods, inputs, field type support, and access controls, see the Computed Field Values reference.

Prerequisites: You need the Manage Custom Fields permission to configure a Computed Field Value. To trigger computations, you also need the TRIGGER_COMPUTATION user permission, as well as Edit or Suggest access on the entities you want to compute.

Step 1: Choose Your Field

Select the field you want to apply the computation to. You can use an existing custom field, a built-in field, or create a new custom field.

1. Navigate to Knowledge Graph > Configuration.
2. Click the Fields tile.
3. Click into an existing field (or create a new custom field).
4. Click the Computation Method tab.

Step 2: Choose a Computation Method

Click the Computation Method dropdown and select the desired method. The full list of supported methods and their supported field types is in Computed Field Overview.

Note: If you do not have a Content Generation subscription, computation methods that use AI content generation will appear as locked. Contact your Client Success Manager to learn more.

System Controlled Setting

By default, the System Controlled setting is false, which is strongly recommended. This routes all automated computations through Suggestions, so generated content can be reviewed by a human before being applied.

Changing this setting to System Controlled is not recommended. When enabled:

• All computations write directly to the entity profile
• The field value cannot be modified except by the Computed Field Values system via an ongoing triggered computation

Step 3: Configure Inputs

Each built-in computation method has a set of inputs, indicated as required (marked with a red star) or optional. You do not need to provide instructions for the basic task the method performs — only provide inputs that augment or tailor the output for your specific use case.

To use a field value as a dynamic input, reference it using embedded field syntax: [[fieldId]]. For example, to use the entity's name as the blog post topic, enter [[name]].

Example: Write a Markdown Blog Post

Tips for Content Generation Inputs

When using content generation methods, think of inputs as prompts to a generative AI model. To get the desired output, ensure you have provided:

For more on writing effective prompts, see the Write Prompts for Generative Models guide.

Tip: If you want to trigger a computation for multiple entities at once by populating a dynamic input field, define the computation method before populating those field values. This ensures the computation is triggered across all entities when data is added.

Once you have configured all required inputs, save the field configuration.

Step 4: Trigger Computations

Computations can be triggered manually, automatically, or via API.

Manual: Single Entity

1. Navigate to the desired entity in Entity Edit.
2. Click on the field that has a computation method configured.
3. Click the wand icon in the bottom right corner of the field.

4. Review the computed value, make any edits, then click Save.

Manual: Multiple Entities

To trigger a computation on a set of entities, select multiple entities in Entity Search and click the wand icon on the desired field. You can also trigger this modal directly from the Field Configuration screen.

In the modal:

1. Select the field to compute.
2. Designate settings for entities where the field is already populated vs. blank.
3. Select whether to apply the computed value as a direct update or as a Suggestion.
4. Select the entities to compute for — by active filter, saved filter, entity type, or individual selection.
5. Select which language profiles to compute for.

Automatic

A computation is triggered automatically when the value of a dynamic input field changes on a given entity. For example, if yearsOfExperience is a dynamic input for generating a c_bio field, updating yearsOfExperience on an entity will automatically re-trigger the computation for c_bio on that entity.

To trigger a computation automatically, update any dynamic input field value using any standard edit method: Entity Edit, Connectors, API, Bulk Edit, etc.

Automatic computations can be enabled or disabled per field. By default, automatic computations flow through Suggestions so content can be reviewed before being applied. To bypass Suggestions and write directly to the entity, set the computation as Write Directly (not recommended for content generation).

Automatic Computations on Alternate Language Profiles

If a dynamic field input on a language profile changes, an automatic computation is triggered for that profile using the localized input values. If the input field is Primary Only, a field update triggers a computation on alternate language profiles as well. For non-deterministic computations (like content generation), separate computations are run for each profile and may produce different outputs even when given the same inputs.

API

Use the Computations endpoints in the Management API to trigger field computations programmatically.

Step 5: Review and Iterate

Review Suggested Computed Values

When System Controlled is false (the default), all automated computations flow through Suggestions for human review.

1. Navigate to Knowledge Graph > Suggestions.
2. Use the Sources filter to show only Computed Field Values suggestions and click Apply.
3. Review each suggestion and optionally modify, assign, approve, or reject it.

Iterate on Your Configuration

If computed values are not aligned with your desired output, iterate on your inputs. Return to the field configuration, adjust the inputs, and re-trigger the computation.

For example, if you want to add contact information to the end of generated content, you might add to the Additional Instructions input:

Conclude the post with instructions to contact us by calling [[mainPhone]] or emailing [[c_emailAddress]].