Imbi Workflows
The workflow engine (ADR 0021). It claims queued and running workflow runs
from the workflow_runtime Postgres schema, runs one step per claim, records
the result, and releases the run. imbi-api owns the schema, starts runs, and
cancels them; the engine has no public API, only /status.
Deploy, rollback, and email steps call imbi-api as the imbi-workflows
service account. The bounds of ADR 0017 apply to deployments: the account
needs integration:act-as-service, membership in the workflow's
organization, and a target environment with allow_autonomous. imbi-api
sends email, to users and teams of the organization only.
The engine also reconciles trigger bindings. When a workflow activates,
pauses, or is deleted, imbi-api writes the desired bindings to
workflows.trigger_bindings and notifies. The engine then makes the
scheduler task of each schedule trigger (as the imbi-workflows account)
and the gateway-actions#start_workflow rule of each webhook trigger, and
records each binding as synced or failed. It also does this on a
schedule, so a failed call is tried again.
Settings
| Variable | Purpose | Default |
|---|---|---|
IMBI_INTERNAL_API_URL |
In-cluster origin of imbi-api | http://localhost:8000 |
IMBI_API_URL |
imbi-api's public URL, whose path is its route prefix | |
IMBI_WORKFLOWS_SA_CLIENT_ID |
Client id of the imbi-workflows service account |
|
IMBI_WORKFLOWS_SA_CLIENT_SECRET |
Client secret of that account | |
IMBI_WORKFLOWS_WORKERS |
Runs one process works on at the same time | 10 |
IMBI_WORKFLOWS_POLL_INTERVAL |
Upper bound in seconds on the sleep between polls | 10 |
IMBI_WORKFLOWS_SCHEDULER_URL |
imbi-scheduler's task API, with its route prefix | http://localhost:8005/api |
IMBI_WORKFLOWS_RECONCILE_INTERVAL |
Seconds between passes of the trigger reconciler | 300 |
Postgres and the graph use the shared settings of imbi-common.
Developer Quickstart
moon run root:setup
moon run root:services
uv run --env-file .env.test pytest apps/workflows/tests
Metadata
Release files for imbi-workflows 2.39.1
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 | |
|---|---|---|---|---|
| imbi_workflows-2.39.1.tar.gz | 34.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imbi_workflows-2.39.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.1 kB
Release files / imbi_workflows-2.39.1.tar.gz
| Download URL | imbi_workflows-2.39.1.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f83d1b05d7fb1c152bdda58ec3978aaf53586fee588678c6815b086a7dd4c701
|
|
BLAKE2b-256 checksum How to use checksums |
200d715145b78a96b977c0031fe06d99628919bf7062eb69ef828a2b696b3b9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 22, 2026.
Transparency logRelease files / imbi_workflows-2.39.1-py3-none-any.whl
| Download URL | imbi_workflows-2.39.1-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79e06b57c173b99b2df37670b2367e940f29af2b7b0439cbdff33755dbdafdbd
|
|
BLAKE2b-256 checksum How to use checksums |
e2273055d9c1b35c0793c9da15fc124b4a40c14e373fc12a78cecdc52051a882
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 22, 2026.
Transparency logSecurity for imbi-workflows 2.39.1
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 imbi_workflows-2.39.1.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 Oct 22, 2026.
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.
