What can the Mock Provider integration do in StackOS?

The current catalog includes 1 Mock Provider actions across Integration Testing. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Mock Provider?

No. Mock Provider remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.

Utilities plugin

Mock Provider

Local fake provider for end-to-end StackOS action execution tests without external API accounts.

1 supported actions1 capability groups

Supported work

What StackOS can do with Mock Provider.

The catalog reflects the actions currently available through the Utilities plugin. A workflow still decides which actions belong in the job and where approval is required.

Search Mock Provider actions

1 matching actions

Integration TestingReads data

Mock Provider Echo

Local executable action for validating StackOS auth, grants, redaction, audit, and failure handling without provider accounts.

Direct answer

How does the Mock Provider integration work?

People continue using Mock Provider as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

Mock Provider

What StackOS can do with Mock Provider.

Mock Provider Echo

How does the Mock Provider integration work?

Related integrations.

Alibaba Wan

BytePlus ModelArk

Firecrawl