Contact field notification sent (or not) based upon category field value
Hi there --
I'm putting together a call log app for our reception desk.
We'll be using it to log all phone calls, but I need to avoid call recipients (contact field) to be notified when they've been passed a call, i.e. only notified of missed calls.
Right now, as I understand things, contact field notifications can not be dependant upon value entered in a category field.
Here is a more detailed use case :
Our receptionist gets a call; she fills in the form, either entering “Passed” or “Missed” in a dedicated “Status” category field.
Upon form submission, if the item has got “Passed” as value for Status, the item's Recipient (contact field) doesn't get a notification; if the item has got “Missed“ as value for Status, the Recipient gets notified.
My question is whether that would be a good case for me to start tackling the API. IOW, how complicate does that sound to accomplish usig the API? I saw a post on podiohelp.com about “ Event-based task creation”, which I think I could find my way around. What I'm trying to do initially looks simpler in that it doesn't involve webforms thus authentication etc., is it actually so? I've got basic web programming knowledge, meaning I can find my way around tweaking JS or PHP code. I don't intend to get deep into using the API myself, but I would like to find one or two simple enough stuff I could do by myself, which would help get a better idea of how the API works, so I can collaborate better with Podio developers.
I would appreciate it very much if a kind soul familiar with the API could provide an initial hint as to the logic I should use for this. I already went through the Items and Notifications documentation, and couldn't find what method to use so a notification can be muted/omitted upon item creation (if call is marked as passed), assuming that's the right logic to use in the first place (notifications on by default + mute if marked as passed, vs. notifications off by default + send if marked as missed).
Many TIA for your help.
It's correct that users will always get a notification when added as contacts on an item through the Podio interface.
It sounds like you are on the right track, and the good news is that you can in fact mute notifications when you create an item. If you set "silent" to true when creating the item no notification will be generated (see https://developers.podio.com/doc/items/add-new-item-22362). The same goes for a number of other operations that support the "silent" option.
Webforms could be an easier approach for you, but there you don't have the option to mute notifications.
I don't really understand your first question. How would you use what within the Podio interface itself? You may already know this, but just make it clear:
- Podio's interface and the mobile apps are based on the API. Anything you can do on Podio, you can do through the API. Anything you do through the API will show up on Podio.
- We have a feature at Podio we refer to as webforms, where you make it possible to enter data into an app via a public or by embedding a form on your own page. This feature is not related to the API as such.
- Where you to create items through the API, you would have to build your own html form in your PHP app and make sure the values entered by the user is appropriately submitted to the API.
As for your second question, no there is only the silent option, if you skip notifications you also don't see it in the stream.
As I understand things,
- either I use an external input form (which I called webform, not referring to the Podio feature, but as opposed to the Podio form) pointing to a PHP script that will handle the whole item creation process, making relevant ones silent,
- or I mute the app altogether in Advanced settings, and use a webhook to send a notification for relevant items only.
So basically, can option 2 work, or am I bound to use an external form for this?
Option 2 should work, and sounds like a lot less work than option 1. However, bear in mind that you can't create notifications via the API, they are always triggered by user actions, and once you have chosen to mute notifications in the settings for app, there is no way you can send the notification later.
Instead, I'd recommend that you create a task via API for the user to check out the item with the missed call. You also consider just letting the receptionist add the task manually, since she will be adding the call item manually in any case.
Please sign in to leave a comment.