Skip to main content

Hey!

while building our app we encounter a bunch of publishing task that say “Required field "xy" should appear and not be null in latest task” as well as “Required field "xy" should appear and not› be null in the sample of Zap”. All fields listed in the tasks are nested tasks. We use the output definition described here. An exerpc of the output fields is:
```

          {
            "key": "conversation__channel_id",
            "label": "channel_id",
            "required": true,
            "type": "string",
          },

```

both the trigger executions and the sample contain data for this field, e.g.:

```

          {
            "conversation”: { “channel_id”: “xyz” }
          },

```

but it seems like zapier does not expect nested but flat fields. The documentation clearly states that it's possible to define nested fields using the “__” and “ ]” syntax. What am I missing here?

Hi @psteinroe 

If you are building a Zap app integration using the Zapier Developer Platform, then best to post your topic in this category: Developer Zone

https://community.zapier.com/p/developer-zone


Hi @psteinroe 

If you are building a Zap app integration using the Zapier Developer Platform, then best to post your topic in this category: Developer Zone

aaad

When configuring triggers in a database or application, it is essential to ensure that nested output fields function correctly to maintain data integrity. Specifically, for output field X to appear, it must be populated and not null. This means that the trigger should be designed to check the conditions surrounding field X's data. If the necessary conditions are met and field X contains valid data, it should be included in the output.