Automating Bug Reports with Tally and Make
When building my first proper Android app, Timety , I ran into a common issue: I wanted to collect user feedback, but since my app is privacy-focused, I wanted to avoid forcing users to create an account just to report a bug. I found a great form-builder called Tally and created a feedback form. However, this introduced a new problem. Tally sends form submissions via email, but I manage my…
When Timety, a user's first proper Android app, was created, the developer, Timety, faced a common issue: collecting user feedback without forcing users to create an account. The developer found a form-builder called Tally and created a feedback form. However, Tally sent form submissions via email, which conflicted with the user's management of project boards, bug reports, and feature requests on GitHub. To solve this, the developer built an automated workflow using Make to connect Tally, GitHub, and Discord.
The user's goal was to route three types of Tally form submissions: bug reports, feature requests, and general feedback. The workflow overview is as follows: Tally form submissions trigger a workflow in Make, which splits into three branches based on the submission type. Top and middle branches handle GitHub Issues, while the bottom branch handles GitHub Discussions.
The workflow uses a router to split the branches, formats media URLs properly for GitHub Markdown, creates GitHub Issues or Discussions, and sends alerts to Discord.
To create GitHub Issues, the developer used a GitHub module with a POST request to the GitHub GraphQL API. The mutation creates an issue with a specific repository ID, title, body, and label. The body variable can be standard Markdown, allowing for easy formatting. The GitHub IDs for the repository, labels, and discussion categories need to be found using the GitHub GraphQL API Explorer.
For Discord notifications, the developer passed the response URL from GitHub into a Discord message module. Discord supports a subset of Markdown syntax, making it easy to format the notifications. This pipeline, while requiring some initial setup, provides a seamless way to collect and manage user feedback on GitHub.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
