Add Sequence Through Custom GTM Tool
Contract for user-owned outbound tooling exposed through project-local static HTTP actions.
Placeholder for project-local GTM or RevOps tooling. Install a project plugin with concrete HTTP connector config before execution.
Supported work
The catalog reflects the actions currently available through the GTM And RevOps plugin. A workflow still decides which actions belong in the job and where approval is required.
4 matching actions
Contract for user-owned outbound tooling exposed through project-local static HTTP actions.
Contract for user-owned reporting tools exposed through project-local static HTTP actions.
Contract for user-owned GTM tooling. Project-local plugins should provide static HTTP connector config before execution.
Contract for user-owned enrichment tooling exposed through project-local static HTTP actions.
Direct answer
People continue using Custom GTM 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.