Code your
GTM motion.
Automate
the work
Code and automate your GTM motion with the CLI, standalone scripts, or a code node. For agentic AI and GTM engineers who want to code their GTM workflows.
$ Programmatic GTM turns RevSure's governed context and actions into building blocks for code. Code a motion directly with the CLI, write it as a standalone script, or run that script inside an Agent Hub code node. The output of one tool becomes structured input to the next, so you can automate GTM work wherever your team does.
Code your GTM motion. Run it your way
Use the CLI directly, write the motion as a script, or run that script inside an Agent Hub code node.
RevSure CLI
Access RevSure through a CLI that users and agents can invoke directly.
Scripts
Code your GTM motion into a script, transform JSON results, and automate the work wherever it needs to run.
Agent Hub code node
Run that script inside one code node instead of using Agent Builder to wire each input, output, and writeback step by hand.
Code your GTM motion in commands
The CLI is a direct programmatic surface for the GTM motion you want to run. A human or an agent can invoke commands against live context and use the structured result in the next step.
Add the CLI
npm install -g @revsure/cliUse it locally, in scripts, or in the environment where your workflow runs.
Define the motion
revsure tools
revsure describe pipeline-health-overviewUse the available commands and inputs to express the GTM work you want to run.
Execute the motion
revsure pipeline-health-overview --quarters q0Run it directly from the CLI and use the JSON result in the next step of the motion.
One command becomes part of a complete program
Each RevSure command returns structured context. Your code can evaluate it, add your business logic, and route the result into the next approved step.
Pull the GTM view your workflow needs.
Filter, score, enrich, or combine the result in code.
Send an approved result to the next tool or system.
Write it once. Run it wherever your work runs
A script can run as a program or background job. Deploy it in the environment your team already trusts, then let it run when the work is due.
Scheduled checks
Run a recurring program that checks pipeline health, account activity, or data quality without a manual handoff.
Event-driven work
Start a workflow when the signal arrives, so the next approved step happens while the context is fresh.
Production services
Package code into an internal service, container, serverless function, or CI job without changing its GTM logic.
Visible outcomes
Send the resulting report, task, or approved action to the system where the team will use it.
When code is the workflow, one node should be enough
Put the same Programmatic GTM script inside a dedicated Agent Hub code node, run it independently, and avoid assembling every input, output, and writeback step by hand.
Your complete GTM motion, written as one script.
Keep the logic in code.
Run the script independently inside Agent Hub instead of recreating its logic across a chain of individual nodes.
- Reads the context the motion needs
- Runs your script and decision logic
- Writes only through approved actions
Programmatic GTM does not bypass governance
Read context freely. Make a change only when the workflow declares its intent—whether it runs once in a terminal or continuously in production.
Structured output
Every tool returns JSON your command, script, or deployed workflow can inspect, transform, and pass forward.
Explicit write control
Read context freely. Changes require an explicit write intent, so a report cannot accidentally become an action.
Consistent controls
The same context, permissions, and action guardrails apply whether code runs once locally or continuously in production.
The governed layer behind every workflow
Turn GTM logic into running software
See how your team can build, deploy, and govern Programmatic GTM workflows on the stack you already run.