A recipe is a Mix task that adds a common workflow to one of your resources, such as an approval or an expiry. Run mix ash_workflow.gen.<recipe> with the resource to attach it to, and the task writes the workflow resource, its relationship to your resource, and the actions it needs.

The generated code belongs to your application. Edit it like any other code you wrote: rename steps, change deadlines, and fill in the policy checks. AshWorkflow does not regenerate the code or keep it in step with later versions of the recipe.

Catalogue

A recipe without a link has not been released yet. Each row links to its page once the recipe is available.

RecipeStepsExample uses
gen.approvalpending → approved | rejected | cancelled, optional overdueExpenses, leave requests, purchase orders
gen.expiryactive → expiring → expired, with renewContracts, certifications, licences
gen.reviewin_review → changes_requested → in_review → approvedContent, design review, sign-off
gen.publicationdraft → scheduled → published → unpublishedPosts, announcements, listings
gen.invitationsent → accepted | declined | expired | revoked, with resendTeam invites, RSVPs, access grants
gen.acknowledgementpending → acknowledged | overduePolicy attestations, terms updates
gen.dormancyactive → dormant → archivedAccounts, projects, leads
gen.deletionrequested → purging → deleted, with restoreAccount closure, GDPR erasure
gen.syncsyncing → synced | failed, with resyncCRM push, payment provider, search index
gen.verificationsubmitted → verifying → verified | rejectedIdentity documents, registrations