.DkNUKaKx_ZLAT4m.webp?dpl=dpl_FFQ9uu6rhRCm54BGxZwaW513PntG){kind=small}
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.
26 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
AutomationLead 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.
How to build
AutomationLead 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.
How to build
AutomationLead-to-account matching
Domain first, then fuzzy name, then hierarchy, with a confidence score and a review queue for the ones that are close.
How to build
AutomationLead 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.
How to build
AutomationLead 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.
How to build
IntegrationLead scoring sync
Keep fit and activity scores apart, write one score the CRM trusts, let old activity fade, and route the moment a lead crosses the line.
How to build
AutomationSpeed-to-lead alerts
Alert the rep with everything they need, start a clock on every lead, escalate before it goes cold, and reassign when nobody picks it up.
How to build
AutomationPipeline 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.
How to build
IntegrationCRM to marketing automation sync
Decide field ownership before you build, sync deltas not everything, handle the person-versus-lead model gap, and break loops.
How to build
IntegrationSales 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.
How to build
IntegrationConversation 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.
How to build
IntegrationQuote-to-order integration
Approved quote to signed contract to booked order, with the approval state carried through and amendments handled.
How to build
IntegrationOrder-to-cash integration
Closed-won to sales order to invoice to cash applied, as a CRM to ERP integration. Retries that never create a second order, a reconciliation loop.
How to build
IntegrationCPQ 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.
How to build
IntegrationBilling to CRM sync
Put invoice and payment state where the account team works, without letting the CRM become a second billing system.
How to build
IntegrationSubscription 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.
How to build
AutomationPartner 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.
How to build
AutomationTerritory 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.
How to build
IntegrationCommission 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.
How to automate
AutomationBusiness rules and routing decisions
Hold the rules as a table the process owner edits, decide the clear cases automatically, let AI sort free text, and send the rest to a person.
How to build
AutomationDeal desk approvals
Route each discount and non-standard term to the right approver, decide in Slack with the deal in view, lock the quote to what was approved, and keep the record.
How to build
IntegrationForecast snapshot sync
Freeze the pipeline and the forecast call every week, keep each snapshot untouched, compare the call with what closed, and show where deals slipped.
How to build
AutomationPartner onboarding
Take a partner from signed agreement to portal access, a partner manager and their first training in a day, with the partner set up the same way in the CRM and the portal.
How to build
AutomationPartner certification tracking
Bring partner training and certifications back to the CRM and the partner portal, so tiers, deal registration and renewals reflect who at the partner can actually sell.
How to build
AutomationPartner account mapping
Bring account overlaps with partners into the CRM, so reps see which partner already works with an account before they start, and partners hear about the right ones.
How to build
AutomationPartner lead sharing
Route partner-referred leads to the right rep with the partner credited, pass leads to partners with a deadline to accept, and take back the ones nobody works.
The systems involved
The applications these guides read from and write to, most used first. Each links to its connector page.
- Salesforce (26 guides)
- Slack (25 guides)
- Snowflake (23 guides)
- Marketo (7 guides)
- NetSuite (7 guides)
- Outreach (6 guides)
- Clearbit (4 guides)
- Workday REST (4 guides)
- HubSpot (4 guides)
- Gong.io (3 guides)
- Looker (3 guides)
- DocuSign (3 guides)
Connections these guides build
Solutions for revenue operations
The solution pages for this work, with the customer stories behind them.
- Lead Routing Automation with Tray.ai Lead routing automation, from form fill to first call.
- Revenue Operations Automation with Tray.ai Revenue operations automation, from campaign to commission.
- Order-to-Cash Automation with Tray.ai Order-to-cash automation, from quote to cash applied.
- MCP for Salesforce and HubSpot with Tray.ai Your CRM. Your agents. Under control.
Guides for other teams
- Finance (12)
- Customer success (11)
- People operations (7)
- IT and security (15)
- Marketing (3)
- Data operations (7)
- Platform engineering (12)
- AI operations (15)
- Legal and compliance (9)