Revenue operations integrations and automations

The lead lifecycle, the pipeline and the path from a signed quote to cash, built as automations and integrations you can change without a deployment.

17 guides  ·  Built with Tray Headless

What this work has in common

Most of revenue operations is a race against a person. A lead that reaches a rep on Thursday was worth more on Tuesday. A duplicate created this morning gets called twice this afternoon. A quote that fails on its way to the ERP is found by finance at month end, when the customer has already been invoiced wrong.

The systems are familiar: a CRM, a marketing automation platform, enrichment, a sales engagement tool, CPQ, billing and an ERP. The work is moving a lead, an opportunity or an order between them in the right order, with the right owner, and leaving a record of why each decision was made.

These guides cover the lead lifecycle from import to routing, the sync between marketing and sales systems, and the quote to cash path into finance.

Where revenue operations automation breaks

The record that matches nothing

A lead with a personal email, a subsidiary nobody mapped, a SKU the ERP has never seen. Every rule set handles the normal case. The ones that last send the odd case to a named queue and count it.

Two systems that both think they own a field

Marketing automation and the CRM overwrite each other's lead status on every sync, and the loop only shows up as a report that changes by itself. Decide which system owns each field before you build the sync.

A change that needs a deployment

Territories move every quarter and routing rules change every month. When the rules live in code, ops waits on engineering and the workaround becomes a spreadsheet. The rules belong in a table the ops team can edit.

The revenue operations guides

Each one is the design, the sequence it runs in, the prompts that build it, and what changes when it runs in production.

How to build lead import and validation

Validate before you write, quarantine the bad rows instead of dropping them, dedupe against what is already there, and keep the source.

Automation

SalesforceGoogle DriveMarketoSlack

How to build lead routing that assigns in seconds

Match the lead to an account first, evaluate rules in a fixed order, catch what they miss, and time it from arrival.

Automation

SalesforceMarketoClearbitSlack

How to build lead-to-account matching

Domain first, then fuzzy name, then hierarchy, with a confidence score and a review queue for the ones that are close.

Automation

SalesforceClearbitMarketoSlack

How to build lead enrichment that does not stall the queue

Enrich on a budget and a timeout, cache by domain, fall back between providers, and never hold a lead waiting for a field.

Automation

ClearbitZoomInfoSalesforceMarketo

How to build lead deduplication and merge

Detect on a scored rule set, survive the merge with field-level rules, keep the activity history, and never silently reassign an owner.

Automation

SalesforceMarketoSlackSnowflake

How to build pipeline hygiene automation

Detect the staleness that matters, nudge the owner rather than the report, escalate on the deals that count, and measure whether it worked.

Automation

SalesforceSlackGongOutreach

How to build a CRM to marketing automation sync

Decide field ownership before you build, sync deltas not everything, handle the person-versus-lead model gap, and break loops.

Integration

SalesforceMarketoSlackSnowflake

How to build a sales engagement to CRM sync

Log activity without flooding the timeline, suppress sequences on the accounts you must not touch, and keep one definition of engagement.

Integration

OutreachSalesforceZendeskGong

How to build a conversation intelligence to CRM sync

Write the few fields a rep will act on, keep every claim linked to its moment in the call, and never let a model set a close date.

Integration

GongSalesforceGoogle CalendarSlack

How to build a quote-to-order integration

Approved quote to signed contract to booked order, with the approval state carried through and amendments handled.

Integration

Salesforce CPQDocuSignNetSuiteSalesforce

How to build an order-to-cash integration

Closed-won to sales order to invoice to cash applied, as a CRM to ERP integration. Idempotent writes, a reconciliation loop, and

Integration

SalesforceNetSuiteSalesforce CPQStripe

How to build a CPQ to ERP sync

Map the product catalogue as data, carry ramps and proration intact, keep both catalogues aligned, and fail loudly on an unmapped SKU.

Integration

Salesforce CPQNetSuiteSalesforceSlack

How to build a billing to CRM sync

Put invoice and payment state where the account team works, without letting the CRM become a second billing system.

Integration

NetSuiteSalesforceStripeSlack

How to build subscription and entitlement provisioning

Turn a signed contract into working access on the day it starts, handle mid-term changes, and never let entitlement drift from what was sold.

Integration

SalesforceNetSuiteOktaGmail

How to build partner deal registration

Check submissions against pipeline in seconds, protect for a fixed window, expire visibly, and settle conflicts with a rule rather than an argument.

Automation

SalesforceHubSpotGmailSlack

How to build a territory and quota sync

Apply a plan on its effective date, keep in-flight deals with their owner, and make coverage visible before anybody signs off.

Automation

SalesforceSnowflakeWorkdaySlack

How to build a commission data to payroll sync

Qualify transactions against the plan, show the working line by line, hold disputes without holding the run, and reconcile before it pays.

Integration

SalesforceNetSuiteGustoWorkday

The systems involved

The applications these guides read from and write to, most used first. Each links to its connector page.

Connections these guides build

Solutions for revenue operations

The solution pages for this work, with the customer stories behind them.

Guides for other teams