GitHub Engagement Tracking: Notifications via Slack, Teams, and Email

This workflow automates GitHub repository engagement tracking, sending notifications via Slack, Teams, and Email. Key nodes include Webhook for API triggers, GitHub Trigger for real-time events, Condition for security validation, Set for data sanitization, Function for event processing, Switch for engagement classification, Merge for notification consolidation, Slack, Microsoft Teams, and Email for alerts, and Webhook Response for results. To set up, download n8n from n8n.io for self-hosting or sign up at cloud.n8n.io. Create a GitHub personal access token at github.com/settings/tokens with repo and notifications scopes. Obtain Slack API credentials from api.slack.com/apps, Microsoft Teams OAuth2 credentials from dev.teams.microsoft.com, and SMTP credentials from your email provider. In n8n, add these under Credentials > Add Credential > GitHub API, Slack API, Microsoft Teams OAuth2, and SMTP. Import the workflow JSON via Workflows > Import. Configure the Webhook node (path: /repository-engagement-tracking, method: POST) with CORS headers (Access-Control-Allow-Origin: *). Use ngrok for local webhook testing. Set the GitHub Trigger to monitor stars, forks, and issues for a repository (e.g., owner: your-username, repository: your-repo). Ensure HTTPS for secure transmission. Test by starring your GitHub repository or sending a POST request to the webhook with JSON (e.g., {eventType: 'star', repositoryOwner: 'your-username', repositoryName: 'your-repo'}). Include headers (x-api-key, x-repository-authorization). Validate outputs in the Set node for devHubConnectRepositoryResponse (e.g., success: true, repositoryResults.stars > 0). Handle errors like invalid GitHub token (401 response with 'REPOSITORY_SECURITY_VALIDATION_FAILED') or incorrect repository details (check owner/repository in GitHub settings). For issues, confirm HTTPS, valid credentials, and webhook configuration. Deploy by saving and enabling the workflow, ensuring triggers are active. Test with a repository star to verify notifications in Slack (#development), Teams (development-team), or email. Check Webhook Response for communityMetrics (e.g., socialProofLevel: 'emerging'). If notifications fail, verify channel settings and node connections in n8n’s editor.