# Notification In Beta Action Integration
**URL:** https://community.glideapps.com/t/notification-in-beta-action-integration/59196
**Category:** Ask for Help
**Created:** [March 15, 2023, 1:26pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196 "2023-03-15T13:26:51Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Yasin\_Hassanien](https://community.glideapps.com/u/Yasin_Hassanien)
#### Post date: [March 15, 2023, 1:26pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/1 "2023-03-15T13:26:51Z")
What are the limits of the notifications and any plan to use it via API ?
Also is there a plan for one signal as an example as an integration in this case to be able to use one signal API as well ?
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [March 16, 2023, 1:10am UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/2 "2023-03-16T01:10:56Z")
> [@Yasin\_Hassanien](#):
>
> What are the limits of the notifications
You will most likely be charged updates for using it, and you should seriously consider it based on the updates quota for the plan you are using.
> [@Yasin\_Hassanien](#):
>
> Also is there a plan for one signal as an example as an integration in this case to be able to use one signal API as well ?
Haven’t seen that one mentioned.
---
### Author:  [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)
#### Post date: [March 16, 2023, 1:34pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/3 "2023-03-16T13:34:05Z")
FYI the push notification integration had a warning message which said it would consume 5 updates per use.
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [March 16, 2023, 1:36pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/4 "2023-03-16T13:36:16Z")
It’s not the final number, but I would warn any people trying to use the integrations to consider this part before they put it to production. You don’t want to see posts like “I run out of updates in no time this month. What can be the reason?”.
---
### Author:  [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)
#### Post date: [March 16, 2023, 2:36pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/5 "2023-03-16T14:36:36Z")
> [@ThinhDinh](#):
>
> warn any people trying to use the integrations to consider this part before they put it to production
Yes, I am seeing beaucoup updates using the Google Maps “address to coordinates” and “coordinates to address” **EDIT** It would be nice if, once run, the coordinates/address would “stick” in the table, instead of running each time the app is entered or the table refreshed. Why re-run to get the coordinates/address each time, since they will never change. Re-run only if the target data changes. Make it “sticky”.
Something weird when I was setting up the API, though, is it kept trying to use another one of my saved passwords, and I had to delete my saved password for Glide, and for the Glide community so it would use the “saved password” of the API key. No matter how many times I selected the correct password on this screen, it kept defaulting to a different password.
Also, the granularity of the coordinates returned is not that great. And because you can only get either the longitude or latitude from the column, you have to run it in two columns, which doubles the updates – my “coordinates to address” usage is half the usage to get the coordinates from address.
I don’t know if Glide has fixed the template links, but here is the template. I am sharing it because I had tried in the past to set up a “reverse geocode” javascript column, but never got it working correctly. Perhaps someone who knows js can take a look at it? That would be the best way – to avoid all updates…
[https://go.glideapps.com/template/WV63dSEnrUMv4QUkCkYK-template-published/dl/da19fa](https://go.glideapps.com/template/WV63dSEnrUMv4QUkCkYK-template-published/dl/da19fa)
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [March 17, 2023, 12:52am UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/6 "2023-03-17T00:52:30Z")
> [@David\_Gabler](#):
>
> It would be nice if, once run, the coordinates/address would “stick” in the table, instead of running each time the app is entered or the table refreshed. Why re-run to get the coordinates/address each time, since they will never change. Re-run only if the target data changes. Make it “sticky”.
I think you were using the column type instead of the action.
If you use an action, let’s say an on-submit action of a form that has an address, it writes the lat and lon in 1 go, and that should stick. In this case it’s not a column type, so I don’t think it refreshes every time you enter the app or the table refreshes.
---
### Author:  [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)
#### Post date: [March 17, 2023, 1:32am UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/7 "2023-03-17T01:32:39Z")
> [@ThinhDinh](#):
>
> think you were using the column type instead of the action.
You are correct. I did not know it could be an action. What would the use case be for a column since it could literally eat your entire update count if you have 1000 rows…
---
### Author:  [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [March 17, 2023, 2:09pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/8 "2023-03-17T14:09:29Z")
> [@David\_Gabler](#):
>
> What would the use case be for a column since it could literally eat your entire update count if you have 1000 rows…
It should be cached, if it’s not I would argue that’s a bug.
---
### Author:  [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)
#### Post date: [March 17, 2023, 2:28pm UTC](https://community.glideapps.com/t/notification-in-beta-action-integration/59196/9 "2023-03-17T14:28:08Z")
I agree it either should not count against the updates or should be cached unless the value changes and needs to be recalculated.