GitHub and Google Sheets workflows you can build
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made template Log every newly opened pull request in Google Sheets
A Filter keeps the opened events from the pull request trigger, and each PR becomes a row with title, author, branch and link, ready for a weekly review or client report.
New / Updated Pull Request→Filter→Add New Row
View the template
Ready-made template Email the team and log each new star on the repository
Open source maintainers get a short email for each new star and a row with the stargazer and date, which turns into a growth chart in the sheet.
New Star→Email (SMTP)→Add New Row
View the templateKeep a release history sheet for release notes
Each published release adds a row with tag, name, date and notes, so support and marketing can see what shipped when without a GitHub account.
New Release→Add New Row
Mirror issue status in a client-facing tracker
When an issue is edited, closed or labeled, the workflow finds its row by issue number and updates state and labels, or adds the row if the issue is new.
New / Updated Issue→Lookup Row Data→Router→Update Row
Record failed GitHub Actions runs for later review
A Filter keeps runs that finished with a failure, and each one is logged with workflow name, branch and link, which shows which pipelines break most often.
Workflow Run Completed→Filter→Add New Row
Open GitHub issues from rows in a planning sheet
Product owners add requests to a sheet. Each new row creates an issue with its title, body and labels, and the issue number is written back to the row.
New Spreadsheet Row→Create Issue→Add Labels to Issue→Update Row
Refresh an open issues tab every Monday
A Schedule runs List Issues for the repository and imports the result into a tab, so the weekly planning meeting starts from a current list.
Schedule→List Issues→Import CSV or JSON to Existing Sheet