Koleksiyonlar ile düzeninizi koruyun
İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın.
Açık çağrı, bir kullanıcı Google Asistan'a İşleminizi adıyla kullanmasını söylediğinde gerçekleşir.
İsteğe bağlı olarak kullanıcı, çağrısının sonuna, doğrudan istediği işleve götürecek bir çağrı ifadesi ekleyebilir.
Açık çağrı bileşenleri
Aşağıdaki örnekte açık bir çağrı komutunun farklı olası bileşenleri gösterilmektedir:
Tetikleyici ifade
Aşağıdaki ifadeler açık bir çağrı başlatır ve Actions on Google tarafından tanımlanır:
"Ok Google, konuş..."
"Ok Google, konuş..."
"Ok Google, konuşmak istiyorum..."
"Ok Google, sor..."
Diller ve Yerel Ayarlar bölümünde her dil için tetikleyici ifadelerle ilgili bilgi edinebilirsiniz.
Çağrı adı
Bu, "Kişisel Şef" gibi işleminizin adıdır. Kullanıcılar, İşlemleri ada göre açıkça çağırmak için bunu tetikleyici ifadelerle birleştirir. Örneğin: "Ok Google, Personal Chef ile konuşayım."
Çağrı ifadesi (isteğe bağlı)
Çağrı ifadeleri, İşleminizin bulunabilirliğini artırmak için değerli bir mekanizmadır ve kullanıcıların belirli bir görevi yerine getirmelerini sağlayarak görüşmenize derin bağlantı oluşturmaları için bir yol sağlar. Bu ifadeler, kullanıcıların İşleminizin özelliklerini istemek için kullanabileceği çeşitli yöntemleri gösterir. Böylece Google Asistan, İşleminizin özelliklerini daha iyi anlayabilir ve bunları kullanıcı istekleriyle eşleştirebilir.
"bana yemek tarifleri bul"
"şarap öner"
"araç ayırtın"
"oyun oyna"
"meditasyon yapmak istiyorum"
Kullanıcılar belirli amaçları açıkça çağırmak için çağrı adınızı çağrı ifadeleriyle birleştirir. Örneğin: "Ok Google, yemek tarifi bulmak için Personal Chef ile konuş."
Açık çağrı amacı
İşleminiz herhangi bir çağrı ifadesi olmadan ve ad ("Ok Google, Personal Chef") ile açıkça çağrılırsa İşleminizdeki actions.intent.MAIN amacı tetiklenir. Actions projenizde ada göre yalnızca uygunsuz çağrı için tek bir ana amaç bulunmalıdır.
İşleminiz bir çağrı ifadesiyle ve adla açıkça çağrılıyorsa ("Ok Google, bugünün çorba tarifi için Kişisel Şef ile konuş") bu çağrı ifadesine karşılık gelen intent çağrılır.
Daha fazla bilgi için intents dokümanlarımıza bakın.
[null,null,["Son güncelleme tarihi: 2025-07-28 UTC."],[[["\u003cp\u003eExplicit invocation is when a user directly addresses the Google Assistant and specifies your Action by name, optionally including an invocation phrase for a specific function.\u003c/p\u003e\n"],["\u003cp\u003eActions on Google uses trigger phrases like "Ok Google, talk to..." for explicit invocation, which may launch an app instead of the Action if the phrase overlaps with an App Action's built-in intent.\u003c/p\u003e\n"],["\u003cp\u003eThe invocation name is the name of your Action, which users combine with trigger phrases for explicit invocation; ensure it is easily recognizable by the Assistant and adheres to naming policies.\u003c/p\u003e\n"],["\u003cp\u003eOptional invocation phrases increase discoverability and enable deep linking by illustrating user requests for your Action's features, improving the Assistant's understanding of your Action's capabilities.\u003c/p\u003e\n"],["\u003cp\u003eExplicit invocation triggers either the \u003ccode\u003eactions.intent.MAIN\u003c/code\u003e intent when invoked by name only, or the intent corresponding to the invocation phrase when one is included.\u003c/p\u003e\n"]]],["Explicit invocation allows users to engage Actions by name using trigger phrases like \"Ok Google, talk to...\" followed by the Action's name (e.g., \"Personal Chef\"). Users can also add an optional invocation phrase to direct the Action to a specific task (e.g., \"find me recipes\"). If no phrase is included it triggers `actions.intent.MAIN`. The directory and specific invocation phrases enhance Action discoverability. Trigger phrases may be overwritten by apps.\n"],null,["# Explicit Invocation (Dialogflow)\n\nExplicit invocation occurs when a user tells the Google Assistant to use your Action by name.\nOptionally, the user can include an invocation phrase at the end of their\ninvocation that will take them directly to the function they're requesting.\n| **Note:** Users can discover your Action through the [Assistant directory](/assistant/directory), which is like a web store for Actions on the Google Assistant. The directory is a major source for your Action's discovery, so be sure to devote some development time to building a good listing.\n\nExplicit invocation components\n------------------------------\n\nThe following example shows the different possible components of an explicit\ninvocation command:\n\n### Trigger phrase\n\nThese phrases start an explicit invocation and are defined by Actions on Google:\n\n- \"*Ok Google, talk to...*\"\n- \"*Ok Google, speak to...*\"\n- \"*Ok Google, I want to speak to...*\"\n- \"*Ok Google, ask...*\"\n\nYou can read about trigger phrases for each language on\n[Languages and Locales](/assistant/console/languages-locales).\n| **Note:** On Android devices, trigger phrases invoke your Action, unless the phrase overlaps with an App Actions [built-in intent](/assistant/app/intents). In these cases, Assistant launches your app, if it's installed, instead of the Action.\n|\n|\n| For example, if a user says something like, \"*Hey Google, record that I ate\n| a burrito on ExampleTracker,\"* Assistant launches the *ExampleTracker*\n| app, if it has implemented the [`actions.intent.RECORD_FOOD_OBSERVATION`](https://developers.google.com/assistant/app/reference/built-in-intents/health-and-fitness/record-food-observation)\n| built-in intent, over any *ExampleTracker* Actions serving a similar intent.\n\n### Invocation name\n\nThis is the name of your Action, such as \"Personal Chef.\" Users combine this with\ntrigger phrases to explicitly invoke Actions by name, such as: \"*Ok Google, let me\ntalk to Personal Chef.*\"\n| **Note:** It's important to have invocation in mind when you're figuring out what to name your Action. If you have a clever Action name but the Assistant has trouble recognizing it, users may have difficulty invoking your Action. Refer to our [naming policies](/assistant/console/policies/general-policies#naming_directory_listing_and_promotion) and [invocation checklist](/assistant/df-asdk/checklist) for more details.\n\n### Invocation phrase (optional)\n\nInvocation phrases are a valuable mechanism to increase the discoverability of\nyour Action, and provide a way for users to deep link into your conversation by\nproviding a specific task to accomplish. These phrases illustrate various ways\nusers might request your Action's features, so the Google Assistant can better\nunderstand your Action's capabilities and match them with user requests.\n\n- \"*find me recipes*\"\n- \"*recommend a wine*\"\n- \"*book a ride*\"\n- \"*play a game*\"\n- \"*want to meditate*\"\n\nUsers combine your invocation name with invocation phrases to explicitly invoke\nspecific intents, such as: \"*Ok Google, talk to Personal Chef to find me\nrecipes.*\"\n| **Note:** Make sure your invocation phrases are specific to your Action and describe real-world use cases. A common mistake is to define invocation phrases that are too general to be specific to your Action's purpose, which makes your phrases less useful and hurts your Action's discovery. Refer to [implicit invocation](/assistant/df-asdk/discovery/implicit#writing_useful_invocation_phrases) and the [invocation checklist](/assistant/df-asdk/checklist) for more details.\n\nExplicit invocation intent\n--------------------------\n\nIf your Action is explicitly invoked without any invocation phrase and by name\n(\"*Ok Google, talk to Personal Chef* \") the `actions.intent.MAIN` intent in your\nAction is triggered. Your Actions project must only contain one main intent for\nexplicit invocation by name.\n\nIf your Action is explicitly invoked with an invocation phrase and by name\n(\"*Ok Google, talk to Personal Chef for today's soup recipe*\"), then the intent\ncorresponding with that invocation phrase is invoked.\n\nFor more information, reference our documentation on [intents](/assistant/df-asdk/reference/intents)."]]
