Create Outbrain Campaign
Create an Outbrain campaign from an explicit marketer-scoped campaign object.
Outbrain Amplify provider contract. OB-TOKEN-V1 generation, storage, expiry checks, and rotation stay daemon-side.
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.
9 matching actions
Create an Outbrain campaign from an explicit marketer-scoped campaign object.
Create an Outbrain promoted link from explicit destination, asset, and campaign refs.
Fetch a bounded Outbrain performance snapshot for an agent-selected scope.
Read Outbrain marketer metadata available to the configured credential.
Pause an Outbrain campaign by safe campaign reference.
Resume an Outbrain campaign by safe campaign reference.
Update an Outbrain budget from explicit marketer, campaign, or budget refs.
Update an Outbrain campaign from an explicit change object.
Update an Outbrain promoted link from an explicit change object.
Direct answer
People continue using Outbrain 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 9 Outbrain actions across Campaign Management, Creative Operations, Media Measurement. The exact actions used depend on the workflow and approval rules.
No. Outbrain 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.