Custom GTM Tool

Placeholder for project-local GTM or RevOps tooling. Install a project plugin with concrete HTTP connector config before execution.

4 listed actions4 capability groups

Connection facts

What the Custom GTM Tool connector actually exposes.

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.

Connection method: Local StackOS service
Setup: No public vendor registration exists. Install a project-local plugin that declares endpoint, auth injection, allowlisted host, timeout, and response contract.
Capability groups: Enrichment, Lead Management, Outbound Operations, Pipeline Management
Action boundaries: 1 read action2 write actions1 cost-bearing action

Action catalog

Actions listed for Custom GTM Tool.

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.

Search Custom GTM Tool actions

4 matching actions

Outbound OperationsCan make changes

Add Sequence Through Custom GTM Tool

Contract for user-owned outbound tooling exposed through project-local static HTTP actions.

Pipeline ManagementReads data

Fetch Pipeline Through Custom GTM Tool

Contract for user-owned reporting tools exposed through project-local static HTTP actions.

Lead ManagementCan make changes

Import Leads Through Custom GTM Tool

Contract for user-owned GTM tooling. Project-local plugins should provide static HTTP connector config before execution.

EnrichmentUses a paid service

Run Enrichment Through Custom GTM Tool

Contract for user-owned enrichment tooling exposed through project-local static HTTP actions.

Direct answer

How does the Custom GTM Tool integration work?

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.

01Your requestStart in your AI
02StackOS planExpands the steps
03Custom GTM ToolDoes its bounded part
04Checked resultKeeps the proof

Common questions

Custom GTM Tool and StackOS.

What can the Custom GTM Tool integration do in StackOS?

The current catalog includes 4 Custom GTM Tool actions across Enrichment, Lead Management, Outbound Operations, Pipeline Management. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Custom GTM Tool?

No. Custom GTM 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.