Zekt Chainlink
Normally a repository is either a provider or a consumer. Chainlink lets one repository be both: it receives events from upstream services and sends its own events downstream. That way, events can chain across repositories: A → B → C, across organizations if needed.
Requirements
Section titled “Requirements”Your account needs the Both persona. Otherwise the Chainlink sidebar item is hidden, and enabling gives Chainlink requires a dual-role (both provider and consumer) account.
Enable a repository
Section titled “Enable a repository”- Go to Chainlink → Repos and choose Enable on the repository.
- Only one side (provider or consumer) needs to exist already. Zekt creates the other side automatically, with no second GitHub App installation.
The Chainlink section has three tabs: Overview, Repos, and Topology, a graph of your chains that marks whether each hop changed the payload.
How a chain works
Section titled “How a chain works”Zekt never changes a payload in transit. Each repository in the chain runs its own workflow:
- To pass an event on, the middle repository’s workflow sends a new event with the Zekt Action.
- To enrich or reduce the data, that workflow builds the new payload itself.
- To hold an event for approval, use GitHub environment protection rules in that workflow.
- Redaction Guard scans every outgoing provider payload, so it also covers what a relay repository sends.
Hop limit
Section titled “Hop limit”Set a hop limit per repository, from 2 to 10, in the Repos tab. An event that would go beyond the limit isn’t forwarded, and shows as Not sent in the dispatch queue.
Disable Chainlink
Section titled “Disable Chainlink”When you disable Chainlink on a repository, you choose which role to keep. Keeping only the consumer role is refused while the repository’s services still have active subscribers.
A flat monthly fee per Chainlink repository, instead of the normal per-repository fee. Analytics or Shield on a Chainlink repository is charged once, not per side. See zekt.dev/zekt-pricing.