ManualTrigger Automate

ManualTrigger Automate enables seamless monitoring of multiple GitHub repositories through webhooks, allowing for automated registration and deletion of webhooks. It simplifies management by sending real-time notifications to Slack and Telegram whenever changes occur, ensuring you stay updated without manual checks. This workflow enhances productivity and communication, making it easier to track project developments efficiently.

7/8/2025
19 nodes
Complex
webhookcomplexsticky notesplitoutslacktelegramadvancedapiintegrationcommunicationnotificationbot
Categories:
Communication & MessagingComplex WorkflowWebhook Triggered
Integrations:
Sticky NoteSplitOutSlackTelegram

Target Audience

This workflow is designed for:
- Developers who want to automate the monitoring of multiple GitHub repositories without manual intervention.
- Project Managers who need to keep track of changes in repositories and receive real-time notifications.
- DevOps Engineers looking to streamline their deployment processes by integrating GitHub events with communication tools like Slack and Telegram.
- Teams that require collaborative tools to stay updated on project developments and changes.

Problem Solved

This workflow addresses the challenge of manually monitoring multiple GitHub repositories for updates. By using webhooks, it eliminates the need for constant polling, allowing users to:
- Automatically register and delete webhooks for any number of repositories.
- Receive immediate notifications via Slack and Telegram whenever changes occur, thus enhancing team communication and responsiveness.

Workflow Steps

  • Trigger the Workflow: The workflow starts when the 'Test workflow' button is clicked, initiating the process.
    2. Define Repositories: The user specifies which GitHub repositories to monitor by inputting their URLs in the 'Repos to Monitor' node.
    3. Split Repositories: The 'Split Out' node divides the list of repositories into individual items for processing.
    4. Register Webhooks: For each repository, a webhook is registered using the 'Register Github Webhook' node, allowing GitHub to send updates about events like pushes and pull requests.
    5. Handle Webhook Events: When a webhook event occurs, the 'Webhook Trigger' node captures the event data.
    6. Extract Relevant Data: The 'Fields' node processes the incoming data to extract important information such as the repository name, author, commit date, and modified files.
    7. Notify Users: Notifications are sent via Slack and Telegram using the respective nodes, informing users of the changes in the monitored repositories.

    • Customization Guide

    To customize this workflow:
    - Add More Repositories: Update the 'Repos to Monitor' node with additional GitHub repository URLs you wish to track.
    - Change Notification Channels: Modify the Slack and Telegram nodes to send notifications to different channels or groups as needed.
    - Adjust Webhook Settings: Customize the webhook settings in the 'Register Github Webhook' node, such as the events you want to listen to or the URL for the webhook.
    - Format Notifications: Edit the message templates in the Slack and Telegram nodes to include specific details or change the format to suit your team's preferences.