Metadata updated = Trigger
Sample data shows the status
Real data doesn’t.
Tried nearly everything and at a dead-end.
Operations severely impacted & we are going to lose clients if this persists throughout this week
Hi @Tzizzy you can reference this template where you will need to filter out the specific status text to continue on the subsequent steps.
Unfortunately Zapier doesn’t create the webhook on until you publish and turn the zap on which is why there is sample data there. In order to surface actual data, we have to do a bunch of API calls to get this to work due to us not having a search API just yet. This is coming soon for all of the triggers but it is taking some time. I can prioritize the Metadata Value Updated one for you this week to make sure it returns actual data when testing.
If you are still running into issues please dont hesitate to reach out here and we will do our best to help!
Thank you
Prior to reaching out, we have published the zap and did a bunch of runs but this doesn’t solve our issue because regardless of the label/status change, it repeatedbly continues to get filtered out.
Even after using this template, we’ve facing the exact same result.
That doesn’t exist.
First SS - The filter step according to your template
Second SS- the consistently repeated Data ouput for every single run we make regardless of the label change
Limitations on SS attachment
We need this resolved ASAP because we’ve already lost $5000 of MRR due to this issue
To Iterate the real issue:
Real-time runs are NOT bringing us the label/status in the output.
Hi @Tzizzy could you explain a bit more about what exactly you are trying to accomplish here? Such as on status change send a slack message. This will allow me to try to reproduce to see if there is something I can help with.
Trigger: LABEL STATUS CHANGE on frame.io
Action: Whatever we want to do…
There are a variety of different actions we want to take across many zaps and this trigger is the foundation.. Example would be google sheets row lookups, code by zapier, filters, clickup status changes, etc.. the list goes on..
I’m unsure if the actions themselves are irrelevent if the trigger itself aren’t working.
Please advise
hi @Tzizzy I’m looking for your exact workflow so I can try to reproduce on my end to offer solutions if I am able to get it to work. So if you would be so kind as to provide some screenshots or steps that you’re taking in zapier, that would be helpful! You can DM me if it is sensitive information.
hi @Tzizzy I was able to get this to work with the following setup.
My goal was to send myself a slack message on an asset being marked as Approved.
I set up the Metadata Value Updated trigger to my workspace, then set the Zapier filter action to filter based on when the New Field Value contains the text Approved, it would then send me a slack message with that information but only when the text meets the filter conditions.
Charlie - the problem is that “New Field Value” is not populating in any live runs that we’re making. The only output data is as follows:
So what ends up happening is the filter always stops because “new field value”/“new value” doesn’t exist in the trigger step.
What is it that’s different about your Frame.io/Zapier that isn’t in ours?? This is what’s mindboggling.. Please advise
What is it that’s different about your Frame.io/Zapier that isn’t in ours?? This is what’s mindboggling.
I am very perplexed as well as I am just using the same Trigger you are using and can get it to populate.
I have a fix for this in a PR to populate actual live data and to prioritize status for this trigger which I will get out today pending PR approval.
@Tzizzy I just tried this by creating a new free zapier account with my personal gmail and also created a free frame.io account to start fresh, and I am able to populate that New Field Value with the sample data.
The only thing I can think of is you might have some weird caching going on inside Zapier. Can you try creating a new zap with the Metadata Value Updated trigger and see if that populates for you?
Still the same result.
@Tzizzy We have a few people unable to reproduce your issue as we are all able to populate the fields. We are finishing up the PR and will have something out for you soon (it will require you to update to the latest Frame.io V4 version in Zapier FYI)
Just to have an idea, when would this update happen?
Ideally tomorrow if all goes well! I’ll follow up once it’s live.
Thank you so much
Putting professionalism aside, you and the team are about to be more clutch than Kobe.
I’m looking forward to the update tomorrow!
Hey Charlie - how are things looking?
hi @Tzizzy the work day just started for us on the east coast so I’m following up on this atm
@Tzizzy this is now live. You should refresh your page and ensure you are using the latest V4 version 1.0.18 to get this change.
PLEASE NOTE: this will give you 3 of the latest metadata value changes as options, while prioritizing status (As that is the most commonly used metadata value). This will be more robust once we implement our search api in the future.
You’ll know you are on the correct version if when selecting the Frame.io V4 version and twirl down the caret you see 1.0.17 as the last version under Frame.io V4 (1.0.18 is the latest version)
Thank you so much Charlie - I’m unfortunately facing the EXACT same issue despite following these steps.
Something is telling me there was something done incorrectly by the team that switched us over from V3 to V4.
Please advise