Webhooks
Webhook delivery stays visible, signed, and retry-aware.
SignalForge treats webhooks as a first-class workflow surface instead of a hidden side effect. Deliveries are recorded, retryable, and testable from the same product model as the API.
Events
- content.received
- variants.generated
- post.scheduled
Signature model
Each project webhook carries its own signing secret. The receiver should verify the signature before accepting the payload as valid SignalForge traffic.
Delivery operations
Webhook deliveries have history, retry scheduling, and test-send support. That keeps downstream sync issues visible instead of requiring log spelunking.