We use Zapier to automate the task of identifying mentions of GitLab across our Community Response channels and generally convert them to actionable Zendesk tickets
The Zapier subscription runs on the Team plan, and is shared with the rest of the GitLab team
Zapier vault. Please file an access request if you cannot access that vault.Once logged in, you can access, edit and create Zaps in the Community Relations folder
After editing or creating a new Zap, remember to turn it on with the toggle switch next to the task's name on the Zap's list.
List of Zaps that are enabled on the Community Relations folder.
| Zap | Description |
|---|---|
| about.gitlab.com + devops-tools comments | GitLab blog comments to #mentions-of-gitlab Slack channel, and DevOps Tools pages comments to Zendesk and #devoptools-comments Slack channel |
| docs.gitlab.com comments | GitLab documentation comments to #docs-comments Slack channel. Monitored by the Technical Writing team |
| Community Relations MR Updates | All merged MRs with Community Relations label posted to #community-relations Slack channel |
| Hackernews: Slack notifications for front page mentions | Hackernews: front page stories to #developer-evangelism Slack channel |
| Hackernews: Slack Notifications for mentions | Hackernews: mentions to #hn-mentions Slack channel |
| GitLab Swag Store | GitLab store order to Printfection order |
| Student Spotlights Application Alerts | Student Spotlights form submission notifications to #student-spotlights-applications |
