I'm new to Slack, using a free plan, and although I have no issue creating/populating channels/conversations using the Web API I cannot find a method to initiate invitation to new members.
I found many documentation using a deprecated method (https://slack.com/api/users.admin.invite) but this requires to add client scope to my App. This scope being legacy, I'm not able to add it to my App.
The only method I could find that seems to be performing what I need is admin.users.invite which is only available for Enterprise Grid customers.
Has anybody been able to work around that? Is thre any modern way to invite a new members using the API?
Thank for your help.
--
Stephan
Related
I've been searching about call an Azure function from CRM using ouath2, all the information that I found is about using function key to call the Azure functions from Dynamics 365.
Please if someone knows, please let me know if ouath2.0 is possible and how I can implement it?
I opened up a github issue to get update from Microsoft on this topic (as I know this is a challenge for a long time), it is still not positive, but may get some feature in near future. Until then we may have to use HttpClient in plugin directly instead of webhook.
This is a known challenge which Web Hooks doesn't even attempt to
address. Your options are limited. So this is a feature request rather
than a documentation issue.
If you attempt to call such an authenticated service using an
HttpClient in a plug-in, you have more options. But none of them today
represent best practices that we would recommend specifically at this
time, although I see people making them work in community posts.
Setting a certificate or secret value within the secure configuration
of the plug-in seems to be the best solution I've seen. But we are
looking to provide something better.
I want to build an application where it is possible for one client to call another client using webRTC. I've started to look into webRTC providers and I've found Toxbox among others.
Is it possible, using TokBox OpenTok, for a client to actually make a call to another client (similar as a regular phone call)? From their docs and specifications it seems that it is only possible to create a "session" (a room in which participants meet and chat).
Am I missing something, or are they only providing sessions that people join/leave?
Twilio seem to offer what I need here,
but I find it strange that I cannot find something similar at Tokbox.
Thanks,
Muff
Yes it is possible.
You need to make the distinction between the type of API the platform exposes to what you can do with it.
While the OpenTok API is built around the concept of a room/session - you can easily use that concept to create a call. There are many openTok developers who do just that.
Twilio indeed offers the same capability - as are many others (a partial list can be found in this report - https://bloggeek.me/webrtc-paas-report/ - while the report is a paid one, the list is available on that page
I'm new to mobile development and have been looking for a way to retrieve basic email information from simple POP3/SMTP email servers.
I've seen many posts on how to send email using numerous Cordova plugins, etc., but I'm simply trying to retrieve email information for various listing and analysis purposes.
Is this even possible?
Thanks for the help and suggestions on where to start.
Cordova does not have built-in functionality for POP3/SMTP access. As inside your codova app you are running in the javascript/webview sandbox, you don't have socket access, so you can't implement this kind of functionality there.
This leaves you no choice but to implement a Cordova Plugin. You are in Objective-C land now, but unfortunately there aren't any convenient classes in the standard framework for accessing POP3/SMTP. Your best bet is using a library like MailCore.
Details on how to implement a Cordova Plugin (as well as passing the relevant email data from and to your javascript layer) are outside the scope of a simple StackOverflow answer, but the process is (fortunately) well documented.
I am using POSTMAN collections to test my API before opening it up. I work with a team of developers and we would like to share/add/edit our collections amongst each other.
Doing this in source control is proving slightly tricky as can be seen in this comment on the GitHUB page:
This issue still persists in Version 2.1.1 (packaged)
The order of requests might be deterministic now, but the diff of an exported collection from two different machines and users includes data that are not related to the collections exported. The diff is full of owner and other id conflicts if there are several people working on the tests at the same time.
What is the best way that we have of putting this data in some sort of version control system? Any suggestions otherwise?
Putting it in a VCS undoubtly will give you some headaches as you mentioned. Your best bet is to use Postmans functionality to share collections. Here is from the documentation found at https://www.getpostman.com/docs/sharing
Starting with Postman v0.9.3 you have the ability to share and manage your collections more effectively. The first thing you will have to do is create a Postman account. You can create one using your email ID or a Google account. Once you are signed in after creating an account, the collections you upload on Postman are linked to your account. You can delete them later through the "Shared collections" item in the navigation bar dropdown.
Collection v2 format removes most, if not all, problems with portability.
http://blog.getpostman.com/2015/06/05/travelogue-of-postman-collection-format-v2/
The format must be highly portable so that it can be easily transported between various systems without loosing functionality.
Source Control in Postman
The question about sharing collections so that you can collaborate with your teammates has been answered a few different ways, as described in other answers of this question such as by sharing the collection or by syncing to a team account.
Version Control in Postman
The other part of the question was about putting the Postman data into a version control system. Postman introduced some version control features for the paid team accounts, like being able to restore collections to a certain point in the activity feed.
The paid team accounts also get integrations to sync their collections to their own version control systems like GitHub for example. If you're on a free account, you can use the Postman API to build your own similar integration to update the collections.
This blog post talks about some of the version control features in Postman.
UPDATE: Postman released forking and merging in Postman app v6.7.1 so you can manage version control in the app.
To automatically share your existing postman collection you can use Postman Pro.
It is a paid service provided using which a team lead can purchase the complete pro- scheme for his team and work as an admin.
Postman pro enables the following and many more:
Any changes in the API are automatically reflected in Postman for all member
Members subscribe to the collections from the Team library and get notifications of any changes.
For more information you can refer:
https://app.getpostman.com/dashboard/team-upgrades
This is what I use with my team of automation testers.
Basically I am trying accomplish 2 goals:
(1) Start a new Chatter Thread, and
(2) Comment on an existing Chatter Thread that has been loaded.
I am using OAuth to get connected and am able to successfully view and update custom objects but can't seem to figure out how to access and create a new chatter thread using the same [switchboard create:] method.
Does anyone have any idea where to start? I have tried their documentation and the best I could find was Asynchronous HTTPS posts with a body and a parent ID but how can I accomplish the same thing using the provided switchboard interface in the iOS client?
Any help appreciated,
Thanks,
~Arash
Please check out the Salesforce Mobile SDK for iOS on GitHub. There's a great FAQ and examples to access Chatter.
You can use the SFRestAPI to access Chatter objects. See the Chatter REST API documentation for queries and relationships between Chatter objects.