# Store static values in constants
URL: https://docs.awellhealth.com/docs/connect-systems/store-static-values-in-constants

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



**Constants** hold values that don't change. They exist because integrations repeat themselves: the
same API URL and the same API key appear in action after action.

Define the value once, reference it everywhere, and change it in one place.

## Global constants and care flow constants [#global-constants-and-care-flow-constants]

* **Global constants** are defined at organization level and available in every care flow.
* **Care flow constants** are defined on one care flow and available only inside it.

Use a global constant for something genuinely shared, like a vendor's base URL, and a care flow
constant for something specific to one flow.

## Create a global constant [#create-a-global-constant]

Global constants are managed in the CareOps portal under settings, and only **organization
admins** can see that section.

> **Global constants are not synchronized between Sandbox and Production.** Configure them separately in
> each environment, and keep the names **identical** across environments.

A constant named slightly differently in Production means the care flow references something that isn't
there. Add it to the [go-live checklist](/docs/design-care-flows/go-live-checklist).

## Create a care flow constant [#create-a-care-flow-constant]

Care flow constants are managed in the care flow's own settings, so anyone who can edit the flow can
manage them.

## Updating a constant changes every reference to it [#updating-a-constant-changes-every-reference-to-it]

Changing a constant's value changes it in every action that references the constant, including the ones
nobody remembers.

## Next steps [#next-steps]

**Next:** [Integrate with extensions](/docs/connect-systems/integrate-with-extensions), which is often
less work than configuring API calls by hand.