Add custom CRM code only for a defined gap

When to use it

A confirmed limitation in native CRM workflow actions starts this workflow. Use native actions where they work, then test a narrowly scoped code action with observable errors and rollback. The intended output is a bounded action contract with tested outputs and error dispositions. A useful receipt names the accountable person and the next action; it should make the commercial decision easier to inspect.

This is an original GTMhub reference design. It explains how we would run the job, with tools selected for the company's existing stack. It is not presented as completed client delivery or measured commercial performance.

Inputs and decision boundaries

Confirm object ids, api scopes, input/output schema and a native-action comparison. Keep the original source and observed date alongside each fact. Missing context stays unknown until it is resolved. Facts, interpretations and proposed actions should remain distinguishable in the handoff.

Your company brain holds the approved rules and proof; the live system holds current account state and ownership. Read both before making an operational change. Assign an exception owner before launch so an uncertain case has somewhere useful to go.

Run the job

1. Write the exact gap and the minimum required access.
2. Build the action against synthetic fixtures.
3. Test partial failures, retries and duplicate execution.
4. Release a version with an error owner and reversible writes.

At the decision gate, ask: Does native configuration meet the requirement with fewer moving parts? If the answer is no: use the native action and document its configuration. Only the supported path proceeds to its output. A stopped job should preserve the reason and what would let an owner resolve it.

The output to inspect

Failure and recovery

The material failure to watch is this: a retry duplicates associations or overwrites fields owned by another process. Stop that path and preserve the underlying evidence. Repairing a field or a source is different from changing the commercial rule; record which decision was made.

If a connected system fails, keep the original request or event and expose its unresolved state. Retry only the incomplete action, with a stable event key where writes are involved. Do not let a retry create a second owner task or bypass a previous exclusion.

Test before making it live

Replay a supported case, an incomplete case and the failure described above. Where the job writes a record or creates a task, replay the same event twice and inspect the result. Check that the exception owner can understand the hold reason without reconstructing every step.

Judge the result

Track successful unique actions, retry recovery and unintended writes. Record the sample, dates and definitions before evaluating a change. Operational success shows that the job behaved as designed; commercial outcomes need their own mature evidence.

Return reviewed corrections to the company brain with the decision date and rule version. Keep the original observation available. The decision register records what changed and why, while the GTM brain guide explains how the job fits into one company system.