Home

Automatic Yammer group creation via API

%3CLINGO-SUB%20id%3D%22lingo-sub-1058850%22%20slang%3D%22en-US%22%3EAutomatic%20Yammer%20group%20creation%20via%20API%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1058850%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3EHoping%20this%20is%20the%20right%20place%20to%20post...I%20have%20a%20requirement%20from%20a%20client%20to%20automatically%20create%20Yammer%20groups%20as%20part%20of%20a%20SharePoint%20Online%20provisioning%20process.%20I%20understand%20there%20are%20(theoretically)%202%20ways%20to%20do%20this%2C%20but%20I%20am%20limited%20in%20both%3A%3C%2FP%3E%3COL%3E%3CLI%3EUsing%20an%20undocumented%20Yammer%20API%20endpoint%20to%20POST%20to%20groups.json%20in%20the%20following%20manner%3A%3CBR%20%2F%3E%3CPRE%3Ehttps%3A%2F%2Fwww.yammer.com%2Fapi%2Fv1%2Fgroups.json%3Fname%3DExample%26amp%3Bprivate%3Dfalse%3C%2FPRE%3EHowever%2C%20this%20returns%20a%20301%3A%20Moved%20Permanently%20error%2C%20which%20leads%20me%20to%20believe%20POSTing%20to%20this%20endpoint%20no%20longer%20works.%20(Note%3A%20I%20have%20the%20Yammer%20app%20set%20up%20and%20I%20am%20passing%20the%20OAuth%20dev%20token%20properly)%3C%2FLI%3E%3CLI%3EUsing%20Microsoft%20Graph%20API%20with%20O365%20Group-connected%20Yammer%20groups.%20Creating%20a%20group%20via%20API%20works%20fine%20in%20this%20method%2C%20but%20there%20is%20no%20way%20to%20retroactively%20use%20that%20group%20in%20Yammer.%20In%20other%20words%2C%20if%20I%20manually%20create%20a%20Group%20in%20Yammer%20and%20the%20proper%20configuration%20is%20in%20place%2C%20I%20will%20get%20an%20O365%20Group%3B%20however%2C%20if%20I%20first%20create%20the%20O365%20Group%20(which%2C%20due%20to%20the%20lackluster%20Yammer%20API%2C%20seems%20like%20my%20only%20option)%2C%20I%20can't%20create%20a%20Yammer%20group%20from%20it.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20ideal%20process%20will%20work%20in%20this%20way%3A%3C%2FP%3E%3COL%3E%3CLI%3ECreate%20a%20SPO%20Communication%20site%20from%20a%20Site%20Design%2C%20which%20includes%20a%20call%20to%20Flow%3C%2FLI%3E%3CLI%3EFlow%20passes%20the%20name%20of%20the%20SPO%20Comm%20site%20as%20the%20intended%20Group%20name%20into%20a%20POST%20call%20on%20some%20RESTful%20API%20to%20provision%20the%20Yammer%20group%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAlas%2C%20I'm%20stuck.%20This%20seems%20like%20it%20should%20be%20a%20relatively%20common%20scenario%3B%20is%20there%20really%20no%20support%20for%20automated%20Yammer%20group%20creation%3F%20I'm%20open%20to%20any%20ideas%2C%20and%20thanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1058850%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAPI%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eprovisioning%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
fowley
Occasional Visitor

Hello!

Hoping this is the right place to post...I have a requirement from a client to automatically create Yammer groups as part of a SharePoint Online provisioning process. I understand there are (theoretically) 2 ways to do this, but I am limited in both:

  1. Using an undocumented Yammer API endpoint to POST to groups.json in the following manner:
    https://www.yammer.com/api/v1/groups.json?name=Example&private=false
    However, this returns a 301: Moved Permanently error, which leads me to believe POSTing to this endpoint no longer works. (Note: I have the Yammer app set up and I am passing the OAuth dev token properly)
  2. Using Microsoft Graph API with O365 Group-connected Yammer groups. Creating a group via API works fine in this method, but there is no way to retroactively use that group in Yammer. In other words, if I manually create a Group in Yammer and the proper configuration is in place, I will get an O365 Group; however, if I first create the O365 Group (which, due to the lackluster Yammer API, seems like my only option), I can't create a Yammer group from it.

 

 

The ideal process will work in this way:

  1. Create a SPO Communication site from a Site Design, which includes a call to Flow
  2. Flow passes the name of the SPO Comm site as the intended Group name into a POST call on some RESTful API to provision the Yammer group

Alas, I'm stuck. This seems like it should be a relatively common scenario; is there really no support for automated Yammer group creation? I'm open to any ideas, and thanks in advance!

Related Conversations