# Insufficient permission ("key" is undefined) when using the Update Operation on imported data

**URL:** <https://community.directus.com/t/insufficient-permission-key-is-undefined-when-using-the-update-operation-on-imported-data/1319>\
**Category:** Help\
**Tags:** api\
**Created:** [October 11, 2025, 8:50am UTC](https://community.directus.com/t/insufficient-permission-key-is-undefined-when-using-the-update-operation-on-imported-data/1319 "2025-10-11T08:50:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hrtlkr29](https://sea2.discourse-cdn.com/flex002/user_avatar/community.directus.com/hrtlkr29/32/160_2.png) [@hrtlkr29](https://community.directus.com/u/hrtlkr29)\
**Post date:** [October 11, 2025, 8:50am UTC](https://community.directus.com/t/insufficient-permission-key-is-undefined-when-using-the-update-operation-on-imported-data/1319/1 "2025-10-11T08:50:16Z")

</div>

Hi guys, I’m currently adding a flow to update the coordinates of an item on create/update. The flow runs just fine if I edit the item manually. But when I import the items, the flow failed at the “Update Operation” step because the `key` is undefined.  
I wonder, instead of `“{{$trigger.keys}}”`, what should I use here to ensure I get the right key for the operation?  
Thank you!

 ![image](https://us1.discourse-cdn.com/flex002/uploads/directus/original/2X/3/30de839c88e2563e9d6bc26ee058265884b0d13e.png)

---

<div class="post-metadata">

**Author:** ![bryantgillespie](https://sea2.discourse-cdn.com/flex002/user_avatar/community.directus.com/bryantgillespie/32/33_2.png) [@bryantgillespie](https://community.directus.com/u/bryantgillespie)\
**Post date:** [October 13, 2025, 3:20pm UTC](https://community.directus.com/t/insufficient-permission-key-is-undefined-when-using-the-update-operation-on-imported-data/1319/2 "2025-10-13T15:20:59Z")

</div>

Hi there @hrtlkr29 👋 Welcome to the community!

Are you able to share some more details?

I can’t see the trigger data from your example, but the keys you’re looking for might be under something like `"{{$trigger.payload.keys}}"` instead of `“{{$trigger.keys}}”`, depending on how you’re “importing” the data.

Take a look at the payload from the trigger in that flow to be sure.

[Here’s a solid doc on the Data Chain](https://directus.io/docs/guides/automate/data-chain) within Flows. I’d definitely check it out.

Each operation in a flow appends its data to the flow object under the key name that you use. So you would be able to access the key under the previous operation.

For example, if you have an operation called `read_data`, the results would be available as `read_data` in subsequent operations. So you could use `"{{read_data.id}}"` for example.