Sync Android env config to Gradle files with GitHub and Slack alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 28 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects GitHub and Slack.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Check if .env.staging Changed (Code): runs custom JavaScript code
- Proceed Only if ENV Changed (If): checks a condition and branches into true / false
- Fetch .env.staging from Repo (GitHub): get (file)
- Fetch gradle.properties from Repo (GitHub): get (file)
- Parse .env.staging into Key-Value (Code): runs custom JavaScript code
- Parse gradle.properties into Key-Value (Code): runs custom JavaScript code
- Combine Env & Gradle (Merge): merges the data from its input branches
- Compare ENV and Gradle Variables (Code): runs custom JavaScript code
- Generate New Branch Name (Code): runs custom JavaScript code
- Get Latest SHA of main Branch (HTTP Request): calls an HTTP API
…plus 17 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - GitHub
n8n-nodes-base.github - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack
From the author
Environment Config Diff & Propagate for Android Builds This workflow automatically detects changes in the .env.staging file in a GitHub repository and keeps Android configuration files (build.gradle and gradle.properties) in sync.It creates a new Git branch,…