Django Inngest
Missing Django integration for Inngest. This package depends on the Inngest Python SDK (pypi)
Installation
uv add inngest django-inngest
Configuration
Update urls.py to include:
from django.contrib import admin
from django.urls import path, include
from django_inngest.urls import inngest_urls
urlpatterns = [
# ...
path("admin", admin.site.urls),
# ...
]
# uses DJANGO_INNGEST_SERVE_PATH from settings.py
urlpatterns += inngest_urls
Update settings.py to include:
# required for inngest and production
INNGEST_EVENT_KEY = os.environ.get("INNGEST_EVENT_KEY", None)
INNGEST_SIGNING_KEY = os.environ.get("INNGEST_SIGNING_KEY", None)
# configuration
DJANGO_INNGEST_APP_ID = os.environ.get("DJANGO_INNGEST_APP_ID", "my-django-project")
DJANGO_INNGEST_IS_PRODUCTION = not DEBUG
DJANGO_INNGEST_CLIENT_LOGGER = os.environ.get(
"DJANGO_INNGEST_CLIENT_LOGGER", "gunicorn"
)
DJANGO_INNGEST_INACTIVE_FUNCTION_IDS = os.environ.get(
"DJANGO_INNGEST_INACTIVE_FUNCTION_IDS", []
)
DJANGO_INNGEST_AUTO_DISCOVER_FUNCTIONS = os.environ.get(
"DJANGO_INNGEST_AUTO_DISCOVER_FUNCTIONS", True
)
# no trailing slash or leading slash
DJANGO_INNGEST_SERVE_PATH = os.environ.get("DJANGO_INNGEST_SERVE_PATH", "api/inngest")
Usage
Create a new Django app and workflows file:
python manage.py startapp myapp
touch myapp/workflows.py
Update INSTALLED_APPS to include myapp.
In myapp/workflows.py, create a new Inngest function:
from datetime import timedelta
import inngest
from django_inngest.client import inngest_client
@inngest_client.create_function(
id="myapp/my-function",
trigger=inngest.TriggerEvent(name="my/trigger/event"),
rate_limit=inngest.RateLimit(
limit=1,
period=timedelta(minutes=2, seconds=30),
key="event.data.channel_id",
),
)
def my_function(ctx: inngest.Context):
print(ctx.event.data.get("channel_id"))
# your inngest function logic here
return "OK"
Then trigger anywhere in your Django project with:
import inngest
from django_inngest.client import inngest_client
event = inngest.Event(
name="my/trigger/event",
data={"channel_id": "1234567890"},
)
inngest_client.send(event)
Metadata
Release files for django-inngest 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_inngest-0.0.7.tar.gz | 6.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_inngest-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / django_inngest-0.0.7.tar.gz
| Download URL | django_inngest-0.0.7.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa7a13a3d2c744cdbb4b7abb5115ff04e6d153be3a680756cf6ca29bf68b50be
|
|
BLAKE2b-256 checksum How to use checksums |
5fc84f4b0939af0f0a25c02385059fda6a66828e2e247b472320465eaff83841
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2025.
Transparency logRelease files / django_inngest-0.0.7-py3-none-any.whl
| Download URL | django_inngest-0.0.7-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
404eff1cab0a3ac2c5aa2bda59130984314e3b2b7d4224bf6c848a0aee72a3fe
|
|
BLAKE2b-256 checksum How to use checksums |
51ef66e235a47e8bab677147919386fdc253b87b69caedfc29b5825a37efcd9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2025.
Transparency logSecurity for django-inngest 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_inngest-0.0.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.