/w=3840,quality=90,fit=scale-down)
Maker
/w=3840,quality=90,fit=scale-down){kind=logo}
Type
Tags
Event Trigger
Action
nodeType
Status
Available
Batch Trigger
Jump to:
About
This GitHub Action detects changes to specified file types in your repository and sends the file content to a webhook.
Empty AI Block
What can you make?
- Monitor specific file types (like .mdx or .json)
- Automatically detect when files are added or modified
- Send file contents to external services
- Integrate with Lamatic Flow for further processing
Empty AI Block
Available Functionality
Batch Trigger
❌
Event Trigger
❌
Actions
✅ File Monitoring
- Secure webhook communication
- Authorization key support
- Custom webhook URL configuration
✅ Security Features
- Support for GitHub Secrets
- Secure storage of webhook URLs
- Secure storage of webhook keys
✅ Configuration Options
- Customizable file type filtering
- Flexible webhook endpoint setup
Install Steps
Create a Flow in Lamatic
To set up a flow in Lamatic with a webhook trigger, follow these steps to obtain the necessary webhook configurations.
Implementation Options:
- Create a Custom Flow
- Follow our comprehensive webhook integration guide.
- Learn how to configure webhooks as trigger events.
- Set up custom actions based on incoming webhook data.
- Use a Pre-built Template
- Start with our ready-to-use webhook template.
- Quickly implement common webhook scenarios.
- Customize the template to suit your specific needs.
Important Note:
Always test the webhook endpoint before deploying it in a production environment. For detailed instructions, refer to our documentation or explore our template library.
Github Action
- Setup GitHub Secrets: Store sensitive data such as
WEBHOOK_URLandWEBHOOK_KEYin your repository secrets. - Create a github action: Add the following YAML to a GitHub Actions workflow file, such as
.github/workflows/lamatic-index-flow.yml
Configuration
Input | Description | Required | Example |
webhook_url | The URL of the webhook to send data to | ✅ | |
webhook_key | The authorization key for the webhook, if there is any | ✅ | your_webhook_key |
github_ref | The GitHub reference (branch) to work with | ✅ | refs/heads/main |
file_type | The file extension to detect and send (e.g., mdx) | ✅ | mdx |
mode | The mode to operate in: full-refresh to send all files, or incremental to send only new/modified from the last commit. | ✅ | incremental or full-refresh |
verbose | Enable verbose output (true or false). Default - False | ❌ | True |
LowCode Config
- name: Send File Changes to Webhook
uses: Lamatic/Index-to-lamatic@v1.6 # Uses action
with:
webhook_url: ${{ secrets.WEBHOOK_URL }} # Replace with your secret
webhook_key: ${{ secrets.WEBHOOK_KEY }} # Replace with your secret
github_ref: ${{ github.ref }}
file_type: "mdx" # Adjust the file type as needed
mode: "incremental" # or "full-refresh"
verbose: "true" # or "false"Example Workflow Setup
name: Lamatic Index Flow
on:
push:
branches:
- main # Replace with your branch if necessary
paths:
- '**.mdx' # Adjust to only trigger for changes to specific file types
jobs:
send-changes:
runs-on: ubuntu-latest
steps:
- name: Send File Changes to Webhook
uses: Lamatic/Index-to-lamatic@v1.6 # Uses action
with:
webhook_url: ${{ secrets.WEBHOOK_URL }} # Replace with your secret
webhook_key: ${{ secrets.WEBHOOK_KEY }} # Replace with your secret
github_ref: ${{ github.ref }}
file_type: "mdx" # Adjust the file type as needed
mode: "incremental" # or "full-refresh"
verbose: "true" # or "false"Troubleshooting Common Issues
‣
‣