PacketAgentDocs

Configure triggers, permissions, and approvals#

A deployment combines a trigger with a compiled tool policy. Configure both before exposing an event source: a Worker that starts correctly but has broader tools than expected is not ready for production.

Before you start#

  • Complete First Worker.
  • List each external system the Worker must read or change.
  • Decide which actions require a person to approve them.
  • Prepare test endpoints and credentials that cannot affect production data.

Choose a trigger#

Trigger Use
Manual Operator starts a run from the workbench or API.
Cron Scheduler starts runs from a five-field cron expression.
Webhook An external caller presents the Worker webhook credential.
Alert Alert evaluation starts a run when configured conditions fire.
Queue Declaration support exists, but a complete external ingress path must be verified before use.

Start with manual delivery. Add one automated trigger at a time and verify that one source event creates one run.

Restrict tools#

Grant only the effect and resource pattern the Worker needs. Separate read and write capabilities, use exact HTTPS origins for outbound calls, and keep sandbox network access denied unless an origin has been reviewed.

After changing a permission, create and activate a new deployment. The runtime uses the compiled deployment policy rather than an editable draft.

Require approval#

Use approval for destructive, external, high-cost, or broadly scoped actions. The run pauses at an attention request until an operator approves, approves for the remainder of that run, rejects, or lets the request expire.

Review the resolved destination and arguments, not only the tool name. Reject requests whose scope differs from the Worker’s purpose.

Verify#

  1. Send one event with a unique identifier.
  2. Confirm exactly one run appears.
  3. Confirm an allowed read tool succeeds.
  4. Confirm an undeclared or out-of-scope tool is denied.
  5. Trigger an approval-gated test action and reject it.
  6. Repeat and approve it against the test endpoint only.
  7. Replay the same source event and confirm deduplication behaviour matches the trigger contract.

If it does not work#

Symptom Check
Cron never fires Confirm the schedule is active and one scheduler leader is running.
Webhook is refused Rotate or re-copy the credential and use the documented header.
Event creates duplicate runs Confirm the source event supplies a stable deduplication identifier.
Allowed tool is denied Activate a deployment that contains the updated compiled grant.
Approval never resolves Check the request deadline, run status, and operator decision record.