Developer Relations tools: Workato

Developer Relations teams use Workato to automate workflows between tools and platforms.

Workato maintainers

Updated or new workflows need to be requested from the Enterprise Technology team maintaining Workato.

Current workflows

Type Workflow Description Involved Tools
Blog-to-Forum Post new Blogs to the GitLab forum GitLab blog post is posted as a new forum topic GitLab Blog RSS feed, Discourse
Forum-to-Slack New forum topics in the GitLab Duo category Reads Discourse forum RSS feed https://forum.gitlab.com/c/gitlab-duo.rss and posts to #gitlab-duo-forum-posts channel. Discourse forum, Slack
Blog-to-Slack New blog posts - GitLab Reads GitLab blog RSS feed and posts to #developer-advocacy-updates channel. GitLab Blog, Slack
Blog-to-Slack New blog posts - GitHub Reads GitHub blog RSS feed and posts to #developer-advocacy-updates and competitive Slack channels. GitHub Blog, Slack
Blog-to-Slack New blog posts - CNCF Reads CNCF blog RSS feed and posts to #developer-advocacy-updates channel. CNCF Blog, Slack

gitlab-blog Forum Bot

The gitlab-blog user is used to automatically post new GitLab blog posts as a new topic to the Community category. This process is controlled through Workato which reads the blog RSS feed at https://about.gitlab.com/atom.xml and posts a new topic using the admin API key and gitlab-blog user for each new entry there.

The gitlab-blog credentials and admin API key are stored in the 1Password Marketing vault. Admins can directly edit the user in Discourse without login.

History

Zapier was migrated to Workato in 2025, content in this internal issue.