Use return values from webhooks

• Configure the return value for a webhook
• Use the return value in an automation
• Use nested fields from the response
• Use a value in an array from the response
• Tips for debugging return values
• Limitations with returned values

Configure the return value for a webhook

When configuring the task, optionally use the following settings to capture the return values from a webhook:

• Enable the Return value toggle
• Use the Specific types field to map the return values in the JSON response to AppSheet data types

Use the return value from a webhook in an automation

To use a return value from a webhook in an expression that is defined after this task in the automation, refer to the output using the following syntax:

• [StepName].[FieldName]

For example, if the Call a webhook task named Call Address Service captures the following return values:

To reference the return values, use the following format: [Call Address Service].[FieldName]

For example:

CONCATENATE([Call Address Service].[ZipCode],[Call Address Service].[StreetName],"")

Use a nested field from the response

AppSheet supports nested objects to any arbitrary level in the response. You use nested fields by using the . (dot) separator.

For example, if the response data for an employee contains the department information in the response as follows:

"name": "John Doe",
"department": {
   "name": "Finance"
}

You could reference the name of the department using the following syntax:

[StepName].[department.name] // this returns "Finance"

Use a value in an array from the response

Use a value in an array from the response using the INDEX() function.

For example, if the response data for an employee contains the organization information as an array in the response, as follows:

{
  "ID": 123
  "company": "mycompany",
  "function": {
    "role": "project-manager",
    "organizations": ["Finance", "Engineering", "Cloud"]
  }
}

You could reference the Engineering organization using the following syntax:

INDEX([StepName].[function.organizations],2) // this returns "Engineering"

Tips for debugging return values

The following sections provides tips for debugging return values:

• Error messages
• Timeout values

Error messages

If a type conversion fails, bot execution will still succeed but an error message will be reported in the Automation Monitor.

The following table lists the error messages returned based on the JSON mapping issue.

Timeout values

Timeouts are handled as follows:

• When comparing the following values, the minimum timeout value will be used:
  • Bot execution timeout
  • Webhook task timeout
• For automations with scheduled events, the maximum timeout is 5 minutes; for automations with data change events, the maximum timeout is 2 minutes.

Limitations with returned values

Return values from webhooks are only supported for:

• HTTP GET, PATCH, POST, PUT, and DELETE methods
• JSON file formats
• Nested objects in the JSON responses, such as:

  {
  "ID": 123
  "company": "mycompany",
  "employee": {
    "lastname": "Doe",
    "firstname": "Jane"
  }
}

• Flat arrays of same types, such as:

  {
  "ID": 123
  "company": "mycompany",
  "function": {
    "role": "project-manager",
    "organizations": ["Finance", "Engineering", "Cloud"]
  }
}

At this time, return values from webhooks are not supported for:

• Reusable automation components
• Asynchronous HTTP calls (enable Run Asynchronously)
• Other file formats, such as XML
• Nested arrays of complex types, such as:
  
  {"company": "mycompany", 
    "Employees":
       [{
          "lastname": "Doe",
          "firstname": "Jane"
       },{
          "lastname": "Doe",
          "firstname": "John"
       }]
}