작업 데이터 파일의 경우 작업 피드에 설명된 사양을 따릅니다. 업로드마다 고유한 작업 데이터 파일 이름을 사용하는 것이 좋습니다.
파일 이름에 타임스탬프를 포함합니다(예: action_1633621547.json).
파일 세트 설명자에서 name 필드를 reservewithgoogle.action.v2로 설정합니다. 설명자 파일의 예시는 JSON 샘플을 참고하세요.
업로드마다 고유한 설명자 파일 이름을 사용하는 것이 좋습니다.
파일 이름에 타임스탬프를 포함합니다(예: action_1633621547.filesetdesc.json).
설명자 파일을 일반 SFTP 서버에 업로드해야 합니다.
[null,null,["최종 업데이트: 2025-08-27(UTC)"],[[["\u003cp\u003eThe Action feed utilizes a protobuffer format but recommends JSON for feed uploads, with samples provided for reference.\u003c/p\u003e\n"],["\u003cp\u003eAction feeds are structured with \u003ccode\u003eActionDetail\u003c/code\u003e containing information like entity ID, link ID, URL, and actions related to an appointment.\u003c/p\u003e\n"],["\u003cp\u003eLegacy Action feed integrations should refer to a separate legacy feed reference for guidance.\u003c/p\u003e\n"],["\u003cp\u003eDescriptor files provide information about the feed, including generation timestamp, name, and associated data files.\u003c/p\u003e\n"]]],["The content defines the structure for an Action Feed, used for integrations. It includes `ActionFeed` containing multiple `ActionDetail`, each with an `entity_id`, `link_id`, URL, and a list of `Action`. The `ActionDetail` can contain `AppointmentInfo`. Feeds are defined in protobuffer format, but JSON is recommended, with a sample provided. A Descriptor File accompanies the feed, detailing the generation timestamp, name, and associated data file(s). Legacy feed documentation is also available.\n"],null,["| **Note:** For integration utilizing the legacy version of the Action feed, review the legacy [feed reference](/actions-center/verticals/appointments/redirect/reference/feeds/legacy/action-feed). If you are unsure which version of the feed has been enabled for your integration, reach out to your Google contact.\n\nCreate and upload action feeds\n\nWhen creating and uploading action feeds, follow these instructions:\n\n- Follow the spec described in the [action feed](#ActionFeed-definition) for action data files. We recommend using unique action data file names for each upload. Include a timestamp in the filename, for example, `action_1633621547.json`.\n- In the fileset descriptor, set the `name` field to `reservewithgoogle.action.v2`. For an example of the descriptor file, refer to the [JSON sample](#descriptor-file). We recommend using unique descriptor file names for each upload. Include a timestamp in the filename, for example, `action_1633621547.filesetdesc.json`. The descriptor file must be uploaded to the generic SFTP server.\n- Upload feeds to the generic SFTP server daily as full refreshes.\n- You can find SFTP server details in the [Configuration \\\u003e Feeds](https://partnerdash.google.com/apps/reservewithgoogle/configuration/feeds) section of the Partner Portal.\n\n\nSelecting feed servers in the Partner Portal\n- View feed ingestion status in the [Feeds \\\u003e History](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds) section of the Partner Portal.\n\nDefinitions **Note:** The Action feed spec is defined in protobuffer format below, however we recommend uploading the feeds in JSON format. You can reference our [JSON sample feeds](#samples) for more information.\n\nActionFeed Definition \n\n```protobuf\nmessage ActionFeed {\n repeated ActionDetail data = 1;\n}\n```\n\nActionDetail Definition \n\n```protobuf\nmessage ActionDetail {\n string entity_id = 2;\n string link_id = 3;\n\n // Deep link for action detail\n string url = 4;\n repeated Action actions = 1;\n}\n```\n\nAppointmentInfo Definition \n\n```protobuf\nmessage AppointmentInfo {\n}\n```\n\nAction Feed samples \n\nAction Feed \n\n```json\n{\n \"data\": [\n {\n \"entity_id\": \"appointments-merchant-1\",\n \"link_id\": \"appointment-link-1\",\n \"url\": \"https://www.epapartnerwebsite.com/appointment/appointment-partner-1\",\n \"actions\":[\n {\n \"appointment_info\": {}\n }\n ]\n }\n ]\n}\n```\n\nDescriptor File \n\n```json\n{\n \"generation_timestamp\": 1677540395,\n \"name\": \"reservewithgoogle.action.v2\",\n \"data_file\": [\n \"action_1677540395_0001.json\",\n \"action_1677540395_0002.json\"\n\n ]\n}\n```"]]
