Make sure that you are using the group’s name and not the name of the category that you allow the group to access. You can find the group’s name in the URL for the group, or from the group’s Name field:
If that does not resolve the issue, make sure that the Discourse API key you add to Zapier is a global All Users API key. Also, make sure that the API Username set on Zapier has permission to add users to the group. Any admin username on your site will work for this.
Let me know if this doesn’t resolve the issue for you.
You can invite the user to multiple groups by adding a comma separated list of group names to the group_names field on Zapier. Discoure doesn’t have the concept of sub-groups, so you will need to add the name of each group you want to invite the user to.
From the screenshot you have provided, it looks like you are trying to give the user access to a category and all of its subcategories. Instead of creating a group for each subcategory you could just allow a single group to access the category and all of its subcategories. This is configured on the Security section of the category’s edit page.
I have another question, maybe you (or @simon) could help me in that :
With Zapier, is there a way to give access to a New group, for people who are already members of Discourse ?
Basically, here is my workflow :
1/ A member joins one of my courses
2/ Zapier takes his email from my learning platform, and send him an invite to my Discourse + add him automatically to the right group, related to the course he just joined.
3/ Sometime, a few months later, this same member will join Another course : So, with my actual process, my Zapier will send him a new invite to Discours, whereas he is already a member, so the invite will not work.
I would need Zapier to give him access to a new group, if he is already a member of my Discourse.
Do you see a quicker way to notify the user ? (It’s ok if it’s a basic message from discourse, just like the one the user receives if I tick the checkbox “notify the users.”
Your solution is great, but as I have a lot of groups and automations, it could be great if I could just add “one” data type, for example to just “activate” the notification, instead of creating 30 new zap
It sounds like a permission issue with either the Api-Key or Api-Username. Try checking both of those on your Discourse site. Make sure that the user you have supplied for the Api-Username is still active on the site and that the Api-Key has either the Global scope, or has a Granular scope with the Invites scope box checked.
I’m bumping Juliano’s message because I tried this just now and experienced the same thing. How do I ensure that the invitation I create is an email invitation? I seem to be able to create only link invitations, although those work just fine.
Zapier’s Discourse integration app appears to have a defect: it maps both the “email” and the “skip_email” POST request body value to the same key: “skip_email”. This results in Discourse receiving an HTTP POST request with no “email” item in the request body, so the invite is created as a “link” invite rather than an “email” invite.
I’m sending Zapier a support email. We’ll see what happens.
If I use Zapier’s generic Webhook feature, I can create the invitation, but Discourse isn’t sending the email, so I need to figure out why not. I’ll follow up when I learn more.