For now, node-yammer library is included in the package.

See with the developer if he can deploying it in the official npm registry.

Hi,
I am new to the hubot and want to integrate my hubot with yammer, Can u please tell me the procedure step by step. I know their are adoptors available for that purpose, but i dont know how to use adaptors to talk to hubot from yammer.

Thanks,
Krishna P

oauth1 is deprecated in yammer now. any updates for oauth2? looks like users will have trouble obtaining a secret token

Following this thread: #17

It seems that the group API has a limit of 50 groups which is problematic for the group_id resolver for big companies.

Have to look at use pagination capabilities.

Hey , love the yammer bot , its great. Got mine up and working with our enterprise yammer and it replies but seems to loop and reply the same message ,hits about 15 replies and then limit reached , any thoughts ?

Message creation status :201

Thanks for the effort.

Right now if hubot is a member of a private yammer group and messages are sent to this group, hubot doesn't get those messages (and hence never replies).
Right now I''d love to have a private group so I can test hubot on yammer, but long term, I think this is a useful feature regardless. I assume large organizations utilize private groups and would appreciate hubot being in the group.

Did the plugin error or something else？
It used to be good.

I exported all the env properties required (noted in the WIKI) and then started hubot with the following command:

bin/hubot -a yammer -n "Hubot yammer name"

No error ... subscription goes in successfully.

Using another yammer account I send "updates" (e.g. "hubot ping", "hubot help" etc) to the group listed in HUBOT_YAMMER_GROUPS, but get NO reply back. Don't know where to look next.

Hi,

I am not able to start hubot using Yammer adapter.

I have the following stack trace:

/home/hubot/bob_the_hubot/node_modules/hubot-yammer/src/yammer.coffee:149
        return callback(err, data.data);
                                 ^
TypeError: Cannot read property 'data' of undefined
  at /home/hubot/bob_the_hubot/node_modules/hubot-yammer/src/yammer.coffee:84:6, <js>:149:34
  at /home/hubot/bob_the_hubot/node_modules/hubot-yammer/src/node-yammer.js:11:19
  at Request._callback (/home/hubot/bob_the_hubot/node_modules/hubot-yammer/src/node-yammer.js:124:14)
  at Request.self.callback (/home/hubot/bob_the_hubot/node_modules/hubot-yammer/node_modules/request/main.js:108:22)
  at Request.<anonymous> (/home/hubot/bob_the_hubot/node_modules/hubot-yammer/node_modules/request/main.js:468:18)
  at Request.EventEmitter.emit (events.js:95:17)
  at IncomingMessage.<anonymous> (/home/hubot/bob_the_hubot/node_modules/hubot-yammer/node_modules/request/main.js:429:16)
  at IncomingMessage.EventEmitter.emit (events.js:117:20)
  at _stream_readable.js:920:16
  at process._tickCallback (node.js:415:13)

I wonder if I correctly set the environment variables. In particular, I am not sure which value I have to set to HUBOT_YAMMER_TOKEN and HUBOT_YAMMER_TOKEN_SECRET.

Using Yammer OAuth flow, I got an authorization code (callback url) and a token from the last returned JSON hash.

Thank you for your support.

Run for some time, yammer automatically offline，
What reason is this?
Where did your plug-in set the session time？
This is log:
[Thu Dec 14 2017 09:06:32 GMT+0000 (UTC)] INFO hubot-redis-brain: Using default redis on localhost:6379
[Thu Dec 14 2017 09:06:32 GMT+0000 (UTC)] DEBUG Parsing help for /home/ec2-user/hubot/yammer-bb8/node_modules/hubot-redis-brain/src/redis-brain.coffee
[Thu Dec 14 2017 09:06:32 GMT+0000 (UTC)] DEBUG Parsing help for /home/ec2-user/hubot/yammer-bb8/node_modules/hubot-rules/src/rules.coffee
[Thu Dec 14 2017 09:06:32 GMT+0000 (UTC)] DEBUG Parsing help for /home/ec2-user/hubot/yammer-bb8/node_modules/hubot-shipit/src/shipit.coffee
groups list : hubotTest
groups_ids list : 13282582

