Create Media Campaign Through Custom Media Tool
Contract for user-owned campaign tooling. Project-local plugins should provide static HTTP connector config before execution.
Placeholder for project-local paid media tooling. Install a project plugin with concrete HTTP connector config before execution.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
4 matching actions
Contract for user-owned campaign tooling. Project-local plugins should provide static HTTP connector config before execution.
Contract for user-owned reporting tools exposed through project-local static HTTP actions.
Contract for user-owned budget tooling exposed through project-local static HTTP actions.
Contract for user-owned campaign tooling. Project-local plugins should provide static HTTP connector config before execution.
Direct answer
People continue using Custom Media Tool 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.
Common questions
The current catalog includes 4 Custom Media Tool actions across Campaign Management, Media Measurement. The exact actions used depend on the workflow and approval rules.
No. Custom Media Tool 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.