We have tried to send notifications to Microsoft teams. We have created a bot using this we can send but users want to initiate the conversation.
Also tried graph API shows 401 error.
We want to send notifications to Bot or API without the user initiating the conversation. i.e. sending notification direct to user chat.
Please help?
You can send message to user with out user interaction using graph API. Proactive messages are initiated by bots to start conversations with a user. They serve many purposes including sending welcome messages, conducting surveys or polls, and broadcasting organization-wide notifications. Proactive messages in Teams can be delivered as either ad-hoc or dialog-based conversations. Please check Proactive installation of apps using Graph API and send messages
I am planning to use Yammer APIs to develop an App that will assign task to other members with in a group. Can we send push notification from one device to another device while assigning task to other member using Yammer APIs?
There are no APIs provided for generating specific notifications to end users. Yammer puts users in control of notifications they receive so you should just post a message to a group with the available APIs, and if the user has notifications enabled, then they may receive notifications.
Is there a way to achieve twitter like push notification via AWS SNS?
SNS send notification to the user when something is happen him or her?
As i know the best way is to create a topic per user.
When user relate event happened,we publish a notification to the topic.
As AWS described the max topic number is 100,000 per account currently.
What if i've 1,000,000 users, it will not work.
Is there a more scalable scheme?
beeth0ven,
SNS supports publishing to a Topic of subscribed device endpoints or direct publishing to individual endpoints. In your case, you'll want to implement direct publishing to each individual endpoint. This allows more control and personal engagement but also means that you'll need to manage those endpoints in your own database and associate each endpoint to a user of your mobile app. Instead of publishing to a TopicArn, you'll publish individual messages to a TargetArn, which is the SNS Platform Endpoint that represents an app and mobile device. TargetArn is also the same call to send an SMS message to an individual phone number.
SNS Publish CLI: (see --target-arn)
http://docs.aws.amazon.com/cli/latest/reference/sns/publish.html
Direct Publishing via the Console:
http://docs.aws.amazon.com/sns/latest/dg/mobile-push-send-directmobile.html
I am trying to move my existing iOS push notification infrastructure over to amazon SNS mobile push.
I exported all my tokens from my local db into an SNS application (using CSV). Now I want to send push notification to all my 10,000 users. I think the only way is to create a topic and subscribe all the users to that topic then publish message to that topic.
Is there any easy way to subscribe all the 10,000 users who I have imported into the system to a topic?
Thanks for any help!
It sounds like you have created the Amazon SNS Platform Application and imported your tokens as Amazon SNS Platform Endpoints.
What kind of notification are you sending?
If you send a custom message to each user, use Direct
Addressing. With this approach, you
Publish to each EndpointARN.
If you send the same message to all users, use topics. You need to subscribe your endpoints to a topic. When you are ready to send, Publish to the TopicARN. Amazon SNS will handle delivery to all endpoints subscribed to that topic. Amazon SNS currently does not provide a bulk subscribe API, so you will have to invoke Subscribe once per EndpointARN.
Full disclosure: I work for AWS on Amazon SNS.
Unfortunately there is no way so far... see Bulk push endpoints subscription to a topic on AWS Discussion Forum.
Hi there langelvicente,
Thanks for this feature request. I've passed this back through to the SNS Service Team for review.
Best regards,
Phil P
This is now possible with subscribing mobile endpoints to topics. The default subscriber limit was increased.
Q: Are there limits to the number of topics or number of subscribers
per topic?
By default, SNS offers 10 million subscriptions per topic, and 3,000
topics per account. To request a higher limit, please contact us at
at http://aws.amazon.com/support
http://aws.amazon.com/sns/faqs/?nc2=h_ls
If you have an application full of endpoints which you want to bulk subscribe to a SNS topic you can do so from the AWS SNS dashboard by:
Going to that application in SNS
Waiting until the 'total items' count at the bottom has completed its count (ie all items are listed)
Checking the select all check mark above the list of endpoints (screenshot attached)
Tap on platform action > subscribe endpoints to topic
Enter your topic ARN and click create subscription
The process will begin and it will stall your web browser but let it be as it takes time and if you want to see the subscriptions to the topic increasing you can use the AWS CLI with :
aws sns get-topic-attributes --topic-arn "[YOUR TOPIC ARN]"
note the "SubscriptionsConfirmed" value
Yes, but caveat: they each must accept your effort to enroll them into push messaging. That means that for each token in your database, each individual must consent to receiving future messages from you (via SMS and email, that is).
Each address (tel #, email) becomes an endpoint, and you can use SNS to create a topic, then subscribe each endpoint. After a confirmation email is sent to each endpoint (person on your list), they must confirm, in order to begin receiving your stream of messages via text or email.
Unfortunately, this confirmation/consent event is dicey, and must be handled correctly. Your ARN's title must be succinct (7 letter via SMS, no subject line allowed). Hence, you must contact them via SMS using a name they will recognize (the SMS message will arrive via short code, 304-something), and can be refused and/or blocked.
Not trivial! Best to investigate using push messages via mobile app. This will avoid the coveted SMS space, but you might consider putting out a blast to email and/or SMS, in order to get them using your mobile app. Apparently, given the immediacy of SMS, folks will be reading your first confirmation within 20 seconds. This could be a good thing, if they confirm, then accept your future messages.
Am doing this right now, and am preparing to be recognized by name using my initial blast -- apps that create anonymous SMS will be banned through iTunes!
I have an existing web app built using Ruby on Rails. It already has a built-in email messages feature. Our users have requested for a functionality which is able to do the following (for US users only):
Get a unique and new US phone number which is tied to their registered email address (user ID in our web app
For others (users or non-users) to be able to send our registered SMS messages to this new number. The registered user will get a notification that he has received an SMS and will then go to Messages module to retrieve the SMS
The registered user should also be able to send an SMS message from his Message module to other users and their mobile numbers. These users will not be receiving the content of the SMS but rather be getting a notification that they have receved a SMS from our registered user and now they need to either creae a new ID or login using existing credentials and authenticate phone number in order to retrieve SMS from our user.
Question: What Ruby Gem could be used for such functionality?
Also, are there APIs and open source code available for such functionality?
I would also like to kee my costs low for all the above as we are still a start-up company.
Thanks in advance.
You might consider checking out Twilio (disclosure: I work for Twilio).
Twilio has a Ruby gem that provides a high-level API for sending SMS messages and buying phone numbers. You can also receive incoming SMS messages to a number by specifying "webhook" URLs that will receive an HTTP request when a message is received. You can sign up for a free trial account here.
Some relevant bits of documentation:
Sending an SMS
Find an available number (note: you can also do this through the GUI)
Buy the number you found (note: you can also do this through the UI on the site)
Responding to incoming messages