Artifacts

Artifacts are persistent outputs created by agents or workflow steps. They keep a generated deliverable available after its originating run has finished and provide a review point before the result is shared or used elsewhere.

Availability

Artifacts are Orbit features unless an organization-specific entitlement enables them. An artifact belongs to the workspace in which its originating agent or workflow ran.

Browse artifacts

Open Artifacts to view saved output. You can:

• search by name;
• filter by category;
• filter by artifact type;
• sort by name, category, type, version, creation date, or update date; and
• open an artifact to inspect its content and metadata.

Use a recognizable name that describes the subject and period. Renaming changes the artifact label but does not change the agent or workflow configuration that created it.

Understand provenance and versions

Review the available source, run, category, type, and version information before using an artifact. Generated content can become stale when source data, evaluation criteria, or the originating configuration changes.

A revision or retry creates new run activity rather than silently changing the historical execution. Preserve the earlier version when the audit trail matters.

Review and edit supported outputs

Artifact capabilities vary by type. Keyword-plan artifacts can present editable keyword rows. When editing is offered, verify each changed row and save only content that still follows the artifact's intended schema.

For agent-generated artifacts, the detail view can provide:

• a revision action when the result is awaiting human review;
• a retry action after a failed run; and
• quality or retry guidance derived from the run state.

Correct the cause before retrying a failed artifact. Repeated retries will not resolve invalid scope, absent source data, or unavailable connections.

Export

Select Export CSV for artifact types that support structured CSV output. The export represents the artifact content available at that time. Review sensitive fields and confirm the intended recipient before sharing the file outside Marcenta.

Use artifacts in workflows

A Create Artifact workflow step can persist an output for later review. Subsequent workflow steps can reference an artifact where supported, including task creation, human approval, email delivery, and approved destination actions.

Use Human Approval before any action that applies an artifact to an external system. The artifact itself is not evidence that a person approved its contents.

Troubleshooting