How to modify nested values in Zapier Storage using API calls

Other Questions Zapier
1

I’m trying to work with Zapier’s storage system and need help updating nested data without replacing the entire record.

Currently, I have data structured like this:

{
  "project_abc": {"calendar_ref": "cal_reference_1", "deadline": "2018-11-15T14:30:00.000Z"},
  "project_xyz": {"calendar_ref": "cal_reference_2", "deadline": "2018-11-12T16:45:00.000Z"},
  "project_def": {"calendar_ref": "cal_reference_3", "deadline": "2018-11-18T19:15:00.000Z"}
}

I want to modify just the “deadline” field for a specific project without removing and recreating the whole entry. I tried using a PATCH request with the “set_child_value” action:

def modify_nested_value(self, main_key, nested_key, new_value):
    headers = self.build_headers()
    
    payload = {
        "action": "set_child_value",
        "data": {
            "key": main_key,
            "value": {nested_key: new_value}
        }
    }
    
    response = requests.patch(self.STORAGE_URL, headers=headers, json=payload)
    return response

The API returns 200 OK but my data stays unchanged. What am I doing wrong here?

2

had the same issue last month! the set_child_value action doesn’t exist in zapier’s api - that’s why u’re getting a 200 response but no changes. u need to GET the current data first, modify the specific field in js/python, then PUT the whole object back. it’s annoying but it works.

3

totally feel you! zapier can be a bit tricky with nesting. u gotta fetch the whole thing, update it in ur code, and then push it back with put. not ideal, but that’s how it works. gl!

4

Had this exact problem building a project management integration. Zapier Storage doesn’t support partial updates with PATCH operations like other REST APIs. Your set_child_value approach won’t work - that’s not a valid action parameter. You need a read-modify-write pattern instead. GET the entire record first, parse the JSON, update the nested field in your app logic, then PUT the complete modified object back to storage. It’s more verbose than what you’re trying, but it’s the only reliable way to handle nested updates in Zapier’s storage. Watch out for race conditions if multiple processes might update the same record at once.

5

Hit this same frustrating wall when I started using Zapier Storage for client work. Their API only does full record replacement - no partial updates at all. Your PATCH structure looks right for most REST APIs, but Zapier doesn’t support that set_child_value action you’re trying to use. Here’s what actually works: GET the existing record with the key, modify the nested property in your code, then PUT the whole updated object back. Don’t forget to handle cases where the initial GET fails because the record doesn’t exist yet. Also, make sure you’ve got solid error handling - if any step fails due to network issues, your data could end up inconsistent.