[vinodhdavid]

We want to run this as a service, for eg with hubot you need to add the API keys in a config file which isn't that easy unless you have a dev to write something on top of it. We are planning to make the UX really simple on provide /pulling the data from your services.

[akerl_]

Adding API keys to a config hardly requires a dev.

And giving my API keys to you is much more dangerous.

[vinodhdavid]

We use OAuth so we don't store any API keystroke passwords. Well more than the ease we are trying to make this collaborative so you can add data to your team mate services easily.

[akerl_]

Not sure what you mean by "API keystroke passwords". Almost all major APIs these days that you'd be working with for your bot use either OAUTH, generated API token strings, or bot. So you're either storing an OAUTH token or a token that isn't OAUTH but that the user treats a lot like a simple OAUTH token (it is use-case-specific, can be revoked, is identified by its purpose, etc)

[diggan]

Ask a non-developer to just update the configuration file with the API keys received from whatever service and you'll get a confused look as an reply in most cases.

[GrinningFool]

Keep in mind that the people who have need of this kind of thing are typically dev , ops, or both. To neither group is updating a configuration file a major consideration.

It sounds like these may not be your target audience - but in that case, who is?

[vinodhdavid]

Well, its not just updating the config details its connecting other team mates apps together for eg you can create a google calendar event in your team mates calender by adding their name @teammate :)