# Global values

> Store values you reuse across emails and automations, such as a webinar date, a booking link or an offer deadline, and use them as {{global.key}}, in conditions and in dates.

A global value is one value for the whole workspace, such as the date of the next webinar, a booking link, an offer URL, a deadline or a sales rep's name. Define it once and use it everywhere as `{{global.<key>}}`: change it in one place and every email sent from then on uses the new value, as does every run that reaches a **Wait until** step afterwards. Runs already waiting keep the date they read.

## Create a global value

1. **Open Global values.** Go to **Workspace → Settings → Global values** and select **New global value**.

2. **Name it.** Enter a **Name**, for example `Webinar date`. The **Key** fills in from the name, for example `webinar_date`. Keys start with a lowercase letter and use lowercase letters, digits and `_`, up to 64 characters.

3. **Pick the type and enter the value.**

   | Type | Value | Example |
   | --- | --- | --- |
   | **Text** | Any text | `Automations masterclass` |
   | **Number** | A number | `120` |
   | **Boolean** | True or false | `true` |
   | **Date** | A calendar date | `2026-11-05` |
   | **Date and time** | A date and time, stored in UTC | `2026-11-05T17:00:00Z` |
   | **URL** | An `http` or `https` URL | `https://cal.example.com/demo` |

4. **Save.** Copy `{{global.webinar_date}}` from the list to use it.

A workspace can have up to 500 global values. Deleting one makes `{{global.<key>}}` render empty.

## Use global values

| Where | How |
| --- | --- |
| Templates, campaigns and automation emails | `{{global.webinar_link}}` anywhere in the subject or content. In Temple, `{{#if global.offer_url}}…{{/if}}` works too. |
| Emails sent with the API | `{{global.<key>}}` in the template or inline content is filled in, unless your `variables` contain a `global` object of their own. |
| Automation step settings | Placeholders such as a **Webhook** body or a **Reply to**: `{{global.sales_rep_email}}`. |
| **Wait until** a date | **Date** → **A global value**, for example "1 day before `webinar_date` at 09:00". See [Wait until](/docs/automations/steps/#wait-until). |
| Conditions | **Check** → **Global value**, for example "**Offer deadline** has passed" to send late registrants a different email. |

Dates and times render as stored, for example `2026-11-05T17:00:00.000Z`. To show a friendlier date, add a Text value next to it, such as `webinar_date_label` = `Thursday, November 5 at 6 PM CET`.

## Use the API

The [Global values API](/docs/api-reference/global-values/) manages them with an API key with **Full Access**. `{id}` is the `gv_` ID or the key:

```bash
curl https://api.emailit.com/v2/global-values \
  -X POST \
  -H "Authorization: Bearer $EMAILIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "key": "webinar_date", "name": "Webinar date", "type": "datetime", "value": "2026-11-05T17:00:00Z" }'
```

```bash
curl https://api.emailit.com/v2/global-values/webinar_date \
  -X POST \
  -H "Authorization: Bearer $EMAILIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "value": "2026-12-03T17:00:00Z" }'
```

The [MCP server](/docs/mcp/tools/) has the same operations in the `global_values` toolset.

## Related

  - [Temple](/docs/templates/temple/): Variables, defaults and conditionals in templates.
  - [Automation steps](/docs/automations/steps/): Wait until a global date.

---
Source: https://emailit.com/docs/contacts/global-values/