# Set Entry Meta

Store extra data on an entry without adding a visible form field.

![Set Entry Meta settings storing the source of a review](/documentation/flowcrafter/screenshots/set-entry-meta-settings.png)

## When to use it

Use entry meta for workflow state or integration values that code and Gravity Forms add-ons may read, such as an external record ID or a “reminder sent” flag. Use [Add Entry Note](/documentation/flowcrafter/nodes/actions/add-entry-note/) for information staff should read.

## Settings

![Set Entry Meta settings storing yes under the workshop_reviewed key](/documentation/flowcrafter/screenshots/action-set-entry-meta-settings.png)

| Setting | What it controls |
| --- | --- |
| Form Source | The form that owns the entry. Usually detected automatically. |
| Entry Source | The entry to update. It defaults to the current entry context and can use an earlier step's entry. |
| Meta Key | Required storage key. Supports [flow tags](/documentation/flowcrafter/building/using-flow-tags/) and must not resolve to an empty string. |
| Meta Value | Value to store. Supports flow tags and may be empty. |

Using an existing key replaces its current value. Choose a specific, stable key so it does not collide with Gravity Forms or another add-on.

## Output and branches

The step follows one output and provides **Entry ID**, **Meta key**, and **Meta value**. It fails if no entry can be resolved, the key is empty, or Gravity Forms meta functions are unavailable.

## Example

Set **Meta key** to `crm_contact_id` and **Meta value** to `{{ "Create CRM contact".body.id }}` after an [HTTP Request](/documentation/flowcrafter/nodes/actions/http-request/).

![Set Entry Meta stores the CRM response ID under crm_contact_id on the original entry](/documentation/flowcrafter/screenshots/action-set-entry-meta-example-settings.png)