[Thu Dec 14 2017 09:11:32 GMT+0000 (UTC)] INFO keepalive ping
[Thu Dec 14 2017 09:11:32 GMT+0000 (UTC)] INFO keepalive pong: 404

[Thu Dec 14 2017 09:26:32 GMT+0000 (UTC)] INFO keepalive ping
[Thu Dec 14 2017 09:26:32 GMT+0000 (UTC)] INFO keepalive pong: 404

...............................
[Thu Dec 14 2017 10:01:32 GMT+0000 (UTC)] ERROR Error: Redis connection in broken state: connection timeout exceeded.
at RedisClient.connection_gone (/hubot/node_modules/redis/index.js:644:19)
at RedisClient.on_error (/hubot/node_modules/redis/index.js:405:10)
at Socket. (/hubot/node_modules/redis/index.js:279:14)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at emitErrorNT (net.js:1281:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
..........................................................
[Fri Dec 15 2017 01:46:32 GMT+0000 (UTC)] INFO keepalive ping
[Fri Dec 15 2017 01:46:32 GMT+0000 (UTC)] INFO Skipping keep alive, time to rest
[Fri Dec 15 2017 01:51:32 GMT+0000 (UTC)] INFO keepalive ping
[Fri Dec 15 2017 01:51:32 GMT+0000 (UTC)] INFO Skipping keep alive, time to rest
[Fri Dec 15 2017 01:56:32 GMT+0000 (UTC)] INFO keepalive ping
[Fri Dec 15 2017 01:56:32 GMT+0000 (UTC)] INFO Skipping keep alive, time to rest

Above is the log.
If you know the reason, please tell me.
thank you very much！！！

No tests at the moment so it should be doable :)

bin/hubot -a yammer

results in the following exception ...

[Thu Oct 11 2012 17:20:21 GMT-0600 (MDT)] ERROR Cannot load adapter yammer - TypeError: Object # has no method 'robot'
TypeError: Object # has no method 'robot'
at Object. (/opt/hubot/node_modules/hubot-yammer/src/yammer.coffee:7:28)
at Object. (/opt/hubot/node_modules/hubot-yammer/src/yammer.coffee:210:4)
at Module._compile (module.js:446:26)
at Object..coffee (/opt/hubot/node_modules/hubot/node_modules/coffee-script/lib/coffee-script/coffee-script.js:22:21)
at Module.load (module.js:353:31)
at Function._load (module.js:311:12)
at Module.require (module.js:359:17)
at require (module.js:375:17)
at Robot.loadAdapter (/opt/hubot/node_modules/hubot/src/robot.coffee:215:31)
at new Robot (/opt/hubot/node_modules/hubot/src/robot.coffee:47:14)
TypeError: Cannot call method 'on' of null
at Object. (/opt/hubot/node_modules/hubot/bin/hubot:105:19)
at Object. (/opt/hubot/node_modules/hubot/bin/hubot:109:4)
at Module._compile (module.js:446:26)
at Object.run (/opt/hubot/node_modules/hubot/node_modules/coffee-script/lib/coffee-script/coffee-script.js:79:25)
at /opt/hubot/node_modules/hubot/node_modules/coffee-script/lib/coffee-script/command.js:175:29
at /opt/hubot/node_modules/hubot/node_modules/coffee-script/lib/coffee-script/command.js:150:18
at [object Object]. (fs.js:123:5)
at [object Object].emit (events.js:64:17)
at Object.oncomplete (fs.js:1188:12)

export HUBOT_YAMMER_GROUPS="groups list"

How do I add new group(s) for hubot to recognize and be in the group? I do not want to stop hubot, add new group to HUBOT_YAMMER_GROUPS, and restart hubot.

Thanks!

The list of hubot adapters in the hubot documentation is being replaced with a link to a GitHub topic search. Add the hubot-adapter topic to your repository on GitHub to include it in this list.

/cc hubotio/hubot#1320

The "help" script doesn't work correctly because of a large overflow of request to the Yammer API.

That should be detected but I don't really know how to handle it.

In yammer conversations can be threaded.
So I think it'd be useful that when hubot replies, it replies to the sender in the same thread.

For example, instead of:

Ran: bot ping
Bot: PONG

It would be like

Ran: bot ping
   Bot: PONG (in reply to Ran)