Skip to main content
A trigger binding connects an external event to an agent run. When a matching event arrives, the platform starts a run of the bound agent.

​
Bindings

A binding names the agent to run, the provider the event comes from, the trigger type, and the source that identifies which events match. For GitHub, you describe the source in parts and the platform assembles it:
Omitting --repo makes the binding org-wide. For other systems, use --provider generic_webhook and set --trigger-source directly.

​
Signing

Webhook deliveries are verified with an HMAC secret. You either create one when the binding is created, or point at a credential you already hold: jstm triggers test sends a test delivery signed by the server using the real secret. The secret never leaves the backend, so the test exercises the true signature path rather than a mock.

​
Input mapping

An incoming payload rarely matches an agent’s declared inputs. --input-mapping bridges them:

​
Environment override

By default a triggered run uses the agent’s current stage. An override pins it:
This is how you exercise a live webhook end to end while nothing takes effect — useful while confirming the mapping is right.

​
Events

Every delivery is recorded, whether or not it produced a run.
This is the first place to look when a webhook fired but nothing happened. The event record distinguishes “never arrived” from “arrived and was rejected” from “arrived and started a run that failed” — three very different problems.

​
Enabling and disabling

Disabling preserves the binding, its secret, and its event history:
Prefer this to deleting when the pause is temporary.

​
See also