Better Item Update Triggers
I’m having trouble with item.update after recent changes to the Podio interface. When users edit an entry now, item.update gets fired each time they edit a field instead of when clicking "Save" at the bottom. Are there any API hooks that only fire once that I might be able to use as a trigger?
I know there’s item.create, but I need to connect a trigger to items that are updated after being created. Any creative ideas are welcome. Thanks!
After reading a bit in this forum, it sounds like I need to verify that the trigger includes one specific field in the hook for item.update. I'm not sure how to accomplish this with Zapier handling the API connections.
My goal is to have a field that triggers an action only once based on the selection in that field changing. Thanks for any ideas or suggestions!
The hooks didn't change with our recent update and it's always been possible to edit individual fields on Podio. You can use field level webhooks that only fire when a specific field changes value. It's all documented here: https://developers.podio.com/doc/hooks
I don't know what Zapier supports, but I think it would be excellent if you reached out to them and suggest they implement field level webhooks if they don't already.
Ok, I've contacted Zapier about this to see where that gets me. I'm probably going to need a mini crash course in how to setup webhooks. I saw an example of how to use field level webhooks in this post (https://help.podio.com/hc/communities/public/questions/200516318-How-do-I-see-which-field-is-update-when-running-a-item-update-webhook-?locale=en-us):
$hook_url = "http://www.some-url.com/hook.php";
$field_id = THE_FIELD_ID;
PodioHook::create( "app_field", $field_id, $attributes = array('type' => 'item.update', 'url' => $hook_url) );
I just don't know how to use that with Zapier. The Zapier documentation says they support the following types of webhooks: polling, static, REST, and notification REST hooks. There's documentation here, but I'm still a bit out of my element with this type of work: https://zapier.com/developer/documentation/reference/
Hopefully, together, we can connect the dots. Thanks!
I just found a forum post from October 2013 that says Zapier only supports the "app" ref_type and not "app_field." (https://zapier.com/support/questions/2984/podio-field-update-webhooks/)
I'm still waiting to hear back from their support team, but I suspect they'll tell me what I'm trying to do is unsupported.
Anyhow, I did see there's a way to create a zap that include GET, POST, and PUT requests using custom webhooks. Perhaps I'll be able to implement field level hooks for Podio that way, but I still don't quite understand where the code for that hook fits into the workflow.
After hearing back from Zapier support, is sounds like there's no way to make this happen as of yet. They've "noted it for future development" and I asked is there's anywhere to formally submit a feature request.
I'm still trying to achieve a specific function for my client that has changed since since Podio was updated. Unfortunately, there is no way to distinguish one item.update trigger from another in the scenario I'm working within. If I had field level hooks, this would not be a problem, but since the hook is at the item level and the item gets updated each time a field is updated, we're getting duplicated actions.
Good thread, i think this is what i need too "field level hooks" so that if a status changes we only send an email once. I have sort of worked around it by using a condition of a keyword but if some other change is made to the app then it sends again which is not ideal. If there was some way of setting a limiter on the number of times a certain email could be sent per podio item that would be good too make sure we don't send duplicates.
Please sign in to leave a comment.