All
id fields across every entity are UUIDs (version 4). When referencing a resource in the API or in webhook payloads, always use the full UUID string — human-readable slugs and names are for display purposes only and may change.Organization
An organization is the top-level container for everything your company owns in mFoundry. It holds your member roster, billing details, and organization-wide settings. Each organization has a globally unique slug used in dashboard URLs and certain API routes.The unique UUID that permanently identifies this organization. Use this field when referencing the organization in API requests and webhook payloads.
The human-readable display name of the organization, shown in the dashboard header and on invoices.
A URL-safe, globally unique identifier for the organization (e.g.
acme-corp). The slug appears in dashboard URLs and can be updated by an Owner in Settings → General.The UTC timestamp at which the organization was created. This field is read-only and set by the server.
Project
A project belongs to exactly one organization and serves as the primary workspace for a product, initiative, or client engagement. Projects group workflows together and define which team members have access to those workflows through role assignments. Use the/projects endpoints to create, retrieve, update, and delete projects programmatically.
An optional plain-text description that helps team members understand the project’s purpose and scope.
The current lifecycle state of the project. Accepted values are
active, paused, and archived.The UUID of the organization this project belongs to. Used in API routes and for access-control evaluation.
The UTC timestamp at which the project was created. Set by the server and read-only.
The UTC timestamp of the most recent change to the project’s metadata. Automatically updated on every write operation.
Workflow
A workflow is an ordered sequence of steps that lives inside a project. Each workflow is independently versioned, meaning you can edit and test changes without affecting live executions. When a workflow is triggered — either manually, on a schedule, or by an incoming webhook — mFoundry creates a workflow run and spawns individual task records for each step.The display name of the workflow, visible in the project dashboard and in API responses.
The UUID of the project this workflow belongs to. Determines which members can view and edit the workflow based on project-level roles.
An ordered array of step objects that define the workflow’s logic. Each step specifies an action type, configuration, and any conditional branching rules.
The UTC timestamp at which the workflow was created. Set by the server and read-only.
Task
A task is the runtime record of a single step executing within a workflow run. When a workflow is triggered, mFoundry automatically creates one task per step and tracks its progress in real time. Tasks are read-only after creation — you can inspect their status and logs, retry failed tasks, or cancel pending ones from the dashboard or via the API.The current execution state of the task. Accepted values are
pending, running, succeeded, and failed.The name of the workflow step this task corresponds to, as defined in the workflow configuration.
The JSON output produced by the step upon successful completion. Present only when
status is succeeded.A human-readable error message describing why the task failed. Present only when
status is failed.The UTC timestamp of the most recent status change. Automatically updated as the task progresses.
User
A user represents a human or service account that has been granted membership to one or more organizations. Users authenticate via email and password or SSO, and interact with mFoundry through the dashboard or the API using personal access tokens. Use the/users endpoints to list and retrieve user records.
The unique UUID that identifies this user across all organizations. Immutable after account creation.
The user’s verified email address, used for authentication, notifications, and as the primary contact identifier.
The user’s role within a given organization or project context. Accepted values are
owner, admin, member, and viewer. See Key Features → Team Collaboration for a full permissions breakdown.The UTC timestamp at which the user account was created. Set by the server and read-only.
Webhook
A webhook is an outbound HTTP endpoint registration that tells mFoundry where to deliver event notifications for a given project. Once registered, mFoundry sends a signed JSON payload to your target URL whenever a configured event occurs — such as a workflow completing or a task failing. Use the/webhooks endpoints to create, list, and delete webhook registrations.
The unique UUID that identifies this webhook registration. Use this value when deleting a webhook via
DELETE /webhooks/:id.The UUID of the project this webhook is scoped to. Events from other projects will not be delivered to this endpoint.
The list of event types that trigger a delivery to this webhook. Example values include
workflow.completed, workflow.failed, and task.failed.An optional shared secret used to sign each delivery with an HMAC-SHA256 signature. Verify the
X-mFoundry-Signature header in your receiver to confirm authenticity.