iii-multi-trigger

Handle HTTP requests, queue messages, and cron schedules in one function.

Updated Aug 23, 2026

Search Tags:#routing #event-driven #queue #http #cron #multi-trigger

Ready to run

npx skills add https://github.com/iii-hq/skills --skill iii-multi-trigger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iii-multi-trigger
Source: https://github.com/iii-hq/skills/tree/main/iii-multi-trigger
Command: npx skills add https://github.com/iii-hq/skills --skill iii-multi-trigger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows a single function to be triggered by multiple event sources like HTTP requests, queue messages, and cron schedules, simplifying complex event-driven architectures.

Core Features & Use Cases

Unified Logic: Write your core business logic once and have it respond to various event types.
Conditional Execution: Use ctx.match() to route events based on their type and apply specific handling.
Use Case: An order processing function can accept new orders via an HTTP API, process incoming messages from a queue for order updates, and run a daily batch job to reconcile orders, all within the same code.

Quick Start

Use the iii-multi-trigger skill to create a function that handles both HTTP requests and queue messages.

Frequently Asked Questions about iii-multi-trigger

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

FAQPage Schema

How do I handle HTTP requests, queue messages, and cron schedules in a single function?▼

Handle multiple triggers in one function by using conditional execution and `ctx.match()` to route events. This unified code structure processes HTTP requests, queue messages, and cron schedules, applying specific response handling for each trigger type.

What is the best way to route event-driven logic based on the trigger source?▼

Route event-driven logic by calling `ctx.match()` within your handler. This method identifies the event source, enabling conditional execution so a single function can apply trigger-specific response handling for HTTP, queue, or cron events.

Can I process incoming queue messages and HTTP API requests using the same business logic?▼

Yes, you can process queue messages and HTTP API requests using the same business logic. The multi-trigger approach allows a single function to accept various event types, simplifying complex event-driven architectures with unified logic.

How does conditional execution work for multiple event types in an event-driven architecture?▼

Conditional execution for multiple event types works by evaluating the trigger source via `ctx.match()`. This routing logic facilitates flexible event-driven applications, allowing the unified function to branch into trigger-specific response handling for HTTP, queue, or cron inputs.

When do I need a multi-trigger function for event routing?▼

You need a multi-trigger function when a single business process must respond to various event types. For example, an order processing function can accept HTTP orders, process queue updates, and run daily cron reconciliation within one unified code structure.

Does using one function for multiple triggers limit response handling for specific event sources?▼

No, using one function for multiple triggers does not limit response handling. It facilitates trigger-specific response handling within a unified code structure, allowing you to apply distinct logic and outputs for HTTP, queue, or cron events using routing logic.