Skip to content

docs(services): add Inngest service documentation#647

Open
rohittiwari-dev wants to merge 7 commits into
coollabsio:nextfrom
rohittiwari-dev:v4.x
Open

docs(services): add Inngest service documentation#647
rohittiwari-dev wants to merge 7 commits into
coollabsio:nextfrom
rohittiwari-dev:v4.x

Conversation

@rohittiwari-dev

Copy link
Copy Markdown

Summary

Adds documentation for Inngest as a one-click service in Coolify.

This Documentation Pr is Raised on behalf of Service PR (coollabsio/coolify#10612)

Inngest is an open-source durable workflow engine for building reliable background jobs, queues, and event-driven systems. It provides step functions, automatic retries, scheduling, and fan-out — all without managing infrastructure like queues or workers.

Changes

  • New file: content/docs/services/inngest.mdx — Service documentation page with description, logo, and external links
  • New file: public/images/services/inngest-logo.svg — Inngest logo icon (SVG)
  • Modified: content/docs/services/all.mdx — Auto-generated; Inngest added under Automation category
  • Modified: src/generated/services.json — Auto-generated; Inngest entry added to the service list data

Category

Automation — alongside ActivePieces, Evolution API, Mage AI, N8N, and Trigger.dev

Checklist

  • Service .mdx file created with proper frontmatter (title, description, og.description, category, icon)
  • Logo SVG added to public/images/services/
  • bun run generate:services executed to regenerate all.mdx and services.json
  • Service appears in the overview page (<ServicesList /> component)
  • Service appears in the all services directory page
  • External links include utm_source=coolify.io tracking

@github-actions github-actions Bot added the ⏳ Waiting for PR merge on Core Repo This PR should be merged only after the linked PR in the core repo is merged. label Jun 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

⏳ Waiting for PR merge on Core Repo This PR should be merged only after the linked PR in the core repo is merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants