PluginTriggersManifest
Defined in: plugin.ts:89
Declares a plugin as a trigger source. module points to a JS/TS file
exporting verify(rawBody, headers, secret) and
normalize(payload, headers) (see TriggerSourceModule), plus an optional
respond(result, event, connection) invoked when a trigger-spawned session
reaches a terminal state. The ingress route resolves these via the
TriggerSourceRegistry — no core change per provider.
Properties
Section titled “Properties”events?
Section titled “events?”
optionalevents?:PluginTriggerEvent[]
Defined in: plugin.ts:93
Catalog of events this source can emit, for the automation editor.
module
Section titled “module”module:
string
Defined in: plugin.ts:91
Path (relative to plugin root) to the module exporting verify/normalize (+ optional respond).
requiredSettings?
Section titled “requiredSettings?”
optionalrequiredSettings?:string[]
Defined in: plugin.ts:110
Settings keys (from the plugin’s settings.schema) that must be non-empty
for the provider to be considered “connected”. When omitted, every
password-type setting is treated as required. Drives the automation
editor’s Connect vs Connected status.
setupInstructions?
Section titled “setupInstructions?”
optionalsetupInstructions?:string
Defined in: plugin.ts:103
Markdown checklist of the provider-side setup steps (e.g. Slack: enable
Event Subscriptions, paste the Request URL, subscribe to bot events,
install to the workspace). Rendered as a platform-generated instructions
onboarding step between the auto-generated copy-URL and await-event steps —
authors supply only this text and get the full trigger checklist for free.
setupSkill?
Section titled “setupSkill?”
optionalsetupSkill?:string
Defined in: plugin.ts:95
Optional skill id that walks the user through connecting the provider.