Stay organized with collections
Save and categorize content based on your preferences.
It is highly recommended to support localization in Actions Center
integrations. Users are shown a localized experience based on their language
settings. If no localization is set, the default text may be shown to the
user. You are able to provide localized text for many fields in the
integration, such as service names and descriptions. Please refer to our
feed
specification for the full list of fields that can be localized by using the
Text message.
Any field in the feeds that uses a Text message can be localized by providing
a localized_value for each supported language.
It is required to specify both the value and
localized_value.
We will show the localized_value based on the user’s locale
(which is set in the user’s language browser settings).
Value will be used as a default when the user’s locale is not in your
list of supported localizations
Should you not define value and the users locale is not in your list
of supported localizations we will use the first value present in
localized_value. While this fallback is available it is strongly
recommend for you to specify the default value explicitly.
If you do not support localization in your system, please set
localized_value and set locale with the only
language you support. Set value as well which may be used as a
default.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eLocalization in Actions Center integrations is highly recommended to provide users with a personalized experience based on their language settings.\u003c/p\u003e\n"],["\u003cp\u003eAny field using the \u003ccode\u003eText\u003c/code\u003e message in the integration feeds can be localized using the \u003ccode\u003elocalized_value\u003c/code\u003e property for each supported language.\u003c/p\u003e\n"],["\u003cp\u003eIt is mandatory to specify both the default \u003ccode\u003evalue\u003c/code\u003e and the \u003ccode\u003elocalized_value\u003c/code\u003e for localization to function correctly, with the \u003ccode\u003evalue\u003c/code\u003e serving as a fallback.\u003c/p\u003e\n"],["\u003cp\u003eIf localization is not supported, define \u003ccode\u003elocalized_value\u003c/code\u003e with your sole supported language and locale, while also setting the default \u003ccode\u003evalue\u003c/code\u003e for consistency.\u003c/p\u003e\n"]]],["Localization in Actions Center integrations is highly recommended, allowing users to experience content in their preferred language. Integrations utilize a `Text` message, containing both a default `value` and `localized_value` for each supported locale. User's browser language settings determine which `localized_value` is shown; otherwise, the default `value` or the first available `localized_value` is displayed. All `Text` fields within feeds can be localized. The `value` and the `localized_value` need to be specified.\n"],null,["# Specify localized texts\n\nIt is highly recommended to support localization in Actions Center\nintegrations. Users are shown a localized experience based on their language\nsettings. If no localization is set, the default text may be shown to the\nuser. You are able to provide localized text for many fields in the\nintegration, such as service names and descriptions. Please refer to our\n[feed\nspecification](/actions-center/legacy/reference/starter-integration/feed-overview) for the full list of fields that can be localized by using the\n`Text` message.\n\nImplementing localization\n-------------------------\n\n```mysql\n// A possibly-localized text payload. Some Text fields may contain marked-up\n// content.\nmessage Text {\n // Required. Text value in an unknown locale, which will be displayed if\n // `localized_value` for the user locale is empty or missing. The locale for\n // this value may depend on the partner or service provider, and it should not\n // be assumed to be any specific language.\n string value = 1;\n\n // Per-locale text values. Required.\n repeated LocalizedString localized_value = 2;\n}\n```\n\nAny field in the feeds that uses a `Text` message can be localized by providing\na `localized_value` for each supported language.\n\nIt is required to specify both the `value` and\n`localized_value`.\n\n- We will show the `localized_value` based on the user's locale (which is set in the user's language browser settings).\n- Value will be used as a default when the user's locale is not in your list of supported localizations\n - Should you not define value and the users locale is not in your list of supported localizations we will use the first value present in localized_value. While this fallback is available it is strongly recommend for you to specify the default value explicitly.\n\nIf you do not support localization in your system, please set\n`localized_value` and set `locale` with the only\nlanguage you support. Set `value` as well which may be used as a\ndefault.\n\nExample Services Feed Snippet\n-----------------------------\n\n```scdoc\n \"localized_service_name\": {\n \"value\": \"Chocolate Tasting\",\n \"localized_value\": [\n {\n \"locale\": \"en\",\n \"value\": \"Chocolate Tasting\"\n },\n {\n \"locale\": \"fr\",\n \"value\": \"Dégustation de chocolats\"\n }\n ]\n }\n```"]]