writing-workspace-signals

To configure a Friday workspace signal, you need valid provider configurations, payload schemas, and runtime wiring in your workspace.yml file. This ensures correct job trigger bindings and prevents common runtime errors like missing schemas or invalid cron expressions.

Setting up cron schedules and timezone settings requires defining the schedule provider in your workspace configuration. You must use valid cron expressions and specify timezone policies to avoid dead signals and ensure jobs trigger at the correct times.

HTTP webhook signals cause path collisions when multiple endpoints share the same route. You must ensure path uniqueness across all HTTP signals and include the required JSON schema so the runtime can validate payload types and dispatch correctly.

Yes, Friday workspace signals support Slack, Telegram, WhatsApp, Discord, and Teams providers. You can configure each provider with the correct enum values and payload schemas to enable automated dispatch through these messaging platforms.

To prevent dead signals and payload type mismatches, wire your signals to the appropriate job triggers and define strict JSON schemas for expected inputs. This validates parameters before dispatch and ensures the automation workflow receives the correct data.

The best way to add a JSON schema for an HTTP signal is to define the expected parameters, such as message_id and instructions, directly in the workspace configuration. This allows the runtime to render input fields correctly and validate payload types before dispatch.