For GTM engineers who outgrew n8n

Your workflow outgrew the canvas.

Move it to TypeScript. Rotor retries failed steps, keeps state, and shows exactly what ran.

Move one workflowSee how it runs

$9 to start. 30-day money back. No sales call.

Run recorder
run_8f2a

account-outreach

Enrich, draft, and approve

Recovered
  1. Fetch 312 leadsHubSpot
  2. Enrich company dataClay returned 429
  3. Resume at enrichAttempt 2 of 3
  4. Draft queued for approvalJordan at Acme
Reached approval without a manual rerun5m 12s total

01Outgrowing the canvas

The canvas was fast. Then the workflow became important.

You do not need another visual builder. You need a clean way to own the logic already running your pipeline.

01

The flow became code anyway.

Function nodes hold the logic. The canvas only hides it.

02

Every extra task changes the bill.

A busy month should not turn into a pricing surprise.

03

Nobody wants to own the next edit.

There is no useful diff, review, or clean handoff.

02Move the logic

Your logic belongs in code.

Use the editor, version control, and review flow your team already knows.

Rotor runs the workflow and stores each completed step.

workflows/account-outreach.tsready to deploy
import { createFunction } from '@rotorsh/sdk';

export const accountOutreach = createFunction(
  { id: 'account-outreach',
 trigger: { cron: '*/15 * * * *', timezone: 'UTC' },
 retries: 3,
  },
 async ({ step, runId }) => {
 const leads = await step.run('fetch', fetchLeads);
 const enriched = await step.run('enrich', () => enrichLeads(leads));
 const draft = await step.run('draft', () => draftOutreach(enriched));
 const { approved } = await step.waitForSignal<{ approved: boolean }>('approval', {
 signal: `outreach-${runId}`, timeout: '48h' });
 if (!approved) return;
 return step.run('send', () => sendEmail(draft));
  },
);
Code reviewedState savedRetries on

03Failure recovery

A failed step is not a failed workflow.

Rotor saves each completed step. If Clay rate-limits you, it waits and retries the failed step.

Example run

account-outreach

At approval
01

Fetch

312 leads saved

This step will not run again.

02

Enrich

429, then retry

Rotor waits for the API.

03

Draft

Ready for review

The run reaches its approval gate.

Fetch stayed complete. Only enrich ran again.

04Human control

Let AI stop before it sends.

Put a human decision between an AI draft and a real prospect. Rotor records the answer.

account-outreach · run_8f2aWaiting for Maya
To[email protected]SubjectQuick question about your enrichment flow
Hi Jordan, I noticed your team is hiring GTM engineers. Are visual workflows becoming hard to review?
DNC clearPII clearTone checked
Action blocked until approvalEvery decision is logged

05Keep what works

The workflow lives where your team already works.

Keep HubSpot. Keep Clay. Keep Apollo. Keep your sender. Replace the canvas, not your stack.

Your repo

Review the change before it runs.

Use pull requests, tests, and the release flow your team trusts.

Your tools

Keep the systems already in place.

Rotor coordinates HubSpot, Clay, Apollo, Slack, and your sender.

One history

See what happened without opening nodes.

Review each run, step, retry, and output in the run detail.

Works withHubSpotSalesforceClayApolloSlackAny MCP server

Different starting point

Hit the Claude Routines cap instead?

Add retries, state, sub-minute schedules, and a run history you can inspect.

See the Routines path

Start with the painful one

Move the workflow that keeps waking you up.

Start with Hobby at $9. If it does not earn its place, ask for your money back within 30 days.

Move one workflowSee pricing