Catalyst Signals

by catalystbyzoho9670b79d72feNo license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 weeks ago

Catalyst Signals — event-driven architecture platform for near-instantaneous communication between decoupled applications. Supports Zoho publishers, Catalyst publishers, custom publishers, webhooks, functions, circuits, event filtering, transformation, instant/batch dispatch, and retry policies. Trigger on 'Signals', 'event bus', 'publisher', 'event-driven', 'webhook target', 'dispatch policy', 'event transformation', 'rule filter', or 'event ordering'. Console-only service — no SDK or programmatic API.

Instructions onlyDevOps & Cloud
AI-generated overview

Guides configuration of Zoho Catalyst Signals, a console-only event-driven messaging service.

What it does
This skill explains how to set up Catalyst Signals, an event-driven architecture service that connects publishers to targets. It covers publishers (Zoho, Catalyst, Custom), JSON events and schemas, rules with filters and transformations, webhook/function/circuit targets, and Instant or Batch dispatch policies. It also documents event statuses, retry policies, ordering, logs, dashboard use, and deployment limits, with a reference file for deeper detail.
When to use it
Use it when working with Catalyst Signals concepts such as publishers, event buses, rules, event filters or transformations, webhook targets, dispatch policies, retry policies, or Signals deployment. It is also relevant when a user expects an SDK or REST API for Signals, since the service is console-only.
Requirements
Requires access to the Zoho Catalyst Console and one-time per-project activation of Signals; no SDK or programmatic API exists. It ships no scripts, only a reference document.

Prerequisites

Before using Signals, activate it once per project in the console:

Console → your project → Signals (left sidebar) → click "Start Exploring"

Skipping this step prevents access to Publishers, Webhooks, Rules, and Logs. This is a one-time activation per project.


How It Works

  1. Console-Only Service — HARD STOP if user expects SDK/API. Catalyst Signals is configured entirely through the Catalyst Console — there is NO SDK, REST API, or programmatic interface for creating publishers, rules, or webhooks. All setup is done via the console UI.

    • Publishers, events, webhooks, and rules are created in Console → Signals
    • Functions and Circuits are created separately in Console → Serverless, then selected as targets in Signals rules
    • The only code-level interaction is receiving events in target functions/circuits
  2. Understand the flow — Publisher → Event → Rule (with filters/transforms) → Target (Webhook/Function/Circuit)

  3. Load references/signals-basics.md — for publishers (Zoho/Catalyst/Custom), events, rules, targets, dispatch policies, event statuses, and deployment gotchas

  4. Key concepts:

    • Publishers emit events when actions occur (3 types: Zoho, Catalyst CloudScale, Custom)
    • Events are JSON payloads with auto-generated schemas (max 100KB for Zoho, 64KB for Custom)
    • Rules connect publishers to targets with optional filters and payload transformations
    • Targets receive events via Webhooks, Functions, or Circuits
    • Dispatch Policy controls event delivery: Instant (deliver immediately) or Batch (aggregate events — by count, size, interval, or schedule)
  5. Deployment warning — Rules are locked in production (enable/disable only). All rule changes must be made in Development and deployed. Max 25 publishers per deployment.

Security Checklist

  • Custom publisher REST API rate limit: 500 requests per minute. Exceeding this locks the API URL for 60 seconds.
  • Environment-specific REST API URLs: Custom event REST API URLs differ between Development and Production — update URLs when deploying.
  • Function/Circuit targets inherit their own permissions: If a function is the target, it runs with whatever scope it was configured with (user or admin). Signals does not override function-level permissions.
  • Event payload size limits: Zoho publishers max 100KB per event (5MB for multi-event batch). Custom publishers max 64KB per event (256KB for up to 25 events).

Triggers

Use this skill for: "Signals", "Catalyst event bus", "event-driven architecture", "publisher", "Zoho publisher", "Catalyst publisher", "custom publisher", "event schema", "rule", "event filter", "event transformation", "webhook target", "dispatch policy", "instant dispatch", "batch dispatch", "event ordering", "retry policy", "TTL", "event status", "Signals logs", "Signals dashboard", "deploy Signals", or "Signals console".

References

ReferenceLoad when the query is about…
references/signals-basics.mdPublishers (Zoho/Catalyst/Custom), events and schemas, custom event REST API, rules and filters, targets (webhooks/functions/circuits), dispatch policies (Instant/Batch), event transformation, retry policies, event ordering, event statuses, logs, dashboard, deployment limits, production restrictions

Source and attribution

Source:catalystbyzoho/claude-plugininskills/catalyst-signalsat commit9670b79

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal