How to integrate Unify with Google AppSheet

Before connecting

• A Unify Play with a Webhook action
• An AppSheet Enterprise plan with the API enabled for the app
• The app ID, regional domain, URL-encoded table name, and enabled access key
• An agreed table schema and key-generation rule

1. 01

   Enable the receiving API

   Confirm plan eligibility and enable the AppSheet API for the intended app. Obtain its app ID and an enabled ApplicationAccessKey.[3][4]

2. 02

   Select the regional URL

   Use the documented app-region domain. The global example uses www.appsheet.com. URL-encode the table name; the older api.appsheet.com domain is deprecated.[3]

3. 03

   Map a valid row

   Use Action: Add and a Rows array containing the actual column names. Supply the row key, or satisfy its configured initial-value rule. Required, editable, and valid-value constraints still apply.[3][5]

4. 04

   Send the Play request

   Set POST, JSON, and the explicit ApplicationAccessKey header in Unify. Inspect Expand preview before sending a controlled record.[1][2][3]

5. 05

   Inspect the app result

   Confirm the new row and the intended user-visible result. A successful API write does not by itself establish that a separately configured bot or review action completed.[3][5]

{
  "Action": "Add",
  "Rows": [
    {
      "ProspectKey": "sample-prospect-001",
      "Name": "Avery Morgan",
      "Email": "avery@example.com"
    }
  ]
}

Fictional schema and key. Adapt the row columns and key rule to the receiving app; do not reuse this sample key for every prospect. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2][3]

This sample assumes ProspectKey, Name, and Email columns. Replace the sample key with your chosen stable key or use the app’s documented generation rule. Adapt the fields to the actual table rather than creating columns implicitly.