Block 1 - Webhook
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 2
This workflow is provided as-is. Please review and test before using in production.
Fill iOS localization gaps from → Google Sheets and PR with placeholders (GitHub) This n8n workflow automatically identifies missing translations in files across iOS localizations (e.g., vs ) and g...
n8n-nodes-base.webhook, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.googlesheets, n8n-nodes-base.merge
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.
Original n8n.io source.strings → Google Sheets and PR with placeholders (GitHub)This n8n workflow automatically identifies missing translations in .strings files across iOS localizations (e.g., Base.lproj vs fr.lproj) and generates a report in Google Sheets. Optionally, it creates a GitHub PR to insert placeholder strings ("__TODO_TRANSLATE__") so builds don't fail. Supports DRY_RUN mode.
.strings files under Base.lproj or en.lproj and their target-language counterparts.fr) is updated with missing entries."__TODO_TRANSLATE__").{
"GITHUB_OWNER": "your-github-user-name",
"GITHUB_REPO": "your-iOS-repo-name",
"BASE_BRANCH": "develop",
"SHEET_ID": "<YOUR_GOOGLE_SHEET_ID>",
"ENABLE_PR": "true",
"IOS_SOURCE_GLOB": "**/Base.lproj/*.strings,**/en.lproj/*.strings",
"IOS_TARGET_GLOB": "**/*.lproj/*.strings",
"PLACEHOLDER_VALUE": "__TODO_TRANSLATE__",
"BRANCH_TEMPLATE": "chore/l10n-gap-{{YYYYMMDD}}",
}
Create GitHub Webhook
https://your-n8n-instance/webhook/l10n-gap-iosapplication/jsonPush, Pull RequestConnect credentials
| Tool | Needed For | Notes |
|---|---|---|
| GitHub Repo | Webhook, API for PRs | repo token or App |
| Google Sheets | Sheet output | Needs valid SHEET_ID or create-per-run |
| Slack (optional) | Notifications | chat:write scope |
| SMTP (optional) | Email fallback | Standard SMTP creds |
TARGET_LANGS_CSV (e.g., fr,de,es).IOS_SOURCE_GLOB and IOS_TARGET_GLOB to scan only certain modules or file patterns.IGNORE_KEY_PREFIXES_CSV to skip certain internal/debug strings.PLACEHOLDER_VALUE to something meaningful like "@@@".SLACK_CHANNEL and EMAIL_FALLBACK_TO_CSV appropriately.strings.xml (values → values-<lang>), same diff → Sheets → placeholder PR.TARGET_LANGS_CSV and loop tabs + placeholder commits per locale..stringsdict handling: Validate plural/format entries and open a precise PR.LANG → Slack handle/email map to DM translators with their specific file/key counts.fr has all keys present—placeholders keep the app compiling.| Issue | Possible Cause | Solution |
|---|---|---|
| No source files found | Glob doesn't match Base.lproj or en.lproj |
Adjust IOS_SOURCE_GLOB |
| Target file missing | fr.lproj doesn’t exist yet |
Will be created in placeholder PR |
| Parsing skips entries | Non-standard string format in file | Ensure proper .strings format "key" = "value"; |
| Sheet not updating | SHEET_ID missing or insufficient permission |
Add valid ID or allow write access |
| PR not created | ENABLE_PR=false or no missing keys |
Enable PR and ensure at least one key is missing |
| Slack/Email not received | Missing credentials or config | Configure Slack/SMTP properly and set recipient fields |
Want to expand this for Android? Loop through 5+ locales at once? Or replace GitHub with GitLab? Contact our n8n Team at WeblineIndia with your repo & locale setup and we’ll help tailor it to your translation workflow!
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Syncing iOS localization gaps with Google Sheets and GitHub PR placeholders |
|---|---|
| Complexity | intermediate |
| Nodes | 11 |
| Categories | Engineering, Multimodal AI |
| Author | WeblineIndia |
| Published | 19 Aug 2025 |
Use the JSON export at /data/workflows/7577/7577.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Fill iOS localization gaps from → Google Sheets and PR with placeholders (GitHub) This n8n workflow automatically identifies missing translations in files across iOS localizations (e.g., vs ) and g...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, Multimodal AI use case.