시뮬레이터나 기기를 통해 모든 인텐트 (매개변수 유무와 관계없는 기본 또는 맞춤)의 어시스턴트 링크를 테스트할 수 있습니다.
어시스턴트 링크를 테스트하려면 다음 단계를 따르세요.
콘솔에서 어시스턴트 링크를 사용 설정합니다.
Actions on Google 프로젝트를 만들 때 사용한 것과 동일한 계정으로 어시스턴트에 로그인합니다.
어시스턴트 링크의 클릭 가능한 버전을 만듭니다 (이메일, 채팅, 문서 등).
어시스턴트 지원 기기에서 이전 단계에서 만든 링크를 클릭합니다.
어시스턴트 링크가 예상대로 작동하는지 확인한 후 사용자에게 링크를 제공할 수 있도록 작업을 다시 배포해야 합니다.
제한사항 및 권장사항
이제 어시스턴트 링크 URL을 디렉터리나 다른 Google 서비스 외부로 배포하고 참조할 수 있으므로 다음과 같은 제한사항 및 권장사항이 적용됩니다.
모든 어시스턴트 링크를 계속 지원해야 합니다. 나중에 깨지는 어시스턴트 링크를 배포하면 작업 프로젝트가 비정상으로 신고되어 게시 중단될 수 있습니다.
링크를 게시하면 신뢰할 수 없는 소스에서의 트리거를 지원합니다. 연결된 작업의 경우 '실제 작업'을 수행하기 전에 사용자에게 명시적으로 확인해야 합니다. 예를 들어 스마트 홈 가전제품을 끄는 작업은 사용자에게 '$applianceName을(를) 끄시겠습니까?'라고 묻는 메시지를 표시해야 합니다.
이 맥락에서 '실제 행동'은 사용자의 서비스, 데이터, 기기, 네트워크, 컴퓨터 또는 API에 영향을 주는 모든 작업입니다. 예를 들어 이메일 전송, 거래 수행, 스마트 홈 어플라이언스 상태 변경, 구독 생성, 콘텐츠 업데이트 등이 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eAssistant links enable deep linking into specific Actions and intents, allowing users to access functionalities directly from websites or apps.\u003c/p\u003e\n"],["\u003cp\u003eYou can generate unique Assistant link URLs for your Actions within the Actions Console, customizing them with intents and parameters.\u003c/p\u003e\n"],["\u003cp\u003eAssistant links can include built-in intents, custom intents, or no intent (defaulting to the main intent), and can also incorporate UTM parameters for analytics.\u003c/p\u003e\n"],["\u003cp\u003eBefore distributing Assistant links, ensure they are thoroughly tested and that your Action handles potential security concerns by confirming user intent for real-world actions.\u003c/p\u003e\n"]]],["Assistant links generate URLs for specific Actions, directing users to the Assistant on their device. To create a link, enable the URL option in the Actions Console, add a descriptive title, and save. These links can include custom or built-in intents and parameters, which are passed to the Action. UTM parameters can also be included for analytics. Links can be tested via a simulator or enabled device, requiring redeployment for changes to take effect. Ensure all links are continuously supported.\n"],null,["# Link to your Actions (Dialogflow)\n\nYou can generate a URL that will link directly to the specific Action, on a per-Action basis. Users who click the Assistant link (previously called Action links) in a web or mobile browser will be directed to the Assistant on their device, where they'll interact directly with your corresponding Action.\n\nSome examples of useful Assistant links include:\n\n- Linking users to voice-guided instructions from a how-to website.\n- Linking users to a customer support experience from a \"get help\" page.\n- Linking users to an [update intent](/assistant/df-asdk/engagement/daily) so they can opt-in to your future updates.\n\n| **Note:** Assistant links are different from [Directory weblinks](/assistant/directory#web_directory) which send a user to your Directory page.\n\nTo generate a URL for an Action, do the following:\n\n1. In the [Actions Console](https://console.actions.google.com), navigate to **Develop \\\u003e Actions**.\n2. Click the Action you want to generate a link for.\n3. Under the **Links** section, enable **Would you like to enable a URL for this Action**.\n4. Enter a **Link title** . This title should include a verb that is descriptive of what the Action will do. For example, if your Action takes the user down a [transaction flow](/assistant/df-asdk/transactions) to buy tickets to a concert, a useful link title would be \"purchase concert tickets\".\n5. Click **Save**.\n\nYou can copy the provided URL and reference it wherever you want to direct users to this specific Action.\n\n| **Note:** If you enable an Assistant link after your Action is deployed, you will need to re-deploy the Action for the link to take effect.\n\nAssistant link parameters\n-------------------------\n\nAssistant links can optionally contain an intent and parameters in the URL. Google handles the parameters according to the type of intent specified in the URL.\n\n### Assistant link URL specification\n\nThe general syntax for the URL of an Assistant link is as follows: \n\n https://assistant.google.com/services/invoke[/$action_id][?intent=$intent¶m.$param=$value][&$utm_param=$utm_value]\n\nThe URL parameters you can set are described in the following table:\n\n| URL parameter | Description |\n|---------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| `$action_id` | Action's numeric identifier. |\n| `$intent` | Full name of a built-in or custom intent. |\n| `$param` | Full name of an intent parameter specified in the Action package. |\n| `$value` | URL encoded value of the type declared for `$param` in the Action package. |\n| `$utm_param` | List of one or more UTM parameter types. Valid values include: `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, and `utm_content`. |\n| `$utm_value` | String value of the UTM parameter. |\n\n### Assistant link URLs with built-in intents\n\nIf the Assistant link contains a\n[built-in intent](/assistant/discovery/built-in-intents) (the intent starts with `actions.intent.*`), Google will try to extract any built-in intent parameters in the URL and pass them on to your Action. Any parameters that Google does not understand as built-in intent parameters are stripped.\n\nFor conversational Actions, Google sends these parameters to your fulfillment as part of the [`AppRequest`](/assistant/conversational/reference/rest/Shared.Types/AppRequest) message.\n\nThe following example shows how you might specify an Assistant link URL that includes a built-in intent with a single intent parameter: \n\n https://assistant.google.com/services/invoke/uid/0000008ddd7eabec?intent=actions.intent.GET_HOROSCOPE¶m.astrologySign=%22cancer%22\n\n### Assistant link URLs with custom intents\n\nFor custom intents Google extracts only those parameters that are defined by your Action as part of the intent and discards any other parameters.\n\nThe following example shows how you might specify an Assistant link URL that includes a custom intent: \n\n https://assistant.google.com/services/invoke/uid/0000001f575305a0?intent=NEWS_UPDATE_DEEP_LINK¶m.topic=sports\n\nFor the above example URL, in the `AppRequest`, Google adds a JSON object as\nfollows: \n\n argument {\n name: 'topic',\n raw_text: 'sports',\n text_value: 'sports',\n }\n\n### Assistant link URLs with no intents\n\nIf you don't specify an intent in the Assistant link, Google links to the `MAIN` intent (`actions.intent.MAIN`) of your Action by default with the following behavior:\n\n- If you didn't explicitly enable the `MAIN` intent in the Assistant link, Google triggers the main intent without any parameters, similar to the behavior for \"Talk to app_name\".\n- If you explicitly enabled the `MAIN` intent, Google passes the parameters to your Actions.\n\nThe following example shows how you might specify an Assistant link URL with no intent: \n\n https://assistant.google.com/services/invoke/uid/000000d139bbc4d4\n\n### Assistant link URLs with UTM parameters\n\n[UTM parameters](//en.wikipedia.org/wiki/UTM_parameters) are strings that Google sends to your Action when users click on an Assistant link, which you can later use for analytics.\n\nThe UTM parameters that Google sends to your Action includes the following:\n\n- `utm_source`\n- `utm_medium`\n- `utm_campaign`\n- `utm_term`\n- `utm_content`\n\nThe following example shows how you might specify an Assistant link URL that includes UTM parameters: \n\n https://assistant.google.com/services/invoke/uid/000000d139bbc4d4?utm_source=Google&utm_medium=email&utm_campaign=holiday+sale\n\nFor the example URL above, Google adds the following arguments in the `AppRequest` message: \n\n argument {\n name: 'utm_source',\n raw_text: 'Google',\n text_value: 'Google',\n }\n argument {\n name: 'utm_medium',\n raw_text: 'email',\n text_value: 'email',\n }\n argument {\n name: 'utm_campaign',\n raw_text: 'holiday sale',\n text_value: 'holiday sale',\n }\n\nTest Assistant links\n--------------------\n\nYou can test Assistant links for any intent (main or custom, with or without parameters) through the simulator or a device.\n\nTo test your Assistant link:\n\n1. Enable the Assistant link in the console.\n2. Sign into the Assistant with the same account you used to create your Actions on Google project.\n3. Create a clickable version of your Assistant link (in email, chat, doc, etc.).\n4. On an Assistant enabled device, click on the link created in the previous step.\n\nOnce you confirm the Assistant link functions as expected, you will need to re-deploy your Action to make the link available to your users.\n| **Note:** Assistant links are available through all deployment channels (alpha, beta, and production). For example, if your Assistant link is enabled in the alpha release of your Action, the link will be available to alpha testers.\n\nRestrictions and best practices\n-------------------------------\n\nBecause your Assistant link URL can now be distributed and referenced outside of the directory or other Google services, please note that the following restrictions and best practices apply:\n\n- Make sure you continue to support all of your Assistant links. If you distribute an Assistant link that later breaks, your Actions project may be flagged as unhealthy and taken down.\n- Publishing a link means you support triggering from untrusted sources. For any linked Actions, you must explicitly confirm with the user before taking any \"real-world action\". For example, an Action that turns off a [smart home](/assistant/smarthome/overview) appliance should prompt the user saying \"Are you sure you want to turn off `$applianceName`?\"\n\n In this context, a \"real world action\" is any action affecting the user's services, data, devices, networks, computers, or APIs. For example, sending an email, performing a transaction, altering the status of a Smart Home appliance, creating a subscription, or updating a piece of content."]]
