skills.rest
Techlemariam
TechlemariamCOMMUNITY
Explore all skills by this author →
GitHub

remote-trigger

Trigger IronForge agent workflows remotely via GitHub repository_dispatch from HTTP clients.

Updated Aug 23, 2026
Search Tags:#automation#workflow#github#n8n#webhooks#moltbot#remote-trigger
One-click install
npx skills add https://github.com/Techlemariam/IronForge --skill remote-trigger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: remote-trigger
Source: https://github.com/Techlemariam/IronForge/tree/main/.agent/skills/remote-trigger
Command: npx skills add https://github.com/Techlemariam/IronForge --skill remote-trigger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remote workflow triggering enables IronForge to be controlled by external automation tools like n8n, Moltbot, Slack, or any HTTP client, eliminating manual intervention for workflow starts.

Core Features & Use Cases

  • Remote triggering via GitHub repository_dispatch, n8n, Moltbot, Slack, and HTTP clients
  • Secure authentication using REMOTE_TRIGGER_SECRET and GitHub PAT to validate requests
  • Use cases include autonomous nightly maintenance, system diagnostics, health checks, and deployment workflows

Quick Start

Trigger a workflow by sending a properly authenticated request to the configured endpoint with the desired workflow name.

Frequently Asked Questions about remote-trigger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger agent workflows from external automation tools like n8n or Slack?▼

You can trigger agent workflows from n8n, Slack, or any HTTP client by sending an authenticated request that executes a GitHub repository_dispatch event. This allows external systems to securely start workflows without manual intervention.

What credentials are needed to securely trigger remote workflows via HTTP?▼

Securely triggering remote workflows requires a REMOTE_TRIGGER_SECRET to validate incoming HTTP requests and a GITHUB_PAT with repository scope to execute the repository_dispatch event. Both credentials must be configured before sending triggers.

Does remote workflow triggering work for autonomous nightly maintenance and health checks?▼

Yes, remote workflow triggering is designed for autonomous nightly maintenance, system diagnostics, health checks, and deployment workflows. External automation tools can schedule and initiate these tasks directly via authenticated HTTP requests.

How do I configure n8n and Moltbot to send remote triggers to GitHub?▼

You configure n8n and Moltbot using provided integration artifacts like n8n-workflow.json and moltbot-config.md. These files define the HTTP requests and authentication needed to execute repository_dispatch events via the GitHub API.

Can I use any HTTP client to send a repository_dispatch event for workflow automation?▼

Yes, any HTTP client can be used to send a repository_dispatch event for workflow automation, provided the request includes the correct REMOTE_TRIGGER_SECRET and targets the configured endpoint with the desired workflow name.

What are the limitations of using GitHub repository_dispatch for remote triggers?▼

Using GitHub repository_dispatch for remote triggers requires valid GITHUB_PAT credentials with repository scope and a configured REMOTE_TRIGGER_SECRET. Requests fail if authentication is missing or if the integration artifacts are improperly configured.

Related Skills

Explore More Software Engineering Skills→
AbdullahmohammadarefAbdullahmohammadaref

MCP Integration

test1

Community
Advanced
starlink-awakenstarlink-awaken

skillpack-check

Aggregate gbrain doctor checks and migration statuses into JSON reports.

Community
Intermediate
joabeoliveirajoabeoliveira

n8n Integration & Webhooks

Trigger n8n workflows via webhooks and manage them through API calls.

Community
Intermediate
WilkoMarketingWilkoMarketing
92

n8n-workflow-patterns

Apply proven n8n workflow patterns for webhooks, APIs, databases, and scheduled tasks.

Community
Advanced