Action feed

  • The Action feed specification is defined in protobuffer format, but uploading feeds in JSON format is recommended.

  • The ActionFeed contains repeated ActionDetail messages, each having an optional entity_id and repeated Action messages.

  • An Action can contain AppointmentInfo, which specifies a deep link url for an appointment action.

  • Sample JSON demonstrates how to structure an Action Feed with entity_id and an appointment_info URL.

  • A Descriptor File accompanies the action feed, including a generation_timestamp, a name, and a list of data_file names.

Definitions

Action Feed

message ActionFeed {
  repeated ActionDetail data = 1;
}

ActionDetail Definition

message ActionDetail {
  optional string entity_id = 2;
  repeated Action actions = 1;
}

Action Definition

// Information about an Action which could be performed.

message Action {
  // Deprecated fields not to be reused.
  reserved 1;
  oneof action_info {
    AppointmentInfo appointment_info = 2;
  }
}

AppointmentInfo Definition

message AppointmentInfo {
  // Deep link for appointment action.
  string url = 1;
}

Action Feed samples

Action Feed

{
  "data": [
    {
      "actions": [
        {
          "appointment_info": {
            "url": "https://www.epapartnerwebsite.com/appointment/appointment-partner-1"
          }
        }
      ],
      "entity_id": "appointments-merchant-1"
    }
  ]
}

Descriptor File

{
  "generation_timestamp": 1677540395,
  "name": "reservewithgoogle.action",
  "data_file": [
    "action_1677540395_0001.json",
    "action_1677540395_0002.json"

  ]
}