Stay organized with collections
Save and categorize content based on your preferences.
Create and upload action feeds
When creating and uploading action feeds, follow these instructions:
Follow the spec described in the
action feed
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.
In the fileset descriptor, set the name field to
reservewithgoogle.action.v2. For an example of the descriptor file, refer to the JSON sample.
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.
Upload feeds to the generic SFTP server daily as full
refreshes.
You can find SFTP server details in the
Configuration > Feeds section of the Partner Portal.
Selecting feed servers in the Partner Portal
View feed ingestion status in the
Feeds > History section of the Partner Portal.
Definitions
ActionFeed Definition
messageActionFeed{repeatedActionDetaildata=1;}
ActionDetail Definition
messageActionDetail{stringentity_id=2;stringlink_id=3;// Deep link for action detailstringurl=4;repeatedActionactions=1;}
[[["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-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,[]]