Hatchet

Runs Payload jobs on Hatchet, with Payload's own runner executing each job

Community 3 33/wk Apache-2.0 v0.1.0

Installation

pnpm add @abinnovision/payloadcms-hatchet

About

Hatchet hands Payload's queued jobs to Hatchet, which decides when each job starts and on which worker. Payload stays the system of record and still executes every job with its own retries, backoff and task logs. Jobs queued with a future wait time become scheduled runs in Hatchet, and each job appears as a run in the Hatchet dashboard.

Jobs are pushed to workers instead of being polled. The worker can run as a separate long-running process or inside the Next.js server. A periodic maintenance task recovers jobs left stuck by a crashed worker or a failed dispatch. It suits teams that want durable scheduling and visibility on top of Payload's job queue, and it requires a Hatchet account or self-hosted Hatchet instance.

Package info

Package name
@abinnovision/payloadcms-hatchet
Latest version
0.1.0
Unpacked size
54 kB
License
Apache-2.0
Weekly downloads
33
Last publish
Oct 16, 2026

More from abinnovision

View profile

Runs AI agents in the Payload admin that read and write content through access-controlled tools

Editor-authored URL routing that maps collections to path patterns and links

Typed block registry and React Server Component renderer for Payload blocks

Shows the build version, commit and environment in the admin sidebar

Idempotent seed runner that fills a Payload database with ordered, cross-referenced content

Similar plugins

More in Workflow

Adds order states, status history, internal notes and tracking to orders

Reservation and booking management with conflict detection and a calendar view

Stores DNA reference panels and reviewed sample results in Payload collections

Tracks lab sample kits from stock to keeper and back, with a custody trail

Lets guardians suggest or approve changes to a minor's records and requests

Supplier lists and purchase orders that draft reorders from your stock levels