Skip to main content
Use the @bijection/connectors/trigger entrypoint to declare Trigger tasks resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
Task

​
observed: observed

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

​
Configuration: standard

Case: trigger/task/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: http. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

trigger.task.observed({ contract, release, access, governingRules }) composes native HTTP acquisition, private credentials and governed external calls. Import the application contract/release produced by bijection trigger generate; configure an imports entry with adapter: "trigger.contract", source.file and options.release in bijection.json for normal dev/deploy preparation. The source may be the portable JSON contract or a TypeScript module whose default export is defineContract(&#123; name, taskId, identity, args, returns, progress, waitpoints &#125;) from @bijection/connectors/trigger/contract; integer() declares a JSON integer. Unsupported validators are refused at the authored field. Bind an HTTPS stateless bridge endpoint, exact project_ref and environment, and trigger.credential(name). The bridge is bijection trigger serve in the Bijection CLI; it calls Trigger over TLS, runs no customer tasks and retains no journal. Binding identification checks the captured concrete deployment, version, content hash, task inventory and authenticated project/environment. A task inventory is not behavioral qualification. Capture rollouts with --retain-release to keep explicit prior deployments of the same contract/environment in the new manifest. New starts pin the current version; existing executions and approvals retain their original deployment, token and review identity. Preserve old endpoints for retained calls already accepted against their previous binding. A contract change requires a separate resource. Install runs through defineSyncedTable({ source }). Start through ctx.calls.add with the generated collection command. Start arguments are the task input’s named fields, optional fields included. Record commands require an acquired local execution row. Each decide<Waitpoint> member (decideShipment for waitpoint shipment) takes { review_hash, actor_id, value }; requestCancellation takes no arguments. Governing rules remain mandatory and browser callers cannot supply provider target keys or credentials. Starts use single-attempt delivery. An unknown start is discovered and verified without reissuing it; Trigger keys can expire or be released after failure. Decisions address the exact run and token, and confirm only by comparing the actual winning output with the retained envelope. A successful completion response alone is insufficient. Reconciliation never completes a token again. Cancellation confirms the provider run state without compensating external work. Customer tasks import the generated helper, which uses @bijection/connectors/trigger/worker. Trigger SDK 4.7.5 or later within major version 4 is a peer dependency for that entry point. The wrapper validates input, project/environment/version and contract before customer code, refuses manual replay, publishes bounded progress and provides declared waitpoints. Gates recover across attempts without renewing deadlines. It records task acknowledgement separately from Trigger recording and business completion. External business effects still need customer-owned idempotency or conditional writes. trigger.observations.select orders one run’s rows by attempt and sequence, refuses equal-position disagreements and conflicting outcomes, and prefers a terminal or completed-gate observation at the newest position. trigger.observations.approval(row, gate, now) reports whether that waitpoint still accepts a decision. Only bounded inline JSON is supported. Distinct execution observations have content-addressed source keys and explicit attempt/sequence positions. Lists establish neither deletion nor complete history. Callback URLs and public completion tokens are not published. Source and portable tests are separate from hosted qualification; provider-specific native histories remain unqualified.

​
Application helpers

All workflow adapters share one application vocabulary. Object-typed inputs are named command arguments, optional fields included: adding an optional field never wraps or renames existing arguments. Other values travel as input. Bijection-owned members are camelCase (start, requestCancellation); names a contract declares keep their spelling. Serialized routes, capability keys and records keep their snake_case wire names. <adapter>.commands(contract) returns each command’s target and argument validators for commandPolicy from bijection/server, so a policy module types its inputs without importing the schema that installs the resource. <adapter>.policies(contract, "permissions", { reads }) references one exported policy per command name (permissions:decideShipment, …). Names follow the contract; a missing export fails deployment analysis. <adapter>.observations.select(rows, { bound }) interprets acquired execution rows the application read through its own indexed queries. It returns current, missing, conflict (with its reason) or exceeded; it never invents ordering or infers deletion from absence. The application still decides business association, actor permission and acceptable freshness. <adapter>.trace(...) resolves a retained call’s interaction from the generated capabilities and composes it with an authorized observation.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